How can I deny the Assign Button to a project role while still allowing them to change the assignee on a transition screen?

[danielglowe]

Per the title. I've got a project where I want to force certain project roles to use the workflow buttons.

I've removed this project role from the Assign Issues permission of the permission scheme we're using, but this seems to also deny them the Assignee field on Transistion screens which is not what we want.

Can someone help explain how we achieve removing the Assign button from a project role while not deying Users in this role the ability to change the Assingee on a Transition screen.

[Jobin Kuruvilla [Adaptavist] · Accepted solution]

You can't do it without code or javascript hacks. Neither of them is possible in JIRA onDemand.

[danielglowe]

Thanks for the super quick reply Jobin, though not exactly the answer I was hoping to hear.

Seems a strange limitation as I can imagine many Jira Admins would want to force Users to use workflow buttons but still allow them to change the assignee on a transition, oh well.

[trevor foley]

Hi Daniel - I'd love to accomplish the same with my workflow; remove/disable 'assign' button on the view screen but enable on the transition screen.

Please let me know if you find a solve.

Thanks!

[Michael Megliola]

Same problem here. My company used to be able to do this when we hosted Jira locally, and our transition to OnDemand has left us with disorganized workflow status/assignee pairings. The best I've been able to do instead is set up some custom filters with mail subscriptions to alert me to these mismatches when they occur, so I can go in and clean them up myself as they arise. Pretty irritating. Would love to be able to disable the "Assign" button for certain project roles without denying them the Assign function itself!