Eric Zheng_x0wq2i Atlassian Team

@Rick Westbrock That's awesome! Having an agent help with follow-ups is exactly what we're looking to provide better support for next. 

Great to see all the comments and discussion here! Let me try to address some of the themes. What the Jira Triage Agent does: This agent's job is to help take the manual work out of assessing and making decisions on what to do with incoming, unplanned work. It will read the full context of the work item, find how similar…

Thanks for your patience everyone. We have just brought back end-user controls to turn email notifications on/off for when you're the assignee or reporter of an issue. You can find these changes in your Jira Notifications settings page. Eric Product Manager, Jira

@Pasquale Laviano : It's not possible to add Apps as its own tab right now, but this is something we're looking into. Stay tuned for further updates soon. @Muharrem Bilgin : We haven't considered global configuration of default nav settings for all projects yet, could you share more detail about what you'd be customizing,…

Hey folks, First of all, we apologise for the inconveniences caused by this change and for not addressing your comments sooner - your feedback is always valuable to us and we strive to be better at closing the feedback loops. We are working to bring back some of the controls used to define notifications based on your…

Hey @John Funk ! The "default view" in this context refers to the primary screen that users will land on when navigating to a project. Previously, the Board view was the fixed default for every project, but with this change, project admins can change this to either the Summary, List, Board, Timeline, or Calendar views.…

Thanks for the feedback @Walter Buggenhout and @Marion Richardson. We hear you and I can share that we do plan on bringing some new customisation to the top tab navigation soon. Stay tuned for upcoming announcements at our Team 24 event! Cheers, Eric Product Manager, Jira Work Management

Hey @John Funk thanks for sharing your feedback. There is no way to turn this off, however, we do acknowledge your concerns and want to assure you that we're continuously monitoring feedback and usage metrics to make necessary improvements to this experience. 

Hey there! I'm Eric, Product Manager on the Jira Work Management team. As you've observed, the hierarchy view is not preserved when filters are applied today. But I'd love to learn more about your specific needs an dhow you envision this working with your projects. Please let me know if you'd be willing to share more about…

@Haddon Fisher Yes this implies that users can opt-out of notifications. I understand the concerns here and am completely aware that there are teams who rely on the notifications sent from notification schemes. While it's true that the current setup allows you to prevent certain notifications from being sent, this control…

Hey @S Fong , could you elaborate a bit more on what you're after? It sounds like you're describing project notification schemes which Jira Admins can configure to control who to send the notifications to. But ultimately, this new feature is to give end users the ability to apply an additional filter. Happy to jump on call…

Hey @Haddon Fisher, the initial scope is to just show the ones that had attempted to be sent but failed due to whatever reason.

Hey @Haddon Fisher , we are exploring this feature request to provide a log of Jira emails which is aimed at providing admins with greater visibility over the emails that have failed to deliver. If this tool is something you'd be interested in, I'd love to chat! Please feel free to book some time in via my Calendly:…

@Majken Longlade Hey, no this does not replace notification schemes. The admin notification helper tool is a seperate functionality that was used to troubleshoot email notifications. There is more context on what this is in Jira Admin Helper.

@Matthew Challenger We primarily wanted to speak with Jira Software admins first, but this change will also apply to Jira Service Management and we'd love to chat with you too!

Hey everyone, in case you missed it, we have re-opened the survey :) 

Hey @Kelley R , only those APIs that deal with notification schemes and updating personal preferences are affected. I look forward to seeing your participation!

That's great feedback, thanks for sharing and voicing this @Shaunty, we hear you! We don't have plans to support the suggested ideas for this particular Early Access Program, however, we are aware of the need to address these other problems and we're actively looking to prioritise these over the coming months. If you're…

@Haddon Fisher unfortunately we're not able to share a full definitive tier list at this time as it's subject to change, however, as it is right now, users won't be able to configure notifications for issue create events. I'd love to hear more about your feedback either through the EAP, or you can message me at…

Hey @Haddon Fisher , sorry I'm not sure if I understand the question, what are you referring to when you say tiers in the context of this EAP? Unless Jira users have gone and configured their notification settings (shown in the preview above), they shouldn't receive any less email notifications than usual. Hence, we aren't…

@Éric Dagenais Since this new experience required us to change the notification model, there may be some APIs for Notification interactions that won't be supported during this EAP. This would affect you if your instance is using a marketplace app that has Jira notification configuration support. 

Hey @Frank Dutenhöfer , this should already be activated for all Jira cloud instances. If you're not seeing any changes, then it's likely: * It's an email for a critical update (being mentioned or assigned on an issue). These type of emails will always be sent through immediately to ensure you can respond immediately to…

Hey @Alberto Misrachi, there currently isn't a way to configure batching settings for Jira emails. You may be referring to Confluence daily digest emails - if this is a feature that you think would be beneficial, I'd love to learn more! Feel free to shoot through a message at ezheng@atlassian.com, and I'd be happy to chat!

Hey @Jesse Brooks , Group notification options will continue to be supported and function as expected. Let me know if you have any further questions!

Hey @[deleted] , As Jesse mentioned above, you can navigate to the Notification Schemes page ("under the settings gear in the top right -> Issues -> Notification Schemes in the bottom left"), and have a look through the schemes that have been set up. Within these schemes, a field will be shown for those who are receiving…

Hey @Davor Fisher, your instance might be using another customisation that doesn't have batching support yet. Feel free to shoot through a message to my email at ezheng@atlassian.com and I'd be happy to investigate this further with you!

Hey @Davor Fisher , email batching is available for most emails including those using the Atlassian native email jira@domain, as well as those with a customised email domain. For more details on how batching works, you can refer to this article Jira Cloud Email Notifications are Delayed. I'd also love to chat more about…

Hey @Yatish Madhav , Happy to answer your questions! * There is a rolling 3-minute time window within which the batching is done, with a maximum threshold of 15-minutes. * At the moment, it's not possible to edit the header and footer of the email notifications. If this is something you're interested in, I'd love to chat…