Why do duplicate Request State Metrics appear after RTC/RRDI upgrade?
I am being asked by a report writer why in recent weeks there are duplicate State values on their report.
The graph legend has these values ( listed in their order on the legend):
New
Resolved
In Progress
Reopened
Verified
Reopened
Verified
New
In Progress
Resolved
Verified
The "duplicate" states appear only on columns post our 4.0.3 > 4.0.5 upgrade on Feb 22, 2014.
The report is getting the State from this metric path: Change Management / [Request Metrics].[State].[State].[State]
If I expand that section of the hieararchy, there are indeed multiple "New", "In Progress", etc.
Thanks in advance
More research ....
Using Query Studio to look at ODS / Request Area / Request State it is noted that there are entries dated Feb 23, 2014 which differ in the External Key2 field where the newer ones have something like:
bugzillaWorkFlow
com.ibm.team.apt.storyWorkFlow
com.ibm.team.workitem.defectWorkflow
A bit messy but trying to show that "External ID", Name are the same, Request State ID are different and External Key2 is different.
The graph legend has these values ( listed in their order on the legend):
New
Resolved
In Progress
Reopened
Verified
Reopened
Verified
New
In Progress
Resolved
Verified
The "duplicate" states appear only on columns post our 4.0.3 > 4.0.5 upgrade on Feb 22, 2014.
The report is getting the State from this metric path: Change Management / [Request Metrics].[State].[State].[State]
If I expand that section of the hieararchy, there are indeed multiple "New", "In Progress", etc.
Thanks in advance
More research ....
Using Query Studio to look at ODS / Request Area / Request State it is noted that there are entries dated Feb 23, 2014 which differ in the External Key2 field where the newer ones have something like:
bugzillaWorkFlow
com.ibm.team.apt.storyWorkFlow
com.ibm.team.workitem.defectWorkflow
A bit messy but trying to show that "External ID", Name are the same, Request State ID are different and External Key2 is different.
I'm wagering this is intentional, but seems to be a cause of confusion.