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 Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,026 views 12 18
Join discussion

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
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot