Forums

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

Resolution set to "Done" in error when transitioning

Graham.Wilson
Contributor
September 25, 2020

Hi.  I have noticed that sometimes, when a JSD ticket's status changes, its Resolution changes form "Unresolved" to "Done" in error. So far I've not been able to pin down an exact sequence of events that makes it happen.

 

So...

  1. Has anyone else experienced this?
  2. Does anyone know what causes this?
  3. Most importantly, what's the solution?
  4. If there's no solution, is this already on Jira's radar? If not, what do I need to do to register it? Is this enough?

1 answer

0 votes
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.
September 25, 2020

This will be something you've got configured in your system

Start with a look at your history - is the change of resolution grouped with the status change, or is it separate?  (If it is separate, then the users making the two changes may be different and that might give you a good lead)

The reasons this might happen are:

  • The workflow transition you are using to change status might have a post-function that sets the resolution, or it uses a screen with the resolution field on it.
  • You have a board configured to set the resolution when moving into the column that status is in (beware of having many boards looking at the same issues - someone may be using a board that does this where others are using ones that do not)
  • You may have a listener catching the status change and updating the resolution, and it could be making the decision to change it based on any logic you can code for
  • An Automation may be doing much the same as a listener
  • It is possible to create a service that updates resolution, but that would be very unlikely as you'd not see the resolution change at the same time as the status, it would happen when the service runs, on a schedule, not upon issue-change.
  • If you have one of the scripting apps, these could be doing it (although the ones I'm familiar with would all do it via one of the above)

A look at the history for the change should rule some of these out though.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events