Alexis Robert Community Champion

Hi @Martijn Lukaart , There is currently a global incident on many Atlassian services we are also seein the same errors. This is a widespread issue, we have created tickets to the Atlassian Support. You can check https://status.atlassian.com/ in a few minutes to follow progress on a fix. Let me know if this helps, --Alexis

Hi @Anoob , many people are impacted and see the same errors on their sites. This is a global issue, we have created tickets to the Atlassian Support. I would advise checking https://status.atlassian.com/ in a few minutes to follow progress on a fix. Let me know if this helps, --Alexis

Hi @Martijn Lukaart , I'm also seeing the same errors on many customer sites. This is a global incident, we have created tickets to the Atlassian Support. I would adivse checking https://status.atlassian.com/ in a few minutes to follow progress on a fix. Let me know if this helps, --Alexis

Hi @Waseem Haddad we are also seeing the same errors on many customer sites. Looks like a widespread issue, we have created tickets to the Atlassian Support. I would adivse checking https://status.atlassian.com/ in a few minutes to follow progress on a fix. Let me know if this helps, --Alexis

Bonjour @Dorothée Fouissac , à première vue je dirais que c'est peut être un problème d'index suite à la migration : il est possible que Jira prenne quelques heures à remettre correctement en ordre dans sa base de données les tickets migrés. Si le problème persiste 24h après la migration, il faudra par contre ouvrir un…

Hi @Rajkumar Dalwai , yes I also have the same errors on many customer sites. I believe this is a global, we have created tickets to the Atlassian Support. I would advise checking https://status.atlassian.com/ in a few minutes to follow progress on a fix. Let me know if this helps, --Alexis

Hi @Zakhir Mamedov , we have the same problem on many customer sites. This is the same for many people, we have created tickets to the Atlassian Support. I would advise checking https://status.atlassian.com/ in a few minutes to follow progress on a fix. Let me know if this helps, --Alexis

Hi @Carol Higgins we are seeing the same errors on many Atlassian customer sites. Probably a global issue, we have created tickets to the Atlassian Support. I would advise checking https://status.atlassian.com/ in a few minutes to follow progress on a fix. Let me know if this helps, --Alexis

Hi @V2C SUPPORT Looks like this on many customer sites. This looks like a widespread issue, we have created tickets to the Atlassian Support. I would advise checking https://status.atlassian.com/ in a few minutes to follow progress on a fix. Let me know if this helps, --Alexis

Hi @Neil de Hoog same for me here on many customer sites. Looks like a globalissue, we have created tickets to the Atlassian Support. I would advise checking https://status.atlassian.com/ in a few minutes to follow progress on a fix. Let me know if this helps, --Alexis

Hi @James Fama , I'm also seeing the same errors on many customer sites. This is a widespread issue, we have created tickets to the Atlassian Support. I would adivse checking https://status.atlassian.com/ in a few minutes to follow progress on a fix. Let me know if this helps, --Alexis

Hi @Olivier Ruis Perso , if you do not find the setting as shown in the documentation, this might be because you're not eligible to Atlassian Intelligence : right now this is a feature available on Premium or Enterprise Plans. Can you check this ? You might be on the Standard or Free plan, that would explain why this is…

Hi @[deleted] , this is completely transparent for the users, as nothing changes for them until you add them to a policy that forces SSO. It's all done on the backend as Access will link users coming from Entra to the local directory. --Alexis

Bonjour @Christophe Grosseuvre , ce genre de fonctionnalités n'est pas disponible de base dans Jira Software ou Jira Work Management. Il vous faudra par exemple Jira Service Management pour avoir accès aux Forms qui permettent des formulaires dynamiques. Sinon, il faut forcément passer par un addon qui ajoute ce genre de…

Bonjour @Pauline AWAD , pour la question sur le lien vers le ticket, tu peux tout simplement utiliser ce format : <a href="{{issue.url}}">{{issue.key}} - {{issue.summary}}</a> C'est du HTML, et ça permettra d'avoir un joli lien qu'on peut cliquer directement depuis l'email. --Alexis

Hi @Kasey C , you can have a look at Atlassian release notes here : https://confluence.atlassian.com/jirasoftware/jira-software-9-12-x-release-notes-1319575972.html There is a section that lists all main changes since the last LTS, so that will give you the information you're looking for until version 9.4. Then, you can go…

Hi @[deleted] , happy to answer your questions here. * The mapping between existing users and users coming from Azure AD is done automatically by Atlassian Access, using the email address as a unique key. So, if your users have the same email in Azure AD and their Atlassian account (that should be the case) then it's…

Hi @Creative Ideas , I would try using a different expression to extract Text2 from your example. Can you try this : {{issue.Description.substringAfter("Device").trim()}} Let me know if this helps, --Alexis

Hi @Server Room , as far as I can see it might be because of permissions granted to the Jira user on newer Postgre versions. You can look at the suggested solution in this post : CREATE USER jira WITH ENCRYPTED PASSWORD 'supersecure123'; -- since postgres 15 (before db creation) GRANT ALL ON SCHEMA public TO jira; -- now…

Hi @IT SCS , you can easily upgrade your Jira instance by following this guide : https://confluence.atlassian.com/adminjiraserver/upgrading-jira-applications-938846936.html You can also find the latest version to download on this page : https://www.atlassian.com/fr/software/jira/update I would recommend using version…

Hi @Deepika.Kanaparthi , with Jira Cloud versions, you do not have access to the database. This was only possible with the on-premise version (Server or Data Center). The proper way to do what you're asking is actually to use Jira APIs…

The JQL to search for flagged issues is the following : "Flagged[Checkboxes]" = Impediment The JQL to check for issues that are in open Sprint : Sprint in openSprints() Let me know if this helps, --Alexis

Hi @Ilia Mamontov , yes it is possible to validate that the issue was added after the sprint start date. Here is the full automation for this, I've tested it and it works fine : Let me know if this helps, --Alexis

Hi @Sandra De Pablo , I think your query is almost correct. You should just changed the first "TO" to "FROM" : project = "XXXXXX" AND status changed FROM "TO DO" to "REVIEW" during ("2023/11/07", "2023/11/14") Let me know if this helps, --Alexis 

Hi @Curtis Hill , looks like you're on the right track with the Smart Value to match this label, I'm wondering if maybe this is juste an issue with quotes. Could you try this value instead : {{#issue.labels.contains("EpicImport1")}}{{/}} Let me know if this helps, --Alexis

Hi @Ilia Mamontov ! this feature still exists in Cloud and as far as I know it's exactly the same as Server : you need to right click on the ticket (in the backlog or on the board) and select "Add Flag". This will highlitght it. Here's the documentation…

Hi @Tamir Melamed , this is a bit more complicated than it looks because you need the Smart Value to identify the week number in the label, and then increase it. I have not tested this, but you could try and see if this works for example : "WW" + ({{issue.labels.first.match("WW(\\d+)-\\d+/\\d{4}")[1]}} as number + 1) +…

Hi @Vivek Kumar Aggarwal , yes you can easily create tickets from emails coming in a specific mailbox. This is a standard feature of Jira Service Management, not sure if you are on Data Center or Cloud but both are available : * Data Center documentation…

Hi @lester Kacprzak , switching databases can be very easy or quite complex, all depends on what the source and target environment are like. Basically, if your databases are compatible, you could do a simple database dump and reimport it. Then change Jira settings to use the new database. But there are also more complex…

Hi @Babak Hosseinzadeh , the easiest way to move your automation to a new environment is to export it to a JSON file and reimport it in the target instance. You will need to have Jira admin permissions to do this, as you need access to the Automation global administration page. You can have a look at the documentation here…