assign tickets of a certain project to a specific group using different contexts

[Andrea Dieguez]

Hi, I need to assign tickets of a certain project to a specific group, for this I use the "assigned Group" field with different contexts, indicating for the project PROJECT1 to use certain options like GROUP 1 PROJECT1, and GROUP 2 PROJECT1 also
PROJECT2, with other GROUP 1 PROJECT2, and GROUP 2 PROJECT2
In addition to some specific options for certain projects, I have some global options with the aim of, if there are no specific groups, the global options are used, maybe this is the problem because it is not compatible to use global options and specific contexts?.
I am telling this because the problem is that when filtering in the PROJECT1 queue, I don't get the options included in the project1 context, but rather the generic ones.

Maybe I am misunderstanding and applying it wrong, can you help me please?

What I intend is to have certain assignment groups for each project and for this I wanted to reuse the assigned group field already created by adding different contexts.
But maybe this option is not worth it and I have to create a specific assigned group for each project.

Thanks in advance

[Kris Dewachter]

Hi @Andrea Dieguez ,

I'm presuming "Assigned Group" is a custom field ? Is this of a type "Select list" ?

You can add different contexts for each project.

Open the custom field --> Context and Default value --> Add new context

In the context, you can define for which issue type and projects you want this context to apply.

Once you created the new context, you can use "Edit options" to define the values for each context.

Best regards,

Kris

[Andrea Dieguez]

Ok, I just realized that when editing the context I don't have to indicate the type of issue or the project, but I have to indicate in which type of issue types of the specific project I want the options to be displayed.

It did not work for me because I had put "All issue Types" and I had indicated the Project thinking that it would apply to all the issue types of the project in question but it does not work like that, but I have indicated the issue types  used in the project in question and now It does load the indicated assigned groups.

Thanks @Kris Dewachter  for the clarification!!!

[Andrea Dieguez]

However, now doing the filter for the queue I see that although the group is correctly filtered in the selector of each ticket, (Picture 2) When it comes to including the field "assigned group" to filter the queues by groups, I get the groups that are set by default (Picture 3) not the specific ones indicated in the context for the project (Picture 1 and 4) and the types of incidents  I include some screenshots so that you can see what I mean. (I blur some areas to avoid sharing more information than necessary

[Kris Dewachter]

Hi @Andrea Dieguez ,

I did a test on my environment and i experience the same issue.

When you create a queue, and use the "Basic Search", it only lists the values of the global context. I think this is a bug in Jira.

You can bypass this issue by switching to JQL search. When you use "Assigned Group" in the JQL, it will list all possible values.

Best regards,

Kris