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.
How?
Alexander Eck (Tempo) Mar 6, 09:11 UTC Marie, Best regards, |
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.
Hi, I'm also looking for such an option. I solved the issue by adding jira.permission.work.denied to all states in the Epics' Workflow but Tempo does not evaluate this field.
Please consider implementing this feature for Tempo Timesheets.
Thank you.
Tobias
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Alexander Eck (Tempo) Mar 8, 09:57 UTC Marie, Best regards, |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Alexander Eck (Tempo)
Mar 3, 10:12 UTC
Marie,
this is not an option in Timesheets. We can only restrict JIRA project wise.
Thanks
Best regards,
Alexander
Tempo
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.