I am just trying to reproduce this error and seems that the problem raised becouse the Resolution field is placed on Create Issue Screen. I'am going to analyze this problem in depth tomorrow morning.
I will let you know if the issue will be resolved.
I should also ask is there any business need for you to place Resolution field on Create Issue Screen? We didn't considered such a case before, but it doesn't mean that such case shouldn't be implemented - if of course there is any business need behind.
Hello Atlassian Community! Each month, we run a series of Spotlights to highlight Marketplace vendors and apps that our team thinks this Community would find valuable. In last month's Spotlig...
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!
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