Angélica Luz Atlassian Team

Hi Emma, There was a bounce due to the same error again: 550: 550-5.1.1 The email account that you tried to reach does not exist. Please try 550-5.1.1 double-checking the recipient's email address for typos or 550-5.1.1 unnecessary spaces. Learn more at 550 5.1.1 https://support.google.com/mail/?p=NoSuch... - gsmtp For…

Hello @Bentsion Berg, Thank you for reaching out to Atlassian Community! If the ticket was moved to another project and the Request type wasn't filled or if the participant was not listed on the ticket, it means that they didn't have permission to comment on the ticket, so it was expected that a new ticket was created.…

Hello @Todd Foley, Thank you for reaching out to Atlassian Community! The answer is still valid for Jira Service Management projects, but now it's possible to migrate single company-managed Software and Business projects between Cloud sites. For more details about the feature and steps, please check the documentation…

Hello @Cristiano Schwening, I removed the bounces for both domains. For the .net domain, it returned 19 affected email addresses and for the .br it was 6. 550: 550 [internal] [oob] The recipient is invalid. 550: 550 5.4.1 Recipient address rejected: Access denied. AS({hex})…

Hello Travis, Welcome to the Atlassian Community! When creating tickets via the mobile app, it's not possible to select a Request type. On ITSM projects, the categories, such as Service requests rely on Request types, so if the field is empty because it was created via the mobile app, it won't show correctly under the…

Hello @Carolin Jonietz, Thank you for reaching out to the Atlassian Community! When mentioning customers, they receive a system notification, and the link to view the issue points to the agent view. This is a known bug and you can find more details on the ticket below: * "View Issue" link redirection from mention…

Hello @Nicole Downes, Thank you for reaching out to the Atlassian Community! On Business projects, the board doesn’t have the same settings as on a Jira Software project, so by default, the tickets should be removed from the board 14 days after the resolution has been set. There is a feature request suggesting improvements…

Hello Emma, I'm doing good, thank you. Hope you are too! There was a bounce on your email address due to the same error and I removed it: 550: 550-5.1.1 The email account that you tried to reach does not exist. Please try 550-5.1.1 double-checking the recipient's email address for typos or 550-5.1.1 unnecessary spaces.…

Hello Annie, Welcome to the Community! Reviewing the steps mentioned in the other post, I believe that the documentation is outdated because is different from what they have on our marketplace. * https://support.google.com/chat/answer/9575067 The best option, in this case, is to reach out to their support for further help…

Hello @Khalis Khalili, Thank you for reaching out to the Atlassian Community! Checking your email here, it didn’t return any bounce that we could remove, but Atlassian emails are being rejected. Please, share these errors with the mail server admin and also ask them to whitelist our Domain and IPs: IP addresses and domains…

Hi @Wojtek Pilwinski, Thank you for reaching out to the Community! The bugs I mentioned in my previous response were already closed. For more information, please check the description of this ticket: * New Issue View does not respect Jira's Advanced Settings Date Format Now, there is a new feature request suggesting…

Hello @Yatish Madhav, The steps I mentioned are for team-managed projects where the Issue type and Request type are linked by default. On team-managed projects, the Request type will never be empty due to that. If the Request type is empty on your tickets, it means that you are using a company-managed project, so in this…

Hello Jaqueline, Thank you for reaching out to the Atlassian Community! When customers can see the ticket via the portal but are unable to view the details, it means that the request type is empty. From the agent view, please, select a valid request type and then customers will be able to view the details of the tickets.…

Hi @Pedro van den Einden, Welcome to the Atlassian Community! Maybe the account you are trying to use is already associated with an Atlassian ID, so that’s the expected email notification to receive. If that’s the case, you can follow the instructions of this article: How to change your Atlassian account email address Kind…

Hi @Felicia Rodrigues, Thanks for reaching out to the Community! It’s not necessary an add-on to use dynamic fields anymore. The add-on suggested was ProForma, but now it’s part of Atlassian and available in Jira. In case you never used the add-on when it was a separated product, you can then find it on Project settings >…

Hello @Karsten Schulze, Thanks for reaching out to the Community and for testing the possibilities I mentioned. Other than those, if specific customers are not receiving notifications it can be some block that we can remove. For example, if the inbox was unavailable at some point and the notification was sent it then was…

Hello @Fabio Marastoni, Thanks for reaching out to Community! I checked internally for updates regarding this feature, but currently, there is no news to share. Once the feature starts being worked on, our product managers will update the ticket. You can also find the features that will be implemented soon on our roadmap:…

Hi @Sarah Daily, Thanks for reaching out to Community! Yes, on the original ticket it will show the linked issue as well as on the linked issue, it will show the original one. Kind regards, Angélica

Hi @Maruf Mamurov, Thanks for reaching out to Community! The satisfaction survey only works via email, it's not possible to add the survey on the ticket in the customer portal. * Enable customer satisfaction survey on the Customer Portal In line with our Feature Request Policy, we'd suggest you vote for the feature ticket…

Hello @The Trinh, Welcome to the Community! Checking the email on our tools shows that notifications from notifications-noreply@bitbucket.org are being delivered correctly. Maybe someone else already removed the bounces from the email address before I checked. Please, take your time to test and let us know how it goes.…

Hello @Bhavana A, There was a bounce on your email address due to the same error: 550: 550-5.1.1 ...@... Recipient address rejected: ... in virtual alias table 550 5.1.1 Please see http://support.mailhostbox.com/email-{hash}-{hash}/ for explanation of the problem. The notifications should be delivered normally now. Kind…

Hello @Rodolfo So, Thank you for reaching out to the Atlassian Community! The resolution for this case was to sync the repositories. The option should appear after clicking on Get started on the Github add-on from the Apps > Manage apps. Integrate with GitHub Kind regards, Angélica

Hi @GAN PEOY JOO, Welcome to the Community! There was a bounce on the email address due to the following error: 550: 550 5.4.1 Recipient address rejected: Access denied. AS({hex}) [SG2APC01FT0012.eop-APC01.prod.protection.outlook.com] I removed it and the user should receive notifications now. Kind regards, Angélica

Hi @Marcel D, Thanks for reaching out to the Community! The Customer invited notification can’t be translated at the moment. Customers receive notifications based on their preferred language, but for the invitation, it’s not possible to select in what language it will be sent. Translation for Customer invited notification…

Hi Paul, I checked the entire domain and it returned 420 affected email addresses due to the same error. I removed the blocks from all, so the email you mentioned and also other users should receive the notifications normally now. Kind regards, Angélica

Hi Martin, Welcome to the Community! On the announcements it’s only possible to add links, so you can add this document to Google Docs, for example, or even Confluence in case anonymous access is enabled. Kind regards, Angélica

Hi @Paul Gautier, The email was on the suppression list due to the following error: 550: 550-5.2.1 The email account that you tried to reach is disabled. Learn more at 550 5.2.1 https://support.google.com/mail/?p=Disabled... - gsmtp I removed this block and the notifications should be delivered now. Kind regards, Angélica

Hi @Krzysztof Mętel, Welcome to the Atlassian Community! Checking Mara’s email address on our tools, it didn’t return any blocks. Further checking, I saw that you created a ticket with our support regarding this and they have already removed the blocks. On our logs, it shows that the notifications are being delivered. Here…

Hello @Tony Bakalenko, Welcome to the Community! I saw that your site is Free, that's why it redirects you to the Community. I removed what was blocking the transfer of the products to another organization on your site and you should be able to transfer now. Kind regards, Angélica

Hello @[deleted], Welcome to the Community! The feature is currently in progress and the last update from our Product manager Joseph was on January 2022: Due to our increased focus on delivering an embedded knowledge base experience in Jira Service Management, we had to delay the start of work on the canned responses…