It is limitation have already identified few years ago, and I have never understand why ?
When a Customfield is created, it has a default context applicable on any Project/Issue.
When you created an additional Context, you have 2 possibilities for specifying when the Context is applicable :
It is not possible to select an Issue Type without a Project ... Ok, why not ?
But as soon as a Project is used in a Context, it is no more usable for creating a new Context.
By example, if we have 3 projects (PA, PB & PC) and 3 Issue Types (IT1, IT2 & IT3).
On CustomField creation, we have : Ctxt 1 applicable on Any Project/Issue Type
If we create a context for PA/IT1, then it no more possible to create the other combinations :
What is the functional reason of such limitation ?
In most of part of JIRA, the Context to use is always deduced on the pair Project/IssueType.
The only possible workaround since 5 years (https://jira.atlassian.com/browse/JRA-16027) is to created a new customfield for each additional Context needed ... It is not really practice, mainly if we have to use this field in JQL.
Does somebody has a technical workaround (patch of the ConfigureCustomField action) ?
Thanks by advance.
I guess because the code to decide on which context to use would be more complex. You'd have to work out which of several contexts could apply was the most restrictive and choose that one. Hard to fix seven years later perhaps?
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!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG