Once Jira processor run successfully, following can be observed-
Jira KPI’s on different dashboard appear with data.
Jira Mappings are setup with default setting provided in metadata identifier-
Note: In case if user is not satisfied with default mapping user can change mappings-
From Metadata identifier-Refer Meta Data Setup
Or customize it manually by clicking Setting button on individual KPI.
Managing Field Mapping Configurations
When modifications are made to the field mapping, certain fields may require the processor to be re-run in order to implement the changes effectively.
when we add or remove any mapping, the below are the mappings that require processor to run again.
Note: This is applicable for only Jira processor and Azure board.
1.Custom Fields Mapping:
The changes that we make in the custom field mappings requires the data to be fetched again from the Jira board or azure board, for that we need to re-run the processor.
This will be applicable for all the fields in the custom field mapping.
2.Defect Mapping:
The changes that we make in the defect mappings requires the data to be fetched again from the Jira board or azure board, for that we need to re-run the processor.
In the defect mapping this will be applicable for UAT defect values, production defect values.
3.Additional Filters Mapping:
The changes that we make in the additional filters mappings requires the data to be fetched again from the Jira board or azure board, for that we need to re-run the processor.
This will be applicable for only squads.
For any type in the squad we need to re-run the processor.
4.Issue Types Mapping:
Kanban:
The changes that we make in the Issue type names under Issue types mapping requires the data to be fetched again from the Jira board or azure board, for that we need to re-run the processor.
Scrum:
The changes that we make in the Issue types to be fetched from Jira requires the data to be fetched again from the Jira board or azure board, for that we need to re-run the processor.
Apart from the above mappings, for any other change in the mappings refreshing the dashboard is enough to affect the mappings.