nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

I want to assign the ticket to the group and only to the people in specific group

Swarupa Bawaskar

Hello All,
I want to assign the ticket to the group first and from the group how can i assign to a single person. The assignee should be from the group itself. Can someone help me execute this requirement in JIRA Service Management?
I appreciate any help you can provide.

Accepted answers

All comments

Asha Goyal_0i7i5i

Hello @Swarupa Bawaskar

As there could be only single assignee, you can create a Group user picker field where nultiple users can be added. For Assignee if that is fixed every time, you can apply post function to assignee the ticket to particular assignee.

Feel free to give more details in case I mis understood the issue and please Accept and Vote if it helps.

Thanks

Mohamed Saad Taha

Hello @Swarupa Bawaskar

you can create group picker or custom filed ( drop down list ) and values will be the names for your assignment group but unfortunate the assignee filed will not depend on the above both options

Richard Scholtes

The "Assignee" field in JSM is a Person picker field, so it will always be showing all possible persons. So would a group picker field. The upside of that is, that you don't have to administrate those fields for new persons or those that left the company.

But there is a way to get this more specific, that would work if the group of people is not that big.

You could create a cascading select list field. In this you can enter teams and persons in a hierarchy depending on each other. But you will have to maintain the field manually, which means adding and deleting the users.

That's why it's not generally recommended to do that and most people would tell you to work with workflow options and the automation engine to get a special person as assignee depending on the content of the ticket.

Swarupa Bawaskar

thanks @Asha Goyal

Actually, I want to restrict the options available in the assignee field. currently I am able to assignee the ticket to all the people in the project, but I want to restrict it to the group users only

Swarupa Bawaskar

thanks @Richard Scholtes

Actually, I want to restrict the options available in the assignee field. currently I am able to assignee the ticket to all the people in the project, but I want to restrict it to the group users only

Richard Scholtes

The field "Assignee" is a system field in Atlassian and therefore not changeable in any way.

The only way to put restrictions in place is to make it unchangeable by manual access and only change it via automations. But that would need you to have specified tasks for specified assignee and let an automation identify which assignee is needed.

Swarupa Bawaskar

can you guide us with the steps to restrict the manual changes on the assignee field.

Nic Brough -Adaptavist-

There is an alternative to automating things. Building on @Richard Scholtes answer.

Create the group picker as he said (let's call it the-responsible-team for clarity)
Create a set of groups with the relevant possible assignees in them
In the permission scheme, set the "can be assigned issues" permission to "custom field: the-responsible-team

This will mean the only selectable assignees will be the ones named in the group-picker field.

The downside of this is that it does not work during issue creation. For that though, there is no "assign to", so Richard's recommendation of removing the assignee field from the create screen is spot on. You'll end up with an issue assigned to the default assignee, and an assignee selection based on the group. If you do this, I recommend making the group-picker mandatory, or having someone responsible for triaging issues included as a possible assignee as well as the group.

Asha Goyal_0i7i5i

Hello @Swarupa Bawaskar

I hope you have enough hint to proceed on. Let me know if still any further questions.

Thanks

Haripriya

@Swarupa Bawaskar

For assigning issues to members of a specific group, I would recommend using Workflow Properties. You can use the group picker to add the group. However, to assign it to only members of a particular group under the Assignee field, we need to add a workflow property.

key: jira.permission.assignable.group 
value: {{groupID}}

We only support group IDs. Group names will cause errors.

How the workflow property looks:

img 1.png

This is the error when I try to assign it to someone who is not in the group.

Use Workflow Properties - Reference article.

Cons - We can't fetch the group ID from a group picker field. We need to add a value while configuring the workflow so to dynamically populate the field based on the selected group is not directly possible.

" data-emoji-text="">" data-testid="image-emoji-" data-emoji-type="image">" width="20" height="20" data-emoji-short-name="" data-emoji-id="atlassian-warning" data-emoji-text="" /> This is added per status. If you want to enforce this restriction throughout the workflow, add the property to every status.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management