How to separate a custom field (multiple choice) for 2 different projects

[Mark]

Dear all,

We have 2 JIRA projects on our JIRA server. They shared same custom field and choice values for last 3 years. It is because both projects are belonging to same support team at the beginning.

However, today they are separated. Both Projects want to remove the choices not belonging to them. Some of the choices are common to both projects.

The problem is, in last 3 years, all the issues they created have bind to the multiple choices field already. If I create a new custom field to project B, project B's user need to query one additional field in future. It is inconsistent and cause mistake.

How can I solve this problem?

Mark

[Sreenivasaraju P · Accepted solution]

Hi @Mark,

You can create new context for the custom field for the project B and add options related to project B only. From the earlier context you can disable options related to project A.

Refer https://confluence.atlassian.com/adminjiracloud/configuring-a-custom-field-776636423.html

for more details.

[Mark]

I will test with 2 different context. Thanks.

[Kat Warner]

You (and they) need to consider whether having 2 fields with limited options is better than setting up a dashboard gadget/filter/report to identify any incorrect choices made.

This may simply be a training issue and have a low error rate.

Having 2 fields affects filters and reporting for both teams individually, and for anyone who needs a higher-level view where they want to look at both projects. The common values may look the same to someone at a ticket level but will be separate from a filter/reporting point of view.

Good luck.

[Mark]

Thanks. It seems a good solution. I will try it out.