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; } } }

Why does Parent Issue loose subtasks when moved back to beginning of workflow?

Steven VanderVelde

Using a jira board to track assets. Some assets come in a kit and the idea was to have the kit components as sub-tasks under one main issue for the kit. When the kit is moved to 'in progress' the subtasks are still linked to the kit, but when the kit is moved back to 'To Do' the subtasks are no longer linked to the parent kit issue

Update:
May be because one of our groovy scripts remove links from the the parent issue. Is a Subtask considered a link and if so what type?

Accepted answers

Trudy P Claspill

Are the issues really sub-task issue types or are the other issue types linked to the main issue?

Do you have the issue key for one of those sub-tasks that has disappeared? If so, try browsing for it to see if the issue actually still exists and has been modified or has truly been deleted.

All comments

Nic Brough -Adaptavist-

Welcome to the Atlassian Community!

This suggests an automation or script (post function or listener) that is deleting or changing the parent of the sub-tasks such that they disappear from the parent issue.

Check with your admins what they have set up in the project, or listeners.

Trudy P Claspill

Are the issues really sub-task issue types or are the other issue types linked to the main issue?

Do you have the issue key for one of those sub-tasks that has disappeared? If so, try browsing for it to see if the issue actually still exists and has been modified or has truly been deleted.

Steven VanderVelde

the issues are really sub-task issue types and the sub-tasks are not deleted they just have no parent anymore

Steven VanderVelde

```

IssueLink link in linkMgr.getOutwardLinks(issue.id){

linkMgr.removeIssueLink(link, roboUser)
```
Does this include sub-tasks if linkMgr = ComponentAccessor.getIssueLinkManager()?

Nic Brough -Adaptavist-

The only way to do that is with code that removes the parent issue, forcibly, overriding the relationship that Jira enforces.

It is also possible to hide the relationship, which makes them look orphaned, but you can't do that in the workflow, you have to change the parent's issue type!

Welcome!

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

Quick Links

Find more posts tagged with

server

jira

jira-server