As per my question above, We have a state that a ticket can enter (Backlog) that only the head of product or system admin can update or assign it out. The problem is that others can see the ticket still (which is fine) but they can still use the assign options, and even when they're told not to its still possible for them to do so.
Please see the image below:
jira.permission.assign.user|denied do the magic
Yes, it works, but actually this allows only the user with name "denied" to see them.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
;) key = "jira.permission.assign.user" and value = "denied" in the specific workflow-step-property
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes you can. Use Workflow properties. There is a post on this here.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
What is 'Ad Hoc'?
try something like: jira.permission.assignable=denied
If that doesn't work, try:
jira.permission.assignable.user=auserwhodosentexist
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
thanks, this helps. Although I'm having issues getting anything to work.
I'm trying jira.permission.assignable.Ad hoc.1 denied and am getting no where. Can you see what I'm doing wrong here?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The Ad hoc is a user group I was testing this out with. The thing is I don't want to completely remove the buttons completely. The Production team and Admin still need them. But all other departments don't need it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Try:
jira.permission.assignable.group=Ad hoc
Use jira.permission.assignable.group.1, jira.permission.assignable.group.2 etc if you have more than one group!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Remove the spaces from the group names, see https://confluence.atlassian.com/display/JIRA/Group+Name+Guidelines+for+JIRA
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Join us to learn how your team can stay fully engaged in meetings without worrying about writing everything down. Dive into Loom's newest feature, Loom AI for meetings, which automatically takes notes and tracks action items.
Register today!Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.