How do you manage the 'update parent issue' screen?

Currently I have a story workflow and a separate sub-task workflow in the one scheme assigned to a project.

Both workflows use global transitions throughout the workflow.

Issue: If I close all sub-tasks for the parent issue, I get the 'update parent issue' screen giving me two options:

"All sub-tasks for parent issue JDP-39 are now Done. To update the parent issue to match, select a transition:

  • Cancelled
  • Released"

These are the two final 'green' statuses in the parent workflow. 

However is it possible to add other options such as 'ready for testing' or testing' (two other statuses in the parent workflow) in the 'update parent issue' screen? I understand those statuses have global transitions so this may be the issue.

Otherwise can I remove the update parent screen without effecting the workflow? 

Thanks

1 answer

0 vote

You need to add transitions that go to other "done" status, then they will appear on the screen.

You can get rid of the screen by cutting it down to one transition to done status.

Hi Nic - thanks for the prompt ressonse.

The other statuses that I want to appear in the screen are not 'done' statuses though - for example 'ready for testing'.

We're also using a 'global' transition for this status. 

We require two 'done' statuses of cancelled and released as part of our internal process - so is there another way of removing the screen without removing green statuses? 

No, the way the system works is following the process.  It's marking the parent issue as "done" when all the subtasks are completed.  So all it's doing is saying "which 'done' is the issue?"

It's not able to ask about not-done status, because the point of the process is to mark the issue as done.

Hi - in another workflow, which was set up by a previous administrator, there were other options which were not 'done' statuses. For example:

Capture 2017-07-04 at 9.52.12 (1).png

Ready to deploy for example was a yellow status with no resolution being set?

I've tried to review this workflow but couldn't see any differences in my current configuration apart from the fact that the sub-task and parent issues were using the same workflow within the scheme. 

Ah, have a look at the board - I expect you'll find those status are in the far right hand column.

"Done" is not a function of the status category!  (Which is misleading, in my opinion)

OK, so the statuses in the far right column determine which statuses are available in the 'update parent screen'? 

And yes it is misleading, I found this out when reviewing burndown reports where the 'ready for live' was in the far right column and counting towards burndown before it was transitioned to 'released'. 

Yes, that's correct.  I should have said it sooner!  Sorry!

No worries! We got there :) Thanks again. 

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,313 views 14 20
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot