How to calculate the original committed feature and removed feature from PI

[Yatiraj Sharma]

Hi Team,

Have a specific ask to calculated how many features were originally committed for a PI (We have a custom field created to denote the PI) and how many delivered and how many removed from the PI.
Note: we dont have change of value for that field available and we are not having any plugins at this moment.
Is there any JIRA JQL we can look at it or in eazyBi if that is possible and we dont even have the Jira Align and can't go to it as of yet.

[Alexey Pavlenko _App Developer_]

Hi @Yatiraj Sharma

Did you try the native Sprint Report?

Unfortunately, you won't be able to construct Committed Scope and Removed Scope metrics using JQL, since you need to interate over the history of each issue in a sprint. 

As for the Completed Scope metric, you can construct a JQL in this way

Sprint in (%SPRINT_NAME%) AND (statusCategory = Done OR resolution = Done)AND resolution date >= "%START_DATE_OF_SPRINT%" AND resolutiondate <= "%END_DATE_OR_COMPLETE_DATE_OF_SPRINT"

If you have ScriptRunner, you can construct the Removed Scope metric using 

issueFunction in removedAfterSprintStart("%BOARD_NAME%", "%SPRINT_NAME%")

As you can see, these JQLs should be maintained manually.

If you wouldn't like to maintain it manually, but get all in one solution and you are open to paid apps, you can try the app I have developed - Multi-team Scrum Metrics & Retrospective.

It has all the predefined Scrum metrics and allows you to write custom metrics without needing to maintain them manually. Additionally, it allows you to retrospect these metrics in-place.

It supports Scaled Frameworks such as SAFe, LeSS, SoS, etc. It allows to make comparison between periods, teams, or groups of teams, e.g., Team 1 and Team 5 as one entity versus Team 3 and Team 4 as another.

Best regards,
Alexey

[Yatiraj Sharma]

Thanks a lot @Alexey Pavlenko _App Developer_ ,

Above solution would definitely work with User Stories and tasks which are scoped for Sprint/iteration 

However we scope our features for PIs and in general DC Jira, we dont have any way to scope that... What we did is created a custom field and name as Quarter/PI and then we give values like Q1 FY 24/25, Q2 FY 24/25 etc....

But again, there is not entity like in Jira align to see how many features were originally committed and delivered and removed.

Let's say we had 10 features committed at start of the PI Q2 and we removed 5 out of it in between and moved to Q3, and delivered 5 in Q2, so current setup would give as 5/5 100% planned vs delivered as we have at the end of Q2 
But it actually it was 5/10 which is 50% .. question is how we calculate in Jira ?

[Alexey Pavlenko _App Developer_]

@Yatiraj Sharma

From my perspective, my filters above still cover your case. You can list all the sprints in JQLs that a PI consists of.

Another solution could be to create another custom field to track the history, such as a 'History PI' field. You can maintain it manually or automatically.

Best regards,
Alexey

[Oskars Laganovskis]

Hi @Yatiraj Sharma,

As for eazyBI - you would need to import the change history for the relevant fields.

If PI is a single-select customfield, you might enable the change import by adding extra settings in import options.

you might read more about that here - https://docs.eazybi.com/eazybi/data-import/data-from-jira/import-issue-change-history#Importissuechangehistory-Customfieldchangehistory.

However, the great flexibility of Jira allows a multitude of ways to build your workflows.

Therefore, each activity on features needs a bit more explanation to see how to calculate that.

What denotes the feature being committed to PI, and what denotes the removal and the delivery?

regards,

Oskars / eazyBI support

[Yatiraj Sharma]

Hi @Oskars Laganovskis ,

Greetings !

Thanks a lot for the help, have imported the history of the custom field, However, need some help on how do we access to original value compared to current value?
Like current I can see is like this

[Issue].CurrentHierarchyMember.get('BRP/PI')

So for old value what is the custome calculated measure I have to use ??

[Oskars Laganovskis]

Hi @Yatiraj Sharma ,

You could access the PI value at a historical point in time using the following expression.

CASE WHEN
--check if relevant for the rest of the report context
 ([Measures].[Issues history],
--resetting the PI dimension 
  [BRP/PI].CurrentHierarchy.DefaultMember)>0
THEN
 Generate(
--find the relevant PI
  Filter(
--set of PIs from the selection
   DescendantsSet(
--from currently applicable member/selection
    [BRP/PI].CurrentMember,
--take the level of individual entries
    [BRP/PI].[BRP/PI]),
--the issue was releated to the PI at the end of applicable time period 
   [Measures].[Issues history]>0),
--string part to display
 [BRP/PI].CurrentMember.Name,
--split by comma, if multiple relevant entries
  ",")
END 

 This might work but could get slower on larger datasets.

There might be a faster alternative option, depending on your full reporting requirements.