Is there a way to control the order of members within a Project Role?

[Thomas Hardin]

By chance, does anyone know if it is possible to control the order of the members within a project role? Our goal is to assign tickets to a default member of a project role, but from what I've learned a project role's default member needs to be identified prior to creating a project.

However, members of project roles will change, so we are trying to determine how we can identify 1 member to be the primary assignee of an issue when we do not have the luxury of identifying a default. 

We understand we can assign an issue to the first or last member, but just don't know if there is a way without actually editing a workflow and calling out the specific person.

Any help is greatly appreciated.

[Boris Berenberg - Atlas Authority]

How would you assign it to the first or last member of a role?

[Thomas Hardin]

We are using Scriptrunner, which provide the option to use Assign to First Member of a Role and I mispoke on the Last Member as that is based on the last user of the role that the issue was assigned to.

However, I have noticed that when we've tested this without using scriptrunner and only using JWME, the last member of the role was the one that was selected.

I am not sure how a member is selected though, so if you have insight on this, please share.

Thanks

[Boris Berenberg - Atlas Authority]

I am more confused by your business logic than anything.

how we can identify 1 member to be the primary assignee of an issue when we do not have the luxury of identifying a default.

If you can't identify a default, and you can't control the order, then why not just pick any first person? I think that's the logic behind that kind of function in the first place.

It's not intended as "Pick the first from a numeric list" but more as "Pick any 1 from a list".

I am also adding some tags to this to help gain visibility to your question.

[Thomas Hardin]

I'm sorry for any confusion.

This situation we have is that there are multiple request that are managed by 1 organization. And, within that organization, there are team that work certain issues. Some members of the teams can work on some issues, while other can work other issues. So, we've set up the roles based on the specific people that would work on an issue. 

The customer wants to have 1 person to be the default assignee for the issue, while all others in that role are notified. That person may not be first or last on the list of members of the project role. So, if we have a role with 10 members and the default assignee happens to be #5 on that list, how can we make that person the default assignee for the ticket?

Based on out understanding, we can set a default member of a project role prior to a project being created,, but what if that default person changes over time?

I hope this helps.

[Thomas Hardin]

Additionally, we can always use a post function to just assign the issue to a specific person, but I would think that we don't want to update workflows every time someone changes jobs or becomes a default assignee for an issue. I would think we would want to provide a way for the team leaders to identify he default without contact Jira Admins.

Thank you for any assistance and I do apologize for the confusion.

[Boris Berenberg - Atlas Authority]

Component default assignees?

[Thomas Hardin]

That was one of the options I thought about (Should've thought about that initially - Jira 101). But, I ended up adding project roles identical to the original, just with "-Default". This way I could assign to the Default and still notify the main role.

Thank you Boris for all of your help.