nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Sub-Tasks without parents yes Orphans

Craig Nodwell_7eve9b

I've never seen this before after almost 20 years in Jira.
This morning I had at least two teams create Sub-Tasks issue types (development/qa/ui) off of the stories in the Backlog of their Scrum Sprint Board.
About an hour later I got reports that these tickets did not get created, followed up with they are created but have no Parent Story !!
Around the same time I had another team report that a user dragged her Sub-Tasks into the Done column and selected yes to Move Story To Done as all the children were resolved. This was done and children disappeared, leading that team to think they were deleted... they were not they were Orphaned .... Please see screenshot.

I've resolved this manually by doing a move and selecting the parent issue with no other changes.

Can anyone shed some light??

Issue Type

Orphaned Issue
Screenshot 2023-02-01 134121 no parent.png

Accepted answers

Florian Bonniec

I've already seen orphan sub-task like that but never spent time to investigate as it's quite rare.

Everytime it happen my users told me that it was during an automation rule execution when they was creating sub-task from the story creation using automation but deleting the story before it ends. It's not the steps you listed tho.

Usually integrity checker to fix the parent link issue then the move or delete works for me.

All comments

Craig Nodwell_7eve9b

Screenshot 2023-02-01 134204 issuetypes.png

Florian Bonniec

I've already seen orphan sub-task like that but never spent time to investigate as it's quite rare.

Usually integrity checker to fix the parent link issue then the move or delete works for me.

Craig Nodwell_7eve9b

I did lay in an automation but it doesn't touch the children.
I've since disabled it thinking it may be the root.
It's a scriptrunner listener that checks if a custom filed has been updated on the Story and does some remove link add link stuff.
Re: the custom field is a single issue scripted field for a Feature Link (issue between Epic and Story) nothing fancy about the scripting on the field it's a simple JQL to get the Feature Issues within the project.
The listener triggers on an issue updated event, checks for the story type, checks if the Feature Link field is in the changelog. If that all evals to true it then removes a custom link between the feature and the story and replaces it with the value found in the Feature Link. Further to this it inspects the issue in the Feature Link grabs the Epic Link off there and populates the Story with that Link.
This was my only change prior to this Orphan thing happening.
Thoughts?
I'll share the script if you think that will help.

Florian Bonniec

In you script you seem to clear some link maybe you are cleaning the one that is created between sub-task and task ?

Even if not displayed in Issue Linking JIRA use links between those issues. Link should be Parent-Child Link.

Regards

Craig Nodwell_7eve9b

I think you just got me on the path.
Will update.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

scriptrunner

jira

jira-server