Can you make a JIRA custom field visible to plans in Portfolio but only as read-only?

[Bryan Rosenthal]

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'?

[Danny]

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. 

OR

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. 

• Remove the field from the edit screen.
• Create  new screen that has the field you want to protect.
• Edit the workflow, adding transitions to each status.  These transitions should
  
  • Have the screen with the field on it
  • Go back to the same status
  • Have conditions that only allow people you want to edit the field to use them

Thanks,

Danny

[NAYANA]

Portfolio plug-in allows editing of read-only fields. A custom field that was made read only in Jira is editable in Advanced roadmaps and this is circumventing controls. how can we fix that?