-
Suggestion
-
Resolution: Unresolved
-
None
-
283
-
31
-
-
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
In the custom field configuration context, it is not possible to choose a project if it has already been associated to another configuration context of the same custom field. For instance, it is not possible to make the following associations:
Task, project1, configuration context 1
Task, project2, configuration context 2
Bug, project1, configuration context 3
Bug, project2, configuration context 4
- has a derivative of
-
- Gathering Interest
- is duplicated by
-
JRASERVER-25166 Context cannot set different values for different issue types within the same project
-
- Closed
-
-
- Closed
-
- Gathering Interest
- relates to
-
- Under Consideration
-
MNSTR-3619 Loading...
-
- was cloned as
-
- Gathering Interest
-
- Gathering Interest
- mentioned in
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
[JRASERVER-6851] Allow more than one custom field context to be associated with the same project but different issue types
We recently taught a Jira Bootcamp to some of our highly engaged and awesome clients, and attempted to build multiple custom field contexts in a particular project for different issue types, only to find out that it is not possible to do so, as per the essence of the issue that is captured here.
There are of course workarounds (creating different custom fields being one; not ideal), but I find the design (ability to create different field contexts mapped to different issue types) confusing in that it leads the admin down a path that is then not working.
I am also curious why an issue opened 19 years ago is still being tracked? If it has been fallen off the priority list for nearly two decades, it will probably never get completed and you might want to consider closing it with a succinct note on the reasons and suggested workarounds. Thanks for your consideration.
It is a shame that such a old and high votes feature request , that is even older then the cloud, is considered for the cloud but not yet for DC. Shame on Atlassian that DC customers again are clearly now only in the second position. The are good for giving their money to Atlassian but not for bringing DC also functional forward.
@e0a4ab8f8fd7 where you been for last 2-3 years?
Did you see current UX/UI of Jira Cloud vs Server / DC? Those are already two totally different products. If you train a user to use DC, they have no idea even how to search for issue or change the issue type. Those products are going thru totally different development tree.
@Tomáš Vrabec [neresit.cz] I think that woul be a mistake on Atlassian's part. You don't want people to have to be retrained when switching to the Cloud, Both products should remain similar.
because they wont release new features for datacenter anymore. they have a cloud first policy.
I see that. Nevertheless, this is not an answer for me why this feature with significant demand is not considered. It was raised in 2005 already, long before the cloud product was even in discussion.
Creating multiple custom fields for collecting the same information across different issue types is so redundant and confusing, not just in the process of configuring it, but also for reporting purposes later. It looks horrible in queues and filters. Having multiple contexts for different issue types in the same project would be a game changer..