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
I have a project where project admin has created Components, but this system field was not added to any of the create, edit , view screens.
However users are able when bulk changing issues to update the components which are then appearing in the screen. They cannot edit that field but they can see it in the view screen which is not supposed to contain it.
I have even one issue were components is empty and still visible on the view screen.
Is it a specific feature of the Components field? I couldn't find any documentation on it.
What are those limitations with the field configuration hiding? Can you add some more details why you find it problematic? (I'm just curios, as I'm plannign to rebuild our project config structure in the near future, and have a lot of uncertanities in screen configs vs. field configurations.)
I find a bit worrying that we can set up a project defining what fields users can see by defining screens and then with bulk change rights you have access to anything.
Also because bulk change is not a permission you give to a user at the level of the project, it can be very acceptable that a user project admin of project A can do bulk change on it, but on project B where he is on the business side he shouldn't. But I can't prevent that as JIRA admin.
This is not going in the right direction for JIRA instances used for years and allowing a certain level of customisations. Having as only possibility to hide a field in the field configuration is very limitative.