Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Set certain statuses as "Done" in Jira for parent issue types

Jasiel Lora May 14, 2020

Hi all,

I've tried to research this online but keep getting conflicting answers. Our team just started using Jira and I'm trying to close out some sprints. Under the status field on our "Requirement" issues we have Not Required and Done. When we update an issue as Done is shows as done when trying to complete the sprint. But when we update an issue as Not Required that's not the case even though in workflows we have Not Required under the "Done" category. It seems to work for completing sub tasks but not for parent issues.

Under resolutions I added a "Not Required" resolution but I don't understand how I can use that with workflows to mark Not Required issues as "Done".

 

Screenshots below for more details.

 

Any help is greatly appreciated. Thank you!

workflow.PNGnot req resolutions.PNG

2 answers

1 accepted

2 votes
Answer accepted
Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 14, 2020

Jira and Jira Software have two different ways to look at "done".  My standard advice is that you should configure your workflows, status and resolutions so that the behaviour is consistent between the two. 

Jira (Core and Service Desk) look at the Resolution field.  If it is empty, the issue is open.  If there is anything in the field (and it reallly does not matter what), then the issue is resolved (which in most cases, is equivalent to done)

Jira Software looks at the board.  An issue is done if it (and its sub-tasks) are in the last column on the board

To make these work well together, you should do several things

Categorise your status correctly - any status that represents "done" should be the green "done" category.  This is not strictly necessary, but it makes life easier for your end users looking for "done", and shortens the next three rules:

  • Any transition that goes from a green status to a non-green status should have a post-function on it that says "clear the resolution" (add the "update field" post-function, select the "resolution" for field, and "none" for the value)
  • Any transition from a non-green status to a green one should either
    • Have a post-function that sets the resolution
      • OR
    • Go through a transition screen that includes the resolution
      • (never both though - the post-function will blat out what your people select in the screen, which is bad)
  • Only put green status in the last column of the boards, and non-green in any other columns

Now, that last rule can vary in cases where you have issues that are handled by multiple teams on different boards and there's some form of hand-off in the process, but that rule should be the starting point, as it's the ideal case.

Jasiel Lora May 14, 2020

@Nic Brough -Adaptavist- Nevermind my last post, I understood what you meant and figured it out. Thank you!

0 votes
Jasiel Lora May 14, 2020

Thank you for your response @Nic Brough -Adaptavist- 

 

We use just Jira Software. I added a post function to each transition. For Not Required the post function sets the resolution to Not Required so that's working. However the issue still isn't considered completed/done. When I click on complete sprint it still says 0/30 issues are complete. See screenshot. 

An issue is done if it (and its sub-tasks) are in the last column on the board

So does this what I'm trying to do here is not feasible? Do I have to set the issues to Done in order to have them be completed/resolved?  See screenshots for detials.not required.PNGdone.PNG

Suggest an answer

Log in or Sign up to answer