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
We have a custom field that ties into our team database. It is quite a large list. It is a single drop down field.
We have to use this field to sort and filter roadmap items by but whenever it is added to a plan the performance of the plan becomes almost completely unusable.
Do admins have a way to configure the use of the field in plans but only as 'read-only'?
Hello @Bryan Rosenthal
I can suggest only two options:
1) Add the people you only want to view the Plan within the Plan Access panel, there you can set users and groups to view only.
2) As there is no field level security in Jira (check out Nic's explanation on another question), instead you could control the editing of a field to an extent, by making "edit field X" a workflow action instead of an edit (and adding conditions to the transitions you add for it). This way the field could not be edited in PoJ, and only Jira during a workflow transition.