New issue starts with resolution of Fixed, should be Unresolved

[Christine Duran]

Just a few days ago, we noticed that all new issues are starting with a resolution of Fixed. We haven't changed the workflows or transitions in months. Is anyone else having this problem?

[John Funk · Accepted solution]

Hi Christine,

What we have noticed it that when we clone an issue it is copying over the Resolution value even though it is placing the issue in the Backlog. I have a bug opened with Atlassian to try to get that solved.  The Resolution should be empty in the newly cloned issue. 

[Christine Duran]

I think I found the issue. Someone had added the Resolution field to the create issue screen. This forces a resolution on creation. Wouldn't be surprised if the same thing happens when cloning the issue.

[Jack Brickey]

Hi Christine, you might wish to convert your findings to the actual answer on this post to assist others that might stumble upon this thread.

[Ernest Heredia Soler]

I have the same problem when clone a closed (resolution != none) issue. The field resolution mantains the same value as the original issue field.

I hope atlassian fix it soon.