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.
To see this feature in action check out our recent dependencies demo here: https://www.youtube.com/watch?v=eQu5VsUqyZA Keeping on top of your dependencies is a key part of ensuring project success....
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events