Gor Greyan Expert

Hi @Michael Levinson Welcome to the Atlassian Community! For tracking upcoming changes, I would use Atlassian's Cloud release notes / What's new across Atlassian as the primary operational source rather than trying to build the monthly release from Community posts. Atlassian is actually moving the existing weekly Cloud…

Hi @Corey K Welcome to the Atlassian Community! This can be corrected without undoing the completed sprint. When a sprint is shared across multiple boards, the board from which you complete the sprint does matter for the rollover of incomplete work items. Atlassian documents that only incomplete work items belonging to the…

Hi @Vinod M Welcome to the Atlassian Community! Jira will try to identify an existing local user based on the configured Username mapping in the SAML authentication method. By default, this is commonly - ${NameID} Jira evaluates that value from the SAML assertion and matches the resulting value against the existing Jira…

Hi @Admin Jira SQS Welcome to the Atlassian Community! If you've already added the new credit card but the subscription/invoice is still associated with the previous card, I would first check which payment method is linked to the relevant billing profile/subscription. In Atlassian's improved billing experience, you can go…

Hi @Alex Astafiev Welcome to the Atlassian Community! Atlassian has a troubleshooting guide specifically for verification codes that are not received. https://support.atlassian.com/atlassian-account/docs/login-issues-related-to-identity-verification If the emails still don't arrive after those checks, you'll likely need to…

Hi @Harshad Prajapati Welcome to the Atlassian Community! As @Arkadiusz Wroblewski mentioned, there isn't a native Jira report/CSV export that provides the Sprint/Fix Version change history in the format you've shown. The REST API is the best native option. The issue changelog contains historical field changes, including…

Hi @Jurgen Boer Welcome to the Atlassian Community! I have checked the Atlassian Status page; currently, no ongoing incidents are reported. https://status.atlassian.com/ I suggest waiting a bit and checking the status page to see if any incidents are reported.

Hi @Seb Coursol Welcome to the Atlassian Community! I have checked the Atlassian Status page, currently, no ongoing incidents are reported. https://status.atlassian.com/ I suggest waiting a bit and checking the status page to see if any incidents are reported.

Hi @Ordinet Workflow Welcome to the Atlassian Community! Atlassian currently doesn't support merging two Atlassian accounts, so these will remain two separate accounts. There is an existing feature request for this: ID-240. https://jira.atlassian.com/browse/ID-240 In your case, the safest approach would be to keep the…

Hi @Youmna El-Baz Welcome to the Atlassian Community! Could you provide a little more detail about what you're trying to achieve by “mapping the features”?

Hi @Alex Nicholson Welcome to the Atlassian Community! According to Atlassian's documentation, the Clear Done work items option should still be available for team-managed Kanban boards. Still, there is an important condition, that Sprints must not be enabled for the space. Atlassian documents that if you don't have Sprints…

Hi @Sara Phillips I agree that this is particularly difficult when the instance contains multiple fields with identical or similar names. I have found this suggestion, which was closed as Won't Fix. https://jira.atlassian.com/browse/JRACLOUD-74117 The request below that is still open asks Atlassian to prevent duplicate…

Hi @DRIZ Welcome to the Atlassian Community! If you're referring to the phone number used for two-step verification (SMS) on your Atlassian account, you can update it from your Atlassian account security settings. https://id.atlassian.com/manage-profile/security

Hi @Anders Øyvind Urke-Sætre Happy to help!

Hi @Anders Øyvind Urke-Sætre Welcome to the Atlassian Community! At the moment, Atlassian manages Rovo and its AI capabilities primarily at the organization level, so there isn't currently a built-in option for individual users to opt out while leaving AI enabled for everyone else. This is something that has already been…

Hi @Mugisha Irakoze Welcome to the Atlassian Community! From time to time, Atlassian will need to carry out planned maintenance. You can find details here. https://support.atlassian.com/organization-administration/docs/what-is-a-maintenance-window/

Hi @Hapidz Daulah Nurisman Did you submit an Atlassian Support ticket via the Portal, or just make this post here?

Hi, dear @Jakob Berner Strømberg Happy to help you!

Hi @Ait Benhida Fatimaezzahra Welcome to the Atlassian Community! I tried to do the same on my side, also on my managed account, and it succeeded on my end. I am not aware of another place where it can be changed. I think you can raise a request to Atlassian Support to figure this out.

Hi @roei_Taig Welcome to the Atlassian Community! It isn't currently an Atlassian setting to hide or disable the Rovo Chrome extension for users while keeping Rovo available in Jira or Confluence. If your goal is to prevent employees from using the browser extension, the recommended approach is to manage it through your…

Hi @Susie Lee Welcome to the Atlassian community. You must cancel all your product subscriptions first, then try to delete the account. https://support.atlassian.com/subscriptions-and-billing/docs/cancel-a-subscription/ Or you should make another user the billing administrator and have that person remove your Billing…

@Soham Tare Happy to help, dear!

Hi @Jakob Berner Strømberg Welcome to the Atlassian Community! Since you've successfully signed in, I suggest reconfiguring your two-step verification. You can do this from your Atlassian account security settings. https://id.atlassian.com/manage-profile/security From there, you should be able to set up a new authenticator…

Hi @Soham Tare Welcome to the Atlassian Community! The validator should be written as a Jira Expression, not as a Groovy script. You can try the following script. issue.customfield_XXXXX != null && new CalendarDate(issue.customfield_XXXXX) <= new Date() .plusHours(5) .plusMinutes(30) .toCalendarDateUTC() Replace…

Hi @wammo studio Thanks for confirming. That's certainly interesting. I think the next step would be to raise a support ticket with Atlassian. They can verify whether this occurred during site provisioning or whether there was an unexpected inconsistency in the work type configuration. If Support confirms it's a product…

Hi @wammo studio The change from Issues to Work items is expected and is part of Atlassian's ongoing terminology update. https://support.atlassian.com/jira-software-cloud/docs/what-is-a-work-item Regarding the Story icon, Atlassian has been gradually rolling out a refreshed icon set across Jira Cloud. I checked, but it is…

Hi @Maité Sedeyn As far as I'm aware, the limit of 100 Categories is currently a hard limit and isn't configurable. It was introduced as part of Atlassian's Cloud data limits and guardrails, and there isn't an administrator setting to increase it. I also wasn't able to find an existing JAC suggestion requesting an increase…

Hi @Suporte JRetail As @Thanasis Nikolaou mentioned, the accountId must be the Atlassian Account ID rather than the user's email address. The following JSON should work once you replace <accountId> with a valid Atlassian account ID: { "update": { "Request participants": [ { "add": { "id": "<accountId>" } } ] } } 

@Mariam Hovhannisyan Hi Mar jan, We're seeing very similar behavior in our Jira Data Center environment as well. It may be worth checking whether there are any SMTP/Exchange throttling policies beyond the Receive Connector MessageRateLimit that could affect client submissions. We are planning to update the version to the…

Hi @Hakan AKIN Great! Also, kindly ask you to accept the answer if it helped you.