Arkadiusz Wroblewski Community Champion

@Mikael Sandberg Yep that very strong possibility @Sotiria Roumania Strongly that can be a reason. 

@Tolga Tapan I will also advice wait out at least 1 Business Day. Sometimes these Problems are quite generic and tied to Amazon AWS Hickups.

Hello @Kevin Mathew 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 without logging in. * Enter your…

Hello @G M I’d start by checking exactly which app you’ve installed, as Trello’s own documentation is surprisingly thin on a dedicated Outlook add-in compared to their Gmail or Teams versions. Even with the Atlassian-branded app in the marketplace, it’s worth testing Outlook Web in an incognito window to see if this is…

Hello @Sathishkumar Sundaram , JSM Cloud doesn't actually "reuse" your app's OAuth login. Instead, the standard approach is to have both your app and JSM point back to the same central Identity Provider. While your app sticks with OAuth or OIDC, you connect Atlassian to that same IdP using SAML via Atlassian Guard for your…

Hello @Chris Hampshire Changing a project key in Data Center is doable, but definitely isn't "no impact." While Jira handles the basics like redirecting old links and keeping old keys working in JQL it triggers a background re-index the moment you hit save. Because of that, you really should save this for a low-traffic…

Hey @bharat if your epics are hitting the board but missing from the roadmap, it's almost always a scope or filtering issue. Just because an epic lives on a board doesn't mean the Roadmap "sees" it; you need to verify that the specific board or project is actually listed as an "Issue Source" in your Plan settings. The…

Hello and welcome to the Community @ttang it’s better to read that "every minute" in the docs as the scheduler’s heartbeat rather than a real-time guarantee. In JSM Data Center, processing is a two-step dance where the Puller fetches the mail and the Processor handles the ticket creation. Even in a perfect setup, Atlassian…

@Marc -Devoteam- What a post says and what is actually happening do not always match. :) Especially lately, with all the recent changes across Atlassian products, it’s pretty easy to miss something. For me, this looks like native behavior. The “Cancel” transition is setting a resolution, and that is what triggers the…

Hello @Lyss @Marc -Devoteam- automation idea is a solid lead, but you should first look at the native JSM notification logic. Jira Service Management treats a "Customer-visible status change" and a "Request resolved" event as two different things. Specifically, the resolution email is triggered the moment the Resolution…

Hello and welcome to the Community @Wagner COS_ Garcia I think this question is a bit misplaced, because your post reads more like a direct case for Atlassian Support. This is a community forum, so people here can definitely try to help, but nobody here has direct access to Atlassian’s internal systems or to your company…

@Dave LIAO I always wanted to be a firefighter as a child, but I never got the chance to live that dream.

Hello @Aimee Roddick _Walter_ While John’s approach works if design and engineering are happy in one shared space, your issue seems to be the friction in the handoff itself. If you want clear ownership, don’t force them into one ticket instead, make the link between them more explicit. I would lean into the linked-item…

Hello @alex.2.zhang Looking at your screenshot, this doesn't seem to be an issue with Jira itself, but rather a loading failure specific to the Checklist app panel. The message "We’re having trouble connecting to Checklist" is the standard way Jira tells you that a third-party Marketplace module is failing to "talk" to the…

Hello @azxcasdzxcxc Failure itself are quite Generic. Please try another Name for your Site.

Hello @Sudipta Shekhar _ TCIN If you are looking for that clean, customer-facing portal where people can raise and track their own tickets, you are actually describing a feature of Jira Service Management (JSM). It is a common point of confusion, but standard Jira even at the Premium level doesn't have a built-in "portal"…

Hello @sravani vennapusa First, please describe your process and use case in more detail.

Hello @Bill Sheboy Hope you’re doing well. I’ll be honest, I’m a bit split on this topic. On one hand, I’m very much in favor of free speech and not a fan of heavy moderation. Blocking comments often feels unnatural to me. A lot of the time, people who come in with attitude can be dealt with by simply answering them…

Hi and welcome to the Community @Paul Norrod The "400 Bad Request Request Header Or Cookie Too Large" message from nginx is the key detail here. It usually means that either Jira or the reverse proxy sitting in front of it is hitting a limit on the size of the headers or cookies your browser is sending. Since GitHub is a…

Hello @Jerome Grunnagle _Trey_ I wouldn’t jump to licensing as the culprit just yet. Since your OAuth is working and you can actually see the tools, the "handshake" itself is fine. That specific error message "We are having trouble completing this action" is exactly what Atlassian points to when there’s a transient snag…

Hi @Marina Francolin Janowitzer This definitely doesn't sound like a standard permissions problem since you can see the content perfectly in view mode. The real giveaway is that discrepancy between view and edit; in Confluence Cloud, that usually points to an issue with the editor itself. Likely a "legacy" page trying to…

Hey @Giuseppe Torraco CSM are very Brand new so I will give it some time. That's very real statement without coloring things. 

Hi @Pierangelo Repetti you can definitely track that in Assets, but I wouldn’t recommend just cramming multiple owners into one field on the laptop object. Since you are really looking for an assignment history rather than a list of current co-owners, it's better to model those changes as distinct records. While Assets…

Hello @Josh I wouldn't make a drama out of it. It’s more likely that someone spotted a few errors in the documentation and pulled the changelog to fix them. While it doesn't happen every day, it definitely wouldn't surprise me.

@Corné Louwerse @Kris Klima _K15t_ Even after checking the recent Firefox changelog, my IT intuition tells me the problem is likely on Atlassian's side, not with the browser.

@Kris Klima _K15t_ been there. From time to time switched Browsers because something not worked. 

Hello @Davyd Melnychuk Based on what you’ve shared, I wouldn’t worry about your JQL or webhook registration for now. Your filter looks solid, the webhook is active, and the expiration hasn’t passed yet. The key thing to remember is that the "failed webhooks" log only tracks attempts that Jira actually tried to deliver but…

@nagata shumpei You’re spot on. Removing those users from your organization only cuts their ties to your specific sites and data. It doesn't impact their access to any other Jira instances or organizations where they might be using that same Atlassian account. This works because Atlassian treats "access" and "identity" as…

@nagata shumpei You're exactly right. Removing a user from your organization only cuts off their access to your specific sites. It won’t affect their ability to log into other Jira instances or organizations where that same Atlassian account is still active. Basically, removing them from the org is local to your…