Arkadiusz Wroblewski Community Champion

@Koen Bruggeman Well, we started troubleshooting from a pretty reverse angle. You can try either creating complex automation or simplifying it to pinpoint the real issue. 🤠🤭😉

Hello and welcome to the Community @Jules McCool Native no. options are usually one of this 3: 1. Forward-looking tracking with Automation 2. Historical extraction through the REST API/changelog 3. Marketplace app that indexes issue history For future moves, you should create an automation rule with the Issue moved trigger…

Hello @Deepak Chawla Test in this order: GET https://api.atlassian.com/ex/jira/<cloudId>/rest/api/3/myself GET https://api.atlassian.com/ex/jira/<cloudId>/rest/api/3/project/PROJECTKEY GET https://api.atlassian.com/ex/jira/<cloudId>/rest/api/3/issue/ISSUEKEY If those fail, the problem is still account access, token scopes,…

@Koen Bruggeman Also I seen you asked in this specific topic about this form Automation. Great. We can come then faster to solution. That's why I love Automations, very much of troubleshooting is try, find problem, change, and so go on..... 🤠😅

@Koen Bruggeman GET request is returning a 404, the issue is likely with resource identity or access permissions rather than your JSON body. I would pause the copy troubleshooting and first verify that your cloudId, issue key, and API token user all belong to the same Jira site. You can confirm your site's specific cloudId…

https://support.atlassian.com/jira/kb/access-forms-data-with-the-forms-api-in-jira-cloud/ Experimental API header added? For troubleshoot you must deep oversimplifise that to see what's going wrong. 

Hello @Lana Hedinger Unfortunately Natively no. Cloud are not so customisable like Data Center https://jira.atlassian.com/browse/CONFCLOUD-27701

@David Burrieza Montserrat A safer way to do this is to just create a regular "index" or "navigation" article. You can then manually add links to the relevant KB articles, using the links copied from the JSM knowledge base/customer view. So instead of using the Content Tree / Page Tree macro, you could use something like:…

@Darryl Lee You got pretty much what you asked for and stayed within the possibilities. At the end of the day, the quality of Generative AI really depends on how good/precise your prompts are.

Hello @Donna Foronda Actually, Traceid will be helpful for Atlassian, but not really for us. We don't have access to their deep logs. It could have many reasons, so Atlassian probably needs to look under the hood at your current setup to figure out what's happening and what's causing it.

Hello And welcome to the Community @송지현 https://jira.atlassian.com/browse/JRACLOUD-72282 There also another one. Actually this one are open 😉🤠

@David Burrieza Montserrat Are you using the Content Tree Macro? Are these Macro the links that lead to denied access? If yes, there's a known ancient bug. After using the Page Tree, users are sent to the normal version of the page, not the knowledge base.

@Brendan Dwan Pros for great Question. That's also on my Radar.

Hello @Chethan GR @Christopher Yen examples are a solid start. From an ESM perspective, it is usually better to avoid the "AI everywhere" approach at the beginning. Instead, focus on a single, high-volume service area where your documentation and processes are already well-defined. Rovo is essentially a force multiplier…

Hello @Deep Harsora Without bothering about details, that should be very easy for your Admin. From my experience, Accounts are rarely deactivated just by coincidence, there must be a reason for that which your Admin must know. Good luck 🤞 

Hello and welcome to the Community @VIVIANE SOUSA SANTOS The thing is. @Fabio Racobaldo _Catworkx_ provided you the KB article. Personally, I prefer a “learning by doing” approach here. Explaining every single step in this thread may solve this one case, but it will not help you much in the long run. It is better if you go…

Hello @David Burrieza Montserrat This depends a lot on how those non-licensed users are accessing the Confluence content. Public link? Anonymous space access? JSM knowledge base? Guest users? If you are using public links, then this is expected behavior. A public link shares one specific page only. 

Hello and welcome to the Community @Urvashi Saxena Also I know how it sounds, have you tried reach out to your Admin?

@Bill Sheboy Golden words, I have plenty Automations triggering Automations myself and sometimes behavior are... Tricky... in nicest words.

Hello and welcome to the Community @Jeff Wieland Also we had an incident related to lookup issues adding to answer from @Bill Sheboy Failure in Automation and In System itself are not good combination 😅

@pablo Sometimes it goes like that. From my side I Tending to always little patience. AWS Cloud have sometimes their ”Moods”.

You need to use the exact format my@own.email:API-TOKEN without any quotation marks, spaces, or angle brackets. If you encode "email:token" instead of just email:token, the quotes actually become part of the credential and Jira will reject it. When you're setting up the web request in your automation, the Authorization…

@Matt You can find most of us on Linkedin.

@Matt I answered under instead directly answer. Excuse me.

@Matt I will repeat myself a bit but... For standard Jira projects, it is better to think of the setup as a direct connection rather than a simple association. Jira cannot log in to a distribution list because those lists don't have their own inbox or password. Instead, you should have your distribution list forward all…

Hello @Miles Mai The issue here is likely the authentication method rather than the token itself. The Deployments API is a bit unique; it doesn't usually play nice with standard Basic Auth (email + API token). Instead, Atlassian expects this specific endpoint to be called using OAuth 2.0. Even if your token has the right…

Hello @jason_teoh @Jordi Jaquez Jordi’s on the right track, but I’d definitely have your mail admin dig through the mail gateway logs next. You need to see if the emails are being stopped before they even hit your inbox. Ask them to hunt for any traffic from noreply@am.atlassian.com or @id.atlassian.net. You'll want to…

@Célia for us, Assets is useful when the information should not just be a normal Jira custom field, but a structured object with its own attributes and relations. We do not use it only in the classic “IT asset inventory” sense, like laptops, monitors, phones, etc. The bigger value is that you can model business or…

@Matt Miller That will confirm what I think and point in direction Regress.

Hello @Matt It sounds like the wires might be getting a little crossed between outgoing notification settings and incoming mail processing. The address you set up in the admin console is usually just the "From" address for notifications; it doesn't automatically tell Jira to start "listening" to that mailbox for new…