I have a JIRA screen configuration which is shared with multiple JIRA projects. One one project, I want to show a new custom field but it should not appear on rest of the project. I try to avoid creating another screen configuration. Is there a way to make a field visible only to this particular project, or another best practice to handle such situation?
Without creating separate field configuration or screen scheme, this can be achieved simply by using Custome Field Contexts.
It depends on your *exact* requirements, but if your need is what I think you've said, you've got three options.
I think you have a custom field that should only appear in project X, although you've got projects X, Y and Z. This is exactly what the schemes are for, and you can choose between:
On points 2 and 3, the important point is that you still put the field on screens. For a field to appear within a project, it has to match ALL three criteria.
The best practice is a little difficult to define, there's several factors in which methods will work best for you and your users.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You can have different issue types, and only allow the field to associate with certain issue types by using field configurations. That is the easiest way to do this that comes to mind.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.