Andy Heinzer Atlassian Team

Of course as soon as I posted this, I checked a different user on your domain and found a suppression. I have just cleared this from our side. Try to invite that user again now, and see if that helps. If they are still not receiving this, please let me know the specific user in question. Cheers, Andy

Hi @Micah Kirkpatrick I have not been able to find any email suppressions on our side either to the domain of your email, nor to the gmail account that appears to have been invited to your site. Is there a different email domain that you are using to invite users to your site? Could you share with me the email address or…

Hi @Rusty Sorry to hear about this. It sounds like there is a problem with this integration if you keep seeing this prompt, that should not be happening. I would encourage you to reach out to one of your site-admins about this. The site-admins are able to create a support case for your cloud site in relation to this. They…

You might want to try to follow the troubleshooting steps in https://support.atlassian.com/jira-software-cloud/docs/manage-insights-in-a-company-managed-project/ There is a project permission called View aggregated data, you will need that permission in all the projects where this board can pull issues from. Within that…

Hi @Melanie Hubert I have removed those suppressions, each of those accounts you mentioned had a bounce error with this same message 2023-05-02T11:25:31.000Zd14f625b-5a62-4bbf-8cab-2b7e8029b8af pullrequests-reply@bitbucket.orgl***********@greenware.debounce550 Address invalid (ID:550:1:1 (mi018.mc1.hosteurope.de)) I hope…

I have replied to your other post about this over in https://community.atlassian.com/t5/Jira-Software-questions/Product-Offline/qaq-p/2353052#U2353276

Hi @Amer Amin I can see that your site started a trial of Jira Software standard, and that trial appears to have expired with no payment details on file. I have created a CA ticket on your behalf over in https://getsupport.atlassian.com/servicedesk/customer/portal/35/CA-2341585 I see that you have another technical case…

@Madhu sudhan I have remove the suppression from our side. The SMTP bounce message was the same: 550-5.1.1 : Recipient address rejected: User unknown in virtual alias table 550 5.1.1 Please see http://support.mailhostbox.com/email-administrators-guide-error-codes/ for explanation of the problem.

Thanks for the update. Sorry that this solution doesn't meet the need here. However trying to use a scheduled trigger that can search JQL isn't really an ideal approach here. That is because the actions taken in such an automation rule will have to apply to all the JQL search results equally. Since we want to apply a…

Hi Sam, I am not certain it is still possible to revert to the legacy editor, but I created a support case on your behalf to see if our team can still do this. You can access this over in https://getsupport.atlassian.com/servicedesk/customer/portal/23/JST-871340 Regards, Andy

@Morten Stensgaard Not exactly. This original post was in regards to Jira Server, which implies that the administrators potentially have direct access to the SQL database that Jira uses. Jira Cloud doesn't provide SQL access for customer, so the answers above don't really apply to Cloud. Automation might be able to help,…

Hi @James Knight I created this support case on your behalf over in https://getsupport.atlassian.com/servicedesk/customer/portal/23/JST-870977 I expect that our Cloud support team will want to take a closer look at your environment to better determine a way to address this problem. Regards, Andy

Thank you for the report and the email header, I have referred this to our abuse team. Sorry for the inconvenience. Andy

If you updated the manifest, you do still need to upgrade the app for these scope changes to take affect. More details in https://developer.atlassian.com/platform/forge/add-scopes-to-call-an-atlassian-rest-api/ If that doesn't help, you might want to reach out within our developer community over in…

Hi @Jos van der Sanden I found another user on your domain that appears to have been getting suppressed. The first SMTP rejection message was 550 5.4.1 Recipient address rejected: Access denied. AS(201806281) [DBAEUR03FT059.eop-EUR03.prod.protection.outlook.com 2023-04-21T13:47:12.547Z 08DB41BB4FF6D663] We have cleared the…

Hi @Martina Bubalova I can see that there have been a number of messages sent to your mailbox that have bounced recently. The SMTP response was: 550 The sending IP (156.70.150.12) is listed on https://spamrl.com/. Please resolve this and retry. I have reached out to my mail team for additional help here. As it appears that…

I have created a support ticket to facilitate this transfer. It can be accessed over in https://getsupport.atlassian.com/servicedesk/customer/portal/23/JST-869180 Our support team will need to confirm that we can disable the new admin experience with your consent to be able to make this transfer. Once that has been…

Hi @Marcelo Ignacio Cid Abud You can create a new rule to manage existing issues and update them with new values for this number field. Note that I changed the trigger to happen on Issue updated. Also there is a conditional to check that this field is currently empty. Once those two are there I adjusted the JQL query to…

Hi @Scottie Brimmer At the moment, Atlassian Analytics doesn't directly support this data set, as it comes from a Marketplace vendor that stores its data separately from other Jira issue data. That said, we have seen interest in others for this kind of integration. As such our team has created this feature request…

Those issue were created months ago, so the automation trigger of when issue is created won't be able to change those now. In that case, there are a couple of different ways to go about it. One approach would be to create a new automation rule. You could copy the existing rule, but just change trigger from "Issue Creation"…

When using a Forge app, you will need to include the specific endpoint scopes. See also https://developer.atlassian.com/cloud/jira/platform/rest/v3/intro/#forge-apps For Forge apps, REST API scopes are used when authenticating with Jira Cloud platform. See Add scopes to call an Atlassian REST API for more details. The URIs…

Hi JP, The Support Entitlement number of SEN-10785500 is specifically for Confluence Server. As such, you won't be able to use this license for our Jira Server or Jira Data Center products. That specific license is only for Confluence Server. Perhaps you have a different SEN for Jira Server, however from what I can see it…

Hi, When automation rules have the scope of more than a single project, it requires the user be a Jira Administrator to manage these. This is because those rules are beyond the single project scope now, and are expected to be managed in the global automation page. This is explained in…

Hi @Jean Paul Tatou From looking at your account, I only see an existing license for Confluence Server and a trial license for Jira Data Center. You mentioned seeing this error for an existing license. Could you please let know the SEN of that license itself? Perhaps with that information I can confirm what your license…

Hi @Arifur Chowdhury I am not certain that we will be able to recover this data. it appears that the site was in an evaluation of Jira Software. Evals only have a 15 day data retention period per https://support.atlassian.com/security-and-access-policies/docs/track-storage-and-move-data-across-products/ I suspect this data…

Hi Marco, I think I understand what you are trying to do here, I have put together an automation rule example, that I think might meet your criteria here. Check it out: In my example, I have a numeric field called NewNum. My trigger is upon issue creation. This is also a project specific automation rule (not a global or…

Fabio is correct. In theory it should be possible. But that comes with a big /should/. The operating system has never been the focus of a supported platform for Jira. Frankly Jira doesn't care what the base operating system is. Instead the Java environment has been far more important historically. This is because Jira is a…

It usually happens because the destination mail server has rejected the message for some reason. Our logging here only goes back 30 days, and I can't see back far enough to see the original reject message. But in other cases it tends to happen when the mailbox is disabled or unable to accept mail. If that happens, the SMTP…

Hi, I see that you have a support ticket in https://getsupport.atlassian.com/servicedesk/customer/portal/35/CA-2316954 This is the correct channel to address and resolve this. Someone from the CA team will be able to help you in regards to this issue. Cheers, Andy

Sorry to hear about this problem. I have created a support case on your behalf over in https://getsupport.atlassian.com/servicedesk/customer/portal/23/JST-866743 Regards, Andy