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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


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
Community Members
Community Events
Community Groups

Automation for Jira, you do not have the permission to comment on this issue


I have create some automation on my project.

When the ticket is closed, I need to send an email and insert a comment on ticket.

When the automation try to insert a comment on closed ticket, return:

"Automation for Jira, you do not have the permission to comment on this issue"

1 answer

0 votes

Hi and welcome to the community,

If you check Rule details, is Automation for Jira the actor?

Screenshot 2021-07-15 111356.png

If you look at the permission scheme for the project, does that user belong to a group/role that have the permission to comment?

Yes, the actor is Automation for Jira.

The problem is only when Jira try to insert a comment on a closed ticket..

The other automation, for example for resolution, works correctly and insert the comment.

When the ticket is opened, resolved or another status, Jira can insert a comment on ticket. If the status is closed, Jira can not insert a comment.

Is it possible to create an automation for a closed ticket that create a comment on status closed?

Are you able to comment on closed issues without using automations?

Check the workflow, if you have a property set for jira.issue.editable set to false for the closed status

Like Niels William Porsborg likes this

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events