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.
It would be really nice to have a bulk operation 'hide' available when setting up field configurations. The current 'click > reload' for each field seems a bit OTT.
Apologies, I was concerned I might not have been clear enough.
Go to Project settings > view field configuration > click 'hide' on each you want to hide > the window then does a little refresh, and you repeat with each field you want to hide.
What I'm suggesting is:
View field configuration > each field has a checkbox next to it > click the checkboxes of all the fields you want to hide > click a hide button finally > all hidden at once.
Just seems like it would be much more user friendly and time efficient.
I am not following. However if you wanna make a feature suggestion I recommend using the feedback link within the application.
Seems reasonable. TBH, I rarely am hiding fields and if so it is usually a single field. But I certainly prefer a multi-select approach in most cases.
I seem to remember there is an open improvement that suggests something like this - it's been around since before Cloud, so I suspect it would have been reproduced from the original server request to the Cloud improvement set.
From memory, the request was to change the "click once, refresh" to "fields we can set through the whole scheme and a save-changes button" - more like the Confluence space permissions settings.
I realised I haven't chosen an accepted answer for this one.
My post was more opinion based, I guess. I'll be sure to raise this appropriately as a suggestion if it doesn't already exist on a request ticket.
Thank you very much for your input folks, have a great week.
I ran into a situation where I had to do this for 360+ fields. The solution I came up with is to create a template field configuration with all of the fields hidden, then copy it and show the fields I'd like for that particular configuration. Not ideal, and there may be a better way, but as of right now this is the best way that I've found to do it