Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Permission Implementation

Mohamed El Taweel March 14, 2018

How can I implement the following requirements

on project "Vacation Project"  anyone on jira can create a ticket.
The ticket can be worked on and closed only by a user with HR Admin role

 

Thanks a lot in advance

1 answer

0 votes
Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 14, 2018

Give "create issue" to everyone who needs it in the permission scheme (e.g. role: users).

Use conditions to control the reset (see https://confluence.atlassian.com/adminjiraserver/advanced-workflow-configuration-938847443.html )

Mohamed El Taweel March 14, 2018

Thanks a lot Nic Brough

I created HR Permission Scheme

Close Issues granted to "HR Admin" and "Administrators"
Create Issues is granted to "Anyone"
Delete Issues is granted to "HR Admin" and "Administrators"
Edit Issues is granted to "HR Admin"  
Link Issues is gtanted to "HR Admin"
Transitions Issues is granted to "HR Admin" and "Administrators"
Add Comments is granted to "HR Admin"  and "Reporter
Create Attachments is granted to "Reporter"

 

Should I use the conditions you mentioned or the above is enough to satisfy the requirements

 

Best Regards

Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 14, 2018

You're 99% of the way there.

I think of permissions as having two types - system and workflow, and there's a slight grey area on some of them.  It is mildly annoying that permission schemes present these as though they are the same thing, but it is for historical reasons, and arguably a better interface for admins.

A system permission is one that lets you do something outside the workflow.  This would be things like Edit, Comment, Log Work. move, and even "Create issue" (Personally, I'd move that one into the workflow)

Workflow permissions are things like Close and Resolve.  These, in themselves, actually do absolutely nothing (they used to, in Jira 1, but the don't any more).  They rely on your workflow to have "conditions" that use them.  Conditions like "Only people with 'close' permission can use this transition" - I think you have got this right, but you should check your workflow actually has that condition on it at the right point.  (If it is one of the off-the-shelf workflows, it should have it automatically)

The grey area ones are "resolve" (it is a workflow permission, but also controls who can edit the fix version in some places), and "transition" (this allows or blocks access to all transitions, fixing a long-standing bug where people who could not even see an issue could still transition it unless your long suffering admin added a condition like "only users in role X" to every single transition in your entire system)

Mohamed El Taweel March 14, 2018

Thanks a million, Nic Brough

Suggest an answer

Log in or Sign up to answer