Arkadiusz Wroblewski Community Champion

Hello and welcome to the Community @Phillip Horstmeier Yes, but it depends on what you mean by “additional corp domain. Another email suffix, another OU subtree, or a separate AD domain ?

Hello @Avid Izadpanah You must address that directly to Atlassian https://www.atlassian.com/company/contact/purchasing-licensing#/ It's Public Open community forum.

Hello and welcome @David Black Please take a look Here : Not receiving invitation email Quite similar, first check that answer I provided there.

@Marko Miettinen Nothing to thanks 🤠😉 Let us know how it goes.

@Marko Miettinen Poke Atlassian and look what they can do for you. Alternative probably somebody will Flag this post for them. You can try to reach out to Atlassian Support with a no-login option. If you can’t access your account to open a ticket, use this no‑login path: * Visit our support page:…

@Marko Miettinen You on Free subscription I suppose?

Hello @Rebecca Waller This should be possible in Atlassian Analytics. The table to start with is Work item history. That is the one that tracks field changes over time, so it is the right place to check how often an Epic’s Start date changed. From there, filter to Epics and then to the Start date field. After that, you can…

Hello @Marko Miettinen This usually means you are in the wrong Atlassian account, not that the merge failed. When the reactivation list is empty, Bitbucket normally is not seeing the account that actually belongs to that workspace. So check whether you are signed in with the same email/account that had access to it before.…

Hello @Michaella Barringer In this case you need Atlassian. You can try to reach out to Atlassian Support with a no-login option. If you can’t access your account to open a ticket, use this no‑login path: Visit our support page: https://www.atlassian.com/company/contact Select “Pricing, billing and licensing.” Continue…

@merry chriistmas Also please change nickname, it sounds creepy Middle April 😅🤠🤗

Hello @Mikio Okamoto The two entries for the same person are the important clue here. That usually means Jira is seeing two different user records for that email, often one Atlassian account and one portal-only customer. In that case, adding the wrong one to the project role will not give them agent access. Check which…

Hello @Philycia Atlassian have today some accidents, so it will be best when you give it some time and try later. https://status.atlassian.com/ 

Hello @강호진 To add to @Tomislav Tobijas answer, this is a Jira Cloud bug, not something you set up wrong. Atlassian already has a public bug that matches your case very closely: JRACLOUD-97461. It describes the same pattern where Create another keeps the linked value visible on the next create screen, but the next issue is…

Hello @Yeryeong Judy Kim Yes, that is most likely the Free plan limit. Trello counts not only Workspace members, but also guests and pending invites. So even if one person was removed, you can still stay at the limit if another guest or invite is still there. Check the Workspace member list, guest list, and pending…

Hello @Maryam Hakimipour and @Marc -Devoteam- There is currently an incident, and the main impact appears to be on login functionality. https://status.atlassian.com/

@Tomislav Tobijas Actually we had/have multi product incident now. 😢 https://status.atlassian.com/

Hello @Dev E Failure itself are very generic. Try Private Window, clear cookies, another Browser and wait a little. For a shorter period of time, this error shouldn't really worry.

@Terry Argyadiva Yes, your account is active the "Active" status confirms that. Looking at the screenshot, your account currently only has Jira access on the amartha site. Bitbucket doesn't appear in the App access list at all, which means Bitbucket access hasn't been granted to your account yet, it's not just an…

Hello @Yousif Hassan Even with Guard and an external user policy set to Single sign-on, they still go through the generic Atlassian login page first. The Continue with Microsoft option is a separate login path, not your org-specific SAML flow, so there is currently no supported way to force a clean SSO-first experience for…

Hello @Mi CASA Asamblea de Dios Monte Grande @Trudy P Claspill point about inactivity is a good one One more detail stands out from your post, your thread shows Product Admin permission. That matters here, because adding Confluence again is an Organization Admin task, and access to the Billing accounts page is limited to…

Hello @Andrea Daniels Your invoice already shows a Rovo Dev Standard charge. The problem is more likely that access has not been fully applied yet. With Rovo Dev Standard, payment alone is not enough. The site needs to have Rovo Dev Standard active, your account needs to be in rovo-dev-agents-users-<sitename>, and…

Hello @Terry Argyadiva First, have your admin look in Workspace settings → Access management → User Directory. If your account already has some kind of access there, Bitbucket will not send a new invitation email. If you are not there, then cancel any pending invitations across the workspace groups and send a fresh one.…

Hello @Joseph Hortch @Carlos Garcia Navarro is right. request-channel-type is not a value you normally set yourself. Jira Service Management assigns it from the endpoint that created the ticket. Create it through the regular Jira issue API, and it will show as Jira. Create it through the JSM request API, and it will show…

@Tomislav Tobijas Moin Moin Nice diagram. The overall idea looks solid to me. The main thing I would separate here is who is calling the API versus who the request is being created for. On the JSM side, creating a request on behalf of a customer is possible with raiseOnBehalfOf, so the request can still be opened for a…

"I also came Across" @marc -Collabello--Phase Locked- That's SEO Spam (Spamdexing)

@daniel At least theres workaround which you can use. Well, from last year Focus shifted very much around AI.

@Phạm Nam Hiền _VinMotion-KTKPC-MB_ You're welcome. Have great Sunday.

Hello @Sam Stoof Good advice from @Ajay _view26_ . Just to add one practical thing: since you're locked out and can't access the in-app support form, you can reach Loom/Atlassian support directly at support.atlassian.com without needing to be logged in to Loom. That's your fastest path to getting this resolved at the…

Hello @Chris Berry The only part that can skew reports is when the sprint start date/time is left earlier or later than the real start. Atlassian saying that if the start date is set too early, work added later can look like scope creep. If it is set too late, earlier activity can be excluded from reports. Here some KB…

@James Avery Glad it worked. From my experience. Some things/behavior you can explain quite logic. Wrong Permission, wrong Scope, wrong Settings. But rest? More less try and see if it working.