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.
I saw this in a post:
Without Addon (only link, content of the ticket is not included):
But I don't see a menu item to create an event.
Also, I wonder if an automation would work, if there were a way to use an email address that automatically selects the assignee.
@Phil Bustin hi!
Although @Magdalena Zhisheva is a correct answer, Jira has a built in notification scheme which allows you to inform users within a project role or a group. The answer that you've found is the proper one, but keep in mind that all new software projects have a default notification scheme (if not "shared" is not selected). With that in mind I would advise you to:
If it's not present then
Sounds good, but the automation allowed me to select specific statuses for which I want the assignee notified, that I would think a notification scheme can't do.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It can, if you create a new event called e.g. "Notify only Assignee" and assign this event to the transitions where you want the assignee to be notified. Then on the notification scheme you add to the new event only the assignee, and from the "Issue Update" event you remove the assignee. It's not the best practice imo to remove the assignee from the update issue event, but you can do it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It would appear that the condition in the automation does not work when the issue is transitioned by an automation; only by the user. For those statuses, I inserted the notification into the existing sub-task automation that triggers the parent transitions.
Since the sub-task automation captures the parent state before the automation transitions the parent, I hard-coded the target state in the email Subject as a workaround.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.