I have a question regarding the "Default Field Configuration Scheme". I see that this scheme is now associated with every type of ticket - specifically we have Bug/Story/Task. For Bug type of ticket i need one custom field to be "required" and i do not want to put any validator on the Create workflow because that is a common flow. What is the way to get this done? Earlier i had 3 different field schemes associated with these 3 different types of ticket. That has got replaced with this default scheme.
I used the optimizer on three of our projects after reading the description of how it works. It did clean up a lot of old, unused fields, but it also removed 11 fields that we actively use every day. I only realized something was wrong when QA reported they couldn’t move a story into Acceptance—turns out the QA Engineer field had been removed. After checking our screens more closely, I found 10 additional fields missing.
I opened a support ticket, and the initial response asked whether I wanted an option to reverse the removal. While that would definitely help future users, my main concern is that the optimizer removed fields that were still in active use. I’m hoping Atlassian can address the underlying issue so the optimizer doesn’t incorrectly classify fields as unused.
52 comments