Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

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

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

1 answer

0 votes
Danny Community Leader May 22, 2020

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

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?

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Advanced Roadmaps

Introducing Advanced Roadmap’s new dependency report

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....

128 views 2 6
Read article

Community Events

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

Events near you