We're having trouble with the resolution field.
1. It's mandatory
2. it has no none value
When we edit an issue, we have to set it - but there is no none value corresponding to the <null> value (in the database) which means the issue has no resolution.
We are forced to set it to something and the manually clear in in the database.
I think the resolution feature is broken - if I edit an issue, i should not have to set the resolution - I might just edit the description or something else not related to the status.
I should not have to create custom resolution values either as some kind of workaround as others have done (from what I've read briefly on the forum).
If possible, maybe we can have a screen sharing session some day next week?
Thansk - we solved it your way which also was the suggestion from the support.
What I don't understand is why they continue to force the resolution field to be mandatory if visible and connected to transitions. In my case we would like to manually set it and in order to do that it must be visible in different screens, but since there is no "none" option it's not possible.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Hey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...
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