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
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.
We would like to disable the comment option after 5 days of ticket closure.
We are able to disable comment option using "jira.permission.comment.user" transition property. But we want to allow users to add comment up to 5 days of closure and then after we would like to disable comment option.
Can anyone help in this regard.
Please try Permissions based on Workflow Status
It might be useful to give a few examples here:
You can even use the value as denied when the type is not used. For example, jira.permission.comment=denied
means the comment feature is disabled at this state.
Hi @Madhu Reddy ,
the solution is probably a combination of the two answers already provided:
Disabling comments the way you're describing would fit best using status properties. That said, you'll have to move the tickets to an additional status where commenting is not allowed after being closed for 5 days.
Hi @Madhu Reddy as @Thorsten Letschert _Decadis AG_ commented, one solution is to have two closed status: “resolved” and “closed” ( this last status with property jira.permission.comment.denied=) when an issue is resolved goes to “resolved” and with automation after 5 days in this status automatically transition to “closed” status.