Jira Align Enterprise Insights - What are 'MAP Feature to Process Step' and 'MAP Epic to Process Step' used for
Platform Notice: Cloud and Data Center - This article applies equally to both cloud and data center platforms.
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
This article discusses the use of the Enterprise Insight ‘MAP Feature to Process Step’ and ‘MAP Epic to Process Step’ views.
They may hold no data although Process Flows/Steps have been defined for Features and Epics and plenty of work items assigned to those process steps.
Environment
Jira Align
Diagnosis
(:info: Make sure that the Process Step and Approach (to test Features) fields have been enabled for your Portfolio under the Settings > Details Panels Settings).
Create two Process Steps: EPS1 and EPS2 and choose Epic as the Level (you could see the same behavior with Feature Process steps).
Associate EPS1 to Program1
Associate EPS2 to Program 2
Create an epic 'MyEpicWithSingleProcessStep' and select 'Program 1' as the 'Primary Program'.
Save and close
Create a second epic 'MyEpicWithMultipleProcessStep' and select 'Program 1' as the 'Primary Program' and 'Program2' as an 'Additional Program'.
Save
Notice that now there are 2 Process steps (with the 'Show more Process Step' link on the right side below the 'Process Step - EPS1' section.
You can select as well a process step for EPS2 (else it will be null)
Wait for the ETL job to complete and update Enterprise Insights.
Run the SQL query below
1 2 3 4 5 6 7 8 9 10 11 12select vs.[Value Stream ID], vs.[Value Stream Name], ps.[Process Step ID], ps.[Process Step Name], e.[Epic ID], e.[Epic Name] from current_dw.[MAP Epic to Process Step] meps inner join current_dw.[Process Step] ps on ps.[Process Step ID]=meps.[fk Process step id] inner join current_dw.[Value Stream] vs on ps.[FK Value Stream ID]=vs.[Value Stream ID] inner join current_dw.[Epic] e on meps.[FK Epic ID]=e.[Epic ID] ORDER by [Value Stream ID]
Result:
You see only one record returned while we were expecting one for each of the two Epics created before.
Value Stream ID | Value Stream Name | Process Step ID | Process Step Name | Epic ID | Epic Name |
265 | EPS2 | 982 | Starting work | 3504 | MyEpicWithMultipleProcessStep |
When looking at the REST API response for the given Epic we see:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
{
"id": 3504,
"title": "FXP Epic with multiple PS",
[...]
"description": "FXP Epic with multiple PS",
"primaryProgramId": 450,
"tags": null,
"state": 1,
"processStepId": 979,
[...]
"lastUpdatedBy": "661802",
"createdBy": "661802",
[...]
"customerIds": [],
"epicObjectId": 2,
[...]
"releaseIds": [],
"additionalProgramIds": [
627
],
"additionalProcessStepIds": [
982
],
"points": [
{
"estimationSystem": "T-Shirt",
"estimationValue": "No estimate"
}
],
"externalKey": null,
[...]
"links": [],
"self": "https://alignsupport.jiraalign.com/rest/align/api/2/epics/3504"
}
Notice the value of the additionalProcessStepIds compared to the one in the tables above.
Cause
The 'MAP Feature to Process Step' and 'MAP Epic to Process Step' views are only populated with data when Epics or Features have more than one Process Step associated.
Solution
The Process Step information of an Epic/Feature that only belongs to a Process Step/Value Stream, will be present on the EI table of that work item via the column [developmental step] that reflects the current Step as seen below for a Feature example:
When there are multiple Process Steps/Value Streams associated with an Epic/Feature, EI will reflect the relationship of the extra Steps on the view [Map Epic/Feature to Process Step] as see below for an Epic example:
Was this helpful?