Feature Statuscatogry = closed but child status !=closed

[Richard_Crowley]

In old Jira I was able to identify records with data hygiene issues. This included where teams had closed the feature, but stories/bugs/etc. under it were still open.  I am really struggling to recreate this in Jira Cloud.  I have tried using JQL "issueType = Feature AND statusCategory = Done AND issue in linkedIssues("relates to") AND issueType = Story AND statusCategory != Done" and also tried bringing back all features that are done and then adding a filter "COUNT#subitems > 0" but neither seem to work. Does anyone on this forum have any ideas of how to do this? (I don't have script runner or add ons and can't add either)

[Stephen_Lugton]

Hi @Richard_Crowley 

Do you have access to Plans?

If so create a timeline view filtered to:

• show only Features
• Show only Done work item

Set up the view to show the Progress (Issue Count):

You can then visually go down the list looking for any Features where the progress bar has anything other than Green

[Richard_Crowley]

Thanks @Stephen_Lugton for the quick response &  helpful guidance. This would work if we had small volumes of features, teams and data but due to the volume of data we have I was after something that would only show those features/stories with issue. 

[Stephen_Lugton]

Hi @Richard_Crowley 

My next suggestion is to try this:

Set up an automation similar to:

Create a JQL filter:

Labels IN ("Has_Open_Child_Tasks"}

[Stephen_Lugton]

You could then add a second automation to label the child tasks that are still open:

Just make sure to check the box at the bottom or rule details to allow this rule to be run by another rule

Then you could use another JQL query to find them:

Labels IN ("Feature_Parent_Closed")

[Bill Sheboy]

Hi @Stephen_Lugton 

FYI for your example rule using the Manual Trigger and which uses a Branch on JQL:

Behind the scenes, the automation engine automagically excludes the trigger work item (i.e., issue) for a Branch on JQL by adding AND key != {{triggerIssue.key}} to prevent accidental runaway recursion possibilities.

To also detect the condition for the trigger issue, an additional Branch on Current Work Item with a JQL Condition (for Feature and StatusCategory tests) could be added to the rule, followed by your current suggested steps.

Kind regards,
Bill

[Stephen_Lugton]

Thanks for the reminder @Bill Sheboy I forgot to add the comment that this needs to be run manually from a ticket that doesn't meet the rule requirements