We use Tempo Timesheets to record user time marking. This question, however, is not related to Tempo, and more towards JIRA itself and permissions.
We tried setting permissions in a Vacation project such that administrators are able to create the tickets, but users cannot create tickets in this project. We set the Permission option for "Work On Issues (Ability to log work done against an issue. Only useful if Time Tracking is turned on)" to only being accessible to jira-administrators and managers. But what happened is that even administrators could change or modify the tickets on behalf of their employees. Our administrators are ALSO part of the group "jira-users".
My question is: what should the permissions be set to in this project, such that users cannot create or edit the ticket but administrators can? Related question: should "jira-administrators" also be part of the "jira-users" group? Which supersedes which?
Admins should also be part of the users group - in the default. jira-users is the key to log into JIRA.
But back to your problem:
You could restrict the creation of this projects issues in their workflow.
Set in the create-transition the workflow validator "User in field is / isn't in project role" which comes with workflow toolbox and check assignee = project role administrator. (the project role should just include jira-administrators and project supervisors)
And there you go.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG