@Michael Tokar Please reopen this ticket.

At the very least please take a data-based approach, do some digging into analytics, and report back with actual numbers of how often people see the modal and decide to close the parent task vs how often they close the modal without closing the parent task.

If the numbers point to the modal actually being used to close the parent ticket >50% of the time (and probably a slightly higher bar than that, considering how often I've accidentally closed the parent issue) then so be it.

But my hypothesis — based solely on how our process works at my job — is that the data will show the modal being closed without closing the parent task.

In our case, we use subtasks to track small chunks of work on a ticket, but the parent ticket itself holds all the acceptance criteria. As such, once all the subtasks are closed we generally pass the parent task along to the reporter of the ticket so that they can review it. We don't want the parent ticket to close right away because it still needs to be signed off on. In fact can cause issues with SOX compliance for the ticket to be closed without first being signed off on.

mtokar  How can this be resolved? Is it answered because a workaround is available? The workaround might not be suitable for everyone due to not having script runner or it might not even work, Not to mention this is a requested change and should have gone through a  'gathering interest' state based on your feature policy.

In short, the workarounds don't work for our situation and this needs to be reconsidered. 

Jira server Jira v8.3.4

The workaround of @Nathan Given is very good (requires script runner).

It really annoys the hell out of our users, as we rely on linked issues that has the 'blocked by' link type to be close as well, and not just sub task. The workarounds are all quite an ugly hack.

I was frustrated by the same issue. That's essentially a Post Function that is running that we cannot control and is not visible in the list of post functions. Naughty.

Here's an easy workaround to at least disable the modal so your team can avoid spending time on an unhelpful modal that actually tempts them to update to the incorrect status:

1. Make a copy of your Story workflow so you can edit it.

2. Edit the copy of your Story workflow so you cannot get to DONE without passing through READY TO ACCEPT (or whatever your desired pre-DONE state is). For me, I removed the ability to transition to DONE from ALL other statuses.

3. Save the changes.

4. Swap your story workflows and Publish.

5. Test. When you complete all tasks on a story, the modal to Update Parent Status to DONE should not appear.

How was this still not addressed more than 5 years later? As all the other commentators before, we need to disable this popup for our workflow! Please solve this issue.

As far as I understand, we need to restrict permissions to transition parent issue - so that when closing sub-tasks, there is no Pop-up. Is that correct 

How have this been resolved?

I agree with @Paul. I am going nowhere after reading all the comments. 

@Sascha - I have the same issue. Did you figure out the solution ? 

Hey guys... Kind of not very useful that this was marked as resolved @ 08/Feb/2018 6:13 PM, suggesting that there has been a feature released to support the suggestion, but no indication of what has been released.

Can we perhaps get some clarification on what exactly has been done for this issue, please?

Thanks,

Paul