Forums

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

Issue Status to Done no longer triggering Status.Category to Done - what did I do?

Marc Galante
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
April 29, 2020

I have several older stories which when I set Status on the Issue to Done, there appears a checkmark and the word "Done" to the right of the status field (see rightmost corner of screenshot, below).  However if I change another Story Status to Done, it a) does not get this additional checkmark, and does not show as a "Done" Issue on reports, etc.  I think I found that the app uses a Status.Category field to really control what is "Done" but whatever workflow, etc that used to flip Status Category has stopped working/I did something? 

 

Can anyone help me get the status.category workflow back to working correctly Please?

I am using the Jira Next Gen, Agile template.  thanks for any help!

Screen Shot 2020-04-29 at 4.44.30 PM.png

2 answers

1 accepted

0 votes
Answer accepted
Marc_Galante
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
April 30, 2020

It turns out that someone added a Column to the Board to the right of 'Done' - this caused the standard workflow that sets Status Category to 'done' - see 1st screenshot - this shows the checkbox and the word 'Done to the right of the status field-  without the Done column being the rightmost column on the board, the Status values which are driven by the columns on the board are displayed in the same order in the status dropdown as the columns, and the workflow requires that 'Done' be the right-most column -see second screenshot for the invalid column/status field arrangement, and the 3rd for the correct one.

 

This doesn't feel like a very well designed way to do things, and I just got lucky finding it as I had a 'test' project that I created as a sandbox and was able to do a point-by-point comparison of the two solutions until I found this difference-  took me several hours hat I wont get back.  Perhaps more Documentation from Next Gen on this 'wrinkle' could be put together?

 

Screen Shot 2020-04-29 at 4.44.30 PM.pngScreen Shot 2020-04-30 at 8.54.55 AM.pngScreen Shot 2020-04-30 at 8.55.03 AM.png

0 votes
Jack Brickey
Community Champion
April 29, 2020

The workflow is not accommodating the setting of the Resolution field. Either use a post function to set the resolution or associate a screen with the transition that exposes the Resolution field to the user to have the set it. Don’t forget to clear the field with a post function for any ‘reopening’ trAnsition.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events