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?

Thanks,

Gaby

1 answer

1 accepted

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.

Alex

Suggest an answer

Log in or Sign up to answer
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Published yesterday in Jira

5 ways you can make the most of Jira Software and Bitbucket Cloud

As part of the Bitbucket product team I'm always interested in better understanding what kind of impact the use of our tools have on the way you work. In a recent study we conducted of software devel...

58 views 0 5
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