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

Closed issue notification

Hello,

My use case it the following,

  1. Once a ticket is closed, if a customer comments on the ticket, none of the service desk agents, watchers should receive any notification. 
  2. Instead, a comment that the ticket is closed and that the user needs to open a new ticket should be commented sending notification only to whoever commented on the ticket.

I've tried using properties, automation, but nothing really satisfies both requirements. Please support. 

1 answer

0 votes
Dave Mathijs
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 15, 2023

Hi @Amali welcome to the Atlassian Community!

Why don't you deny comments on a closed issue via a workflow property instead?

Hi @Dave Mathijs

Thank you for the first suggestion. 

We decided not to do that. Because if our customer replies through email, Jira creates a new issue for the comment which would be confusing both for the customer and our agents. So, we would like to avoid that.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events