Notification settings changes in March 2024 made things worse

[Tomáš Vojvoda]

Hello,

I'd like to suggest that the changes to notification settings in Jira Software which happened sometimes between 02 and 03/2024 for which I found no announcement in monthly recap emails, made things worse.

I have just summarize the change for our company like this:

They have switched the logic from "choose the relation to tickets you want to get notifications for" to "choose the activity on tickets you want to be notified about (and we determine which tickets are related to you ourselves)"

The issues I have with this change:

1. You did not notify us about this change of logic, I see it more important to notify about change than about any new feature.
2. Everyone (namely ticket creators like Project/Product owners, Architects, Analysts) will get notifications for all tickets they created (for others) -> SPAM
3. Why did you go from 1:N to N:1 instead of N:N ? Why take away the option for a user to choose which tickets are relevant to him/her? -> this is my suggestion, give us back the ability to determine which tickets we want to get notified about for ourselves.

Kind regards,
Tomas

[Trudy Claspill · Accepted solution]

Hello @Tomáš Vojvoda 

You may want to provide your feedback in comments in the article posted about the changes.

https://community.atlassian.com/t5/Jira-Software-articles/Take-control-of-your-inbox-with-new-ways-to-manage-Jira/ba-p/2637342

[Tomáš Vojvoda]

@Trudy Claspill Thank you for the Tip, I did not know about the article, .. still my goal is to have a change request created and this is the only way that was suggested by Atlassian itself to achieve that (I guess I would need to wait for some Atlassian representative to notice this and react.)

[Trudy Claspill]

The best way to get a product suggestion directly to Atlassian, since you are on a paid plan, is to ask your Jira Administrators to open a support case about it directly with Atlassian.

Commenting on that article also will notify the article author, who is an Atlassian Team member and could also create a suggestion directly in their backlog.

Those options may get a more timely response then hoping an Atlassian Team member will notice your post in the user community Questions board. ;-)