Segregating field values by project

[Teri Simonds]

We have a lot of different projects in JIRA and all but one of them are related to the same product.  We've set up a separate project for a different product and that project needs to use some of the same fields, both custom and not.  However, the values for those fields are different.

For custom fields (such as Affected Release), I think I need to define a new context for the new project.  At that point, I can add the release numbers specific to the new project. 

For non-custom fields, such as Resolution, the new project does not want to see any of the existing project's values.  Is there a way to make Resolution (and potentially other values) project-specific?

And for both of these changes, will I need to perform a re-index?

Thanks for your help!

Teri

[Gabriel Senna · Accepted solution]

Hi Teri,

Unfortunately, this type of field can't be modified.

Due to the fact that it's a system field, it impacts all projects and JIRA itself.

However, there is a feature request open for this to be implemented, you can access it in the below link.

https://jira.atlassian.com/browse/JRACLOUD-3821 

Considering the fact that there is no estimated time or decision for this feature to be implemented, adding yourself will ensure you're proactively informed of progress and updates going forward in accordance to our Implementation of New Features Policy.

https://confluence.atlassian.com/support/implementation-of-new-features-policy-201294576.html]

We are sorry for the impact this lack of feature causes in your work.

[Teri Simonds]

Hi Gabriel,

I thought that was the case.  Thanks for confirming!  There are a couple of workarounds that we can implement that will minimize confusion.