What are the use cases where it is best to use Project Roles rather than Groups?

[Abdul Kader Broachwala]

What are the use cases where it is best to use Project Roles rather than Groups?

[Gikku · Accepted solution]

Hi @Abdul Kader Broachwala 

Project roles can be updated by the project managers where in users belonging to groups can be modified only by the Jira administrators.

So project roles are recommended if you want to use a shared workflow across projects, where users can be specified on project basis and also changes to the list happens more often.
But if it's a general list to be used across projects, use group instead.

Regards
Gikku

[Abdul Kader Broachwala]

Hi Gikku, 

Thank you for your answer. I think project roles can also be updated by Project Administrator in JIRA, correct?

[Gikku]

Hi @Abdul Kader Broachwala 

Yes, project administrators can update the list of the users in the project roles. But they won't be able to add any new project role or user. Only a Jira administrator can perform those actions.

Regards
Gikku

[Abdul Kader Broachwala]

Thank you for your prompt response.

[Nic Brough -Adaptavist-]

Use roles for speed, flexibility, delegating rights to your users, and making life easier for all of us. 

Use groups if you're stuck in a corporate scheme that thinks groups are useful or have an over-arching demand to control your people.  It can be slightly slower, but there's not a lot in it technically.  (In the real world, letting people do what is most effective is.... um... effective - so cheaper, faster and better.  Use roles)