Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Checking Data on the KPI Dashboard

...

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,

    image-20240805-120331.png

  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 .

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 mappingsprocessors.

...