Jira resolutions problem

We have a strange problem. Resolution field for some tickets is set by developers, BUT there is no any transition or any other event (move, clone) in history, just info that resolution field changed by some developer (like he changed some custom field value). I asked devs about it, they said that they do nothing. So who knows what is it ? (maybe they use some IDE and accidentally change the resolution? )

1 answer

0 votes

The only way I can think of doing this is if you have the resolution field on an edit screen. 

Please check the edit screens for the use of the resolution field.  If you find any screens using it, remove it immediately - it's breaking stuff and you need to stop.  The only screens you can have it on are transition screens in the workflow.

Thx for reply! But I know it and that's why I'm confused, because there is no resolution field on edit screen, and this field we have only on screen for transition which leads to Resolve status. 

The only other thing I can think of then is "code".  You've got a script or update editing the resolution.  (It can't be REST or an external service - they respect "resolution is not on the edit screen")

Joseph Pitt Community Champion May 16, 2016

I have some workflows that set it with a post function and the user never sees the field on a screen. I would look at the workflow used by the issue type being affected.

Nic, thx for help, I created filter for such cases and try to monitor it, maybe logs will help me. (but actually we don't have such scripts, it's strange). 

Hi Joe, thx for reply. No the problem is that in history I see :

`SomeUser` made changes - 19/Feb/16 7:17 PM Resolution Fixed

so there is no any transition, and anyway I checked WF just in case

Without a transition, it has to be "edit" or an automated script.  There is no other way.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Oct 09, 2018 in Jira Core

How to manage many similar workflows?

I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...

397 views 6 0
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