Versions Compared

Old Version 11

changes.mady.by.user Pragyan Sundarray

Saved on

compared with

New Version 12

changes.mady.by.user Pragyan Sundarray

Saved on

Key

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

Checking Data on the KPI Dashboard

...

Global-Field-Mappings

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'

  1. Click on image-20240805-103341.png to land on KPI dashboard

  2. Click on 'Settings' on each KPI widget

Custom KPI level settings

override the default mappings by customizing them manually.

  1. Click on 'Settings' on each KPI widget

image-20240805-101201.png

Anchor

Global -Field-MappingsGlobal Jira mappings

Mappings that are global and apply across dashboards.

  1. Additional Filter Identifier

  2. Custom Fields Mapping

  3. Defects Mapping

  4. Issue Types Mapping

  5. Workflow Status Mapping

  1. Go to ‘Projects’ list and search your project

  2. Click on image-20240805-105640.png to edit configuration

  3. Click on 'Mappings'

    image-20240805-105738.png

  4. Expand each section to edit and save the mappings

image-20240805-105950.png

...

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. (see steps)

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

  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.

...