Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,556,620
Community Members
 
Community Events
184
Community Groups

Disable comment on a closed issue after 5 days

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. 

Thanks

Madhu

3 comments

KAGITHALA BABU ANVESH
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Jan 15, 2021

Hi @Madhu Reddy ,

I'm unable to get suitable "Action" for disabling the Comments section. may be you raise a concern to Automation for Jira if you using.

 

image.png

 

Or 

 

I've seen some other community members mentioned by using script runner behaviors there is a possibility.

@Madhu Reddy 

Please try Permissions based on Workflow Status

It might be useful to give a few examples here:

jira.permission.comment.group=some-group
jira.permission.comment.denied=
jira.permission.edit.group.1=some-group-one
jira.permission.edit.group.2=some-group-two
jira.permission.modifyreporter.user=username
jira.permission.delete.projectrole=10000
jira.permission.subtasks.delete.projectrole=10000


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.

Thorsten Letschert _Decadis AG_
Marketplace Partner
Marketplace Partners provide apps and integrations available on the Atlassian Marketplace that extend the power of Atlassian products.
Jan 22, 2021

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.

Cheers
Thorsten

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.

Comment

Log in or Sign up to comment