Jira issue permissions

[Delta Development]

Hi Readers,

We're trying to implement a workflow with permissions and somehow it doesn't seem to work. We have the following users/members on a Jira Next-Gen project:

Project lead:

Create (in backlog), edit, link, assign, delete, move and transition issues(also from backlog to board).

Project Member-Reporter:

Create (in backlog), edit/comment, re-open issues.

Project Member-Assignee:

Create (in backlog), edit/comment, transition, close, re-assign, re-open issues.

Jira-user (global)

Create (in backlog), edit/comment issues.

Project-members is development

Jira-user are other company departments (Sales, purchases)

We've now modified our Permission schemes matching the above requirements (Jira-user, members, issue-assignee, issue-reporter, project-lead,admin,etc) but somehow project-members are always allowed to do ANYTHING and if set as a Jira-user they can't be an assignee.

How do have to approach this? Could someone help me out here? We dont understand the 'layering'.

Best regards,

[Fahad Siddiqui]

@tjarcoboerkoel 

This can be related to Permission schemes issue. The best way is that you need to go permission

then click on 

Permission helper add the user's who are facing issues you will find the cause easily.

[Delta Development]

Indeed, there's said that the project-member has the ability to do everything.

But if I remove the member, than they are not part of the project and cannot be assigned as assignee. This seems to overrule the Permission schemes.

[Fahad Siddiqui]

@tjarcoboerkoel Did you check the user using Permission helper? i need the screen shot so that i can help you in this.

[Delta Development]

Hi Fahad,

Thank you for your reply.

I've created an issue "make it happen" (reporter = me) and assigned to person YY.

Permission schema "move issues"  and "transistion issues" are configured as:

Project Role

atlassian-addons-project-access

Group

administrators

Current assignee

Project lead

But as project member the user "LD" is still able to move and transition the issue, apparently because he is project member. So, I don't understand the layering of permissions and (user)rights.

[Fahad Siddiqui]

@tjarcoboerkoel if you want now to not allow project-members to assignee tickets then remove the user or group form Assign Issues project role. 

[Delta Development]

Hi Fahad,

Thank you for your reply.

I seek the project-members have their 'permissions' not to be bound to a 'project-role', but bound to an Issue. The rights depending on being (for example) an issue reporter or an Assignee (executor).

Scenario:

'Simon' is project-member and is reporter of an issue. He'll not be the one working on the issue. He should only be able to comment and view. So he should not be able to close, transition or re-assign the issue.

'Alex' is project-member and is assignee of an issue. He'll be the one working on the issues and could register time, transition to another status, comment and close. AND assign it to another Member (pass-over) but by doing that he'll also pass his "rights"  to the new assignee.

Project-lead (me) initial assigns issues to a project-member before transition 'backlog' -> 'ToDo'.

I hope this clarifies the goal.