Urgent + Important question

[Preem Prakassh Dayaal]

Problem Statement

Project : P1 

Users - u1, u2, u3 , u5 , u6, u7...

Requirement : u2 , u5 users should be able to assign issues only to u7 and no one else

rest all users should be able to assign to all 

Please suggest a workaround in Jira 

As per other discussion I understand creating a separate permission scheme will not work because users have different assignment restrictions. 

Regards

Preem

[Trudy Claspill]

If you are working with a Company Managed project, you could do this with a custom workflow, I think.

You would remove the Assignee field from the Edit screens.

You would add 2 self-reflecting transitions into the workflow on each status.

One of those transitions would have on it a Condition to limit the visibility of the transition to users u2 and u5. On the same transition you would put a Validator to check that the value of the Assignee field is u7.

The second transition would have a Condition on it to allow everybody except u2 and u5 to see it. This transition would have no Validator since the users of this transition are not limited in how they set the Assignee field.

There might be some additional tweaks needed. I haven't actually tried to implement this, but I used similar logic previously to limit who could edit which fields in issues.

[Trudy Claspill]

I forgot to mention that on each of those self-reflecting transitions you would need to add a Transition screen that includes the Assignee field.

In this manner the Assignee could be set only by executing a Transition.

[Nic Brough -Adaptavist-]

This is done with permission schemes - it is what they are for.

Your only option is to work with the schemes (and have a look at why you think people might have different privileges just because of their access route - that sounds wrong to me)