I have been asked if it's possible to remove the "type" (same as issuetype), on JQL search and leave only "issuetype" to be selected, instead of both with the same function.
Hi Boris, thanks for replying this quick! I would avoid add-ons. The reason is because we already have a Type customfield created and rename it's going to be very complicated since a lot of projects are using this field.
The biggest question is why there is a redundant name for Issuetype, like "type"?
Appreciate the help!
My guess is that type was the original and a lot of people didn't understand it so Issuetype was added to make things clearer, and type was left for legacy reasons.
However, this is just a guess and I have no evidence to support this.
In your situation, the best thing I can suggest is to move away from the Type customfield. It will be a PITA, but it can be done. Getting rid of type is going to be a lot harder.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Can a new-to-agile team survive and thrive in a non-agile culture? If so, what advice would you give to those trying to be agile in a non-agile culture? What's the key(s) to success? Share your thoug...
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