Field Security Plugin: How to handle built in fields?

I understand JFS supports only custom fields but not built-in fields (like affected version, fixed version, priority, etc).

How to cope with this serious limitation?

The only possible solution could be to define custom fields for each built-in field (and to maintain the values equal between these fields), but I do not like this kind of solution.

Any idea?



1 answer

1 accepted

0 votes
Accepted answer

Hi Gaby,

Actually your solution with custom fields is the only one possible for the time being. But JFS 2.0 is under development right now and it'll definitely will support more built-in fields.




Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,770 views 18 21
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you