Checking Data and Managing Field Mapping Configuration

Checking Data on the KPI Dashboard

1. Once Jira processor is successfully run, click on to go to the KPI dashboards

2. You can access different Jira KPIs across dashboards
   
   

   Open

   

Managing Jira Field Mappings

Jira Field Mappings	Description	Steps	Image Reference

Jira Field Mappings	Description	Steps	Image Reference
Default settings	default field mappings are associated with the Standard Jira configuration template while setting up Jira. These metadata identifiers are prepopulated when you click on 'Settings'	Click on to land on KPI dashboard Click on 'Settings' on each KPI widget	Open
Custom KPI level settings	override the default mappings by customizing them manually.	Click on 'Settings' on each KPI widget
Global Jira mappings	Mappings that are global and apply across dashboards. Additional Filter Identifier Custom Fields Mapping Defects Mapping Issue Types Mapping Workflow Status Mapping	Go to ‘Projects’ list and search your project Click on to edit configuration Click on 'Mappings' Expand each section to edit and save the mappings

Things to Remember

When modifications are made to the field mapping, certain fields require the processor to be re-run to implement the changes effectively. Specifically, when we add or remove any mapping, such fields require the processor to be rerun

1. Global mappings: Any modifications to the global field mappings in a Jira or Azure Board configuration require the processor to be re-run.

2. KPI-level mappings: A few KPI-level mappings that require processor rerun are marked in the Settings.
   For example,
   
   

3. For any other changes to the mappings, simply refreshing the dashboard is sufficient to apply the updates.

Note: This applies only to Jira and Azure Board processors.