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.
Hi....All,
In the prior version of Tempo, we were able to filter out closed/released tickets from the tempo, so that developers do not enter time against it. After the upgrade to the new version, this option seems to be missing.
Is there a way to fix it?
Regards,
Praveen
Have you seen the tempo documentation about configuring the options? This documentationhttps://tempo-io.atlassian.net/wiki/spaces/THC/pages/292978789/Configuring+Logging+Time+Options+-+Tempo+Server serves for tempo 9.x - 15x.
If your version doesn't fall into the above period, then try to add the workflow property on your closed status "jira.permission.work.denied"
You can read more here https://confluence.atlassian.com/adminjiracloud/workflow-properties-776636709.html
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.