Issue resultion set on scrum actions

[Michael Schlueter _secunet_]

We see an unexpected behaviour in our Jira Software projects (Server) that use the Scrum functionality. Sometimes, the issue resultion field is set to Done in situation where the status itself is not changed but other scrum related actions are performed (issue moved to a different sprint, story points changed ...)

I'm not sure why this could happen. I do not have a reproducible case, yet.

Any ideas?

Regards

Michael

[Nic Brough -Adaptavist-]

This sounds like you have a post-function, listener, or automation picking up that you have transitioned an issue and setting the resolution.

You'll need to identify that and remove it.

[Michael Schlueter _secunet_]

Hi Nic,

yes, I already looked for these typical things, but was not able to find anything. So I was hoping for some different kind of magic that I am not aware of.

[Nic Brough -Adaptavist-]

The only other things that might set a resolution are

* email or other integrations (that would not be tied to doing things in your scrum process, they would appear to happen spontaneously, not when a card is moved to another sprint or story points edited.

* Your people going into the issue and changing the resolution.  Note that this can change resolution if an inexperienced admin has put the resolution on an edit screen- people will be inadvertently resolving issues just by editing.