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,457,939
Community Members
 
Community Events
176
Community Groups

Email notifications being received by original reporter

we previously had a project manager who raised a number issues under a number of Epics that belonged to one project.

That manager has now moved onto a different project. The assignee has been changed but the manager is still receiving email notifications for this particular project. Is that because they are both listed as the Reporter for both the Epic and Issues?

I have since changed the Reporter from the previous manager to the current manager, but do we need to change the Reporter on all the issues too?

3 answers

2 accepted

1 vote
Answer accepted

Yes, you will have to change the reporter for all issues from previous to the current manager. Maybe you can explore doing this via Bulk Update or setup a Jira Automation rule.

If the previous manager still receives an email notification, you may also want to check if the manager may be added as a watcher on any of the issues.

Hope it helps!

Trudy Claspill Community Leader Dec 14, 2022

@Abhay Gupta 

Good point about checking the Watchers field!

Like Abhay Gupta likes this
1 vote
Answer accepted
Trudy Claspill Community Leader Dec 14, 2022

Hello @lindsay_makin 

You will need to review the Notification Scheme(s) for the projects where the issues were created to determine who is receiving notifications for changes to the issues. Often the default Notification Schemes include notifying the Reporter for major changes like Status changes and Edits, but other events may also be generating notifications to the Reporter.

The only way to stop those notifications to that specific Reporter, without affecting notifications to Reporters for other issues in the project(s), is to modify the Reporter value for those issues in the project(s). If you change the Notification Scheme to stop notifying the Reporter, that impacts all issues in the project.

Thanks for the advise

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS

Atlassian Community Events