You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
When on "Search for Issues" and e.g. you want to adapt the visible Columns it appears that if you have a lot of customfields which have e.g. included in the name "...status..." you will never again be able to include the Jira field "status" again. The list for serchead felds which includes "status" ends by saying e.g. "13 more options. Continue typing to refine further". But well the status for the non-customerfield status is not further refinable.
Seems like a Bug ?
well in big companys where different way of workings in different divisions are in use you may find all kinds of customerfield variations (i.e. a status may represent a certain wording/freetext/description which different teams/divisions are using differently. I totally agree that such fields may never be allowed to be created at least not as such that there are blanks before and/or after "status". But once the train started in a big company it's hard to rename all fields with e.g. "...._status_...." as filters aso need to be adapted as well ;-)
Nevertheless thanks for your quick reply
I agree that's a tough job, it takes a lot of meetings and workshops to prevent this kind of custom fields :)