When we make and change in field mapping, for some fields there is a need to re-run the processor to affect the field mappings.
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.