I have a custom field that is an issue picker and I'm trying to create two contexts for the field, one for a development environment and one for a production environment.
For some reason whenever I try updating the JQL query I want the custom field to have for its given project It also changes the JQL query for the other context.
This is problematic as It would impact the production environment whenever i try to set the development environment JQL query.
If someone could give me insights into what may be causing that, It would be greatly appreciated.
Good Day @Michael H
How about the issue types? Because the context goes with the issue types.
Can you please share a screenshot once you hide any confidential info?
Best,
Fadoua
I can't grab a screenshot at the moment but the I always specified the project and the issues that the context was associated with and both contexts would be associated with different projects and different issue types
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Fadoua Terribly sorry about the late follow up, I can't grab screenshots because of the environment I'm working on but I can provide better clarification.
For some reason, even if an issue picker has multiple contexts defined, in the Scriptrunner fields section the issue picker is defined as having its configuration scheme set as 'All Configuration Schemes' making it such that whenever I edit the JQL query of one context it updates the JQL query of the other contexts to the same value. I've been able to make issue pickers with multiple contexts where this isn't an issue and the configuration scheme contains multiple contexts but sometimes this problem arises and I don't know what the cause of it is.
If you have any insights into why the configuration screen is being set as 'All configuration schemes' that would be great
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
No worries at all, I am reading your reply
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Michael H did you check if there is context added to the fields in Jira? What I mean using Jira native feature under issue types.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.