You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I have another question / Problem.
How can I limit the possibility of booking time on a ticket depending on the status?
More specifically, we want the Issue to be able to book time only while it is in the status "in Progress" and "in Devolopment".
All others such as open or Done should not be open for boking.
Does anyone here have any idea?
We use Tempo Planner, Structure, JMWE, Script Runner, Automation as addons.
Best regards
You do not need any apps to do this!
If you edit the workflow, you can apply workflow-properties to each step (status). These can override permissions (amongst other things)
Let's say you have a simple single workflow that broadly says "Open -> In progress -> Done" and it is the only one your project uses.
Set the project permission "Can log work on an issue" in the permission scheme to allow all the people who might log time (ignoring the status for now) to be able to log time on the issues.
Now edit the workflow. You'll want to do this twice, once for "open" and once for "done" - open the step up and look for the "properties". You will probably find that there are none to begin with, but if you add:
jira.permission.work = denied
Then you'll find no-one can log work while the issue is in that step/status. Note you might want to look at others, such as edit work log, delete, edit own etc.
See https://confluence.atlassian.com/adminjiraserver/workflow-properties-938847526.html for more and then https://www.j-tricks.com/tutorials/permissions-based-on-workflow-status for the list of options and some good examples.
Hallo @Nic Brough -Adaptavist-
sorry but this doesn't work for me. For some reason my devoloper can still book time on this Issue.
we work on this Version:
Jira Software 8.13.6
do you have any other suggestions or how exactly to configure this setup? From my point of view, I tried all possible ways.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.