Ajay _view26_ Community Champion

Hi @Suryanarayanan Sayee Subramanian I think this is a current limitation, not a misconfiguration on your end. Agents can place the macro on the page, but the macro itself can't resolve its data source without a real user-context insertion path.

Hi @Jimmy Vales Welcome to the community! Can you check by generating a fresh token at id.atlassian.com → Security → API tokens, paste it into Gitlab, and re-testing?

Hi @rraswant Can you confirm in the agent's configuration, the knowledge source is enabled across all channels, not just the test panel?

As @Fabian Bruhn mentioned, Atlassian only exposes create/get/delete endpoints for the database container itself, not the row-level data inside it.

Hi @Admin Welcome to the community! One fix which you can try is to ask the other admin open the board and navigate to Board Settings → Members. From there, she should be able to re-grant you admin rights. Once your role is refreshed server-side, the "Close Board" option should reappear on the web.

Hi @C Sense As @Carlos Garcia Navarro mentioned, the fastest path is to go to https://id.atlassian.com and use the "Can't access your account?" flow. This routes you to Atlassian's account recovery team, who can verify your identity through alternate means (billing records, previous login patterns, etc.) and remove or…

Hi @Maurizio As @Trudy P Claspill mentioned, there is typically a grace period of 30 days after deactivation before data is permanently deleted on free-tier Atlassian Cloud sites 

Hi @Todd Gillissie Welcome to the community! Column customization in Sourcetree on macOS is unfortunately much more limited than the Windows version - this is a long-standing platform disparity. Right-clicking column headers does nothing on Mac; it's not broken on your end, it's just not implemented.

Seems to be a large scale outage. https://status.atlassian.com/

Seems to be a large scale outage. 

Yup .. seems to be an outage - https://status.atlassian.com/

Hi @Tanuja Walgude Welcome to the Community! The MCP server currently authenticates org-level permissions via OAuth, not Basic auth with API tokens, even if you've granted every available scope on the token. The root cause is that API tokens generated at id.atlassian.com work fine for Jira REST calls but the Rovo MCP…

Hi @Bralin Coleman As @marc -Collabello--Phase Locked- mentioned, current V1 MCP release, Confluence Databases (the structured-data/records feature) are not exposed through the MCP server's tool set. The available tools cover classic pages, spaces, and search — but the Databases feature uses a separate internal API surface…

@Siddik Shaikh Welcome to the Community! Can you share what endpoint and action type you're calling, and whether it fails consistently or intermittently. Consistent failures point to a permission or unsupported-action issue; intermittent ones are more likely rate limiting or backend load.

Hi @Suraj If you are using JSM, Go to your JSM project → Project Settings → Request Types → create a new request type and customize the fields. You get a public-facing portal URL you can share with requesters — no Jira login required for submitters. This is the recommended path for structured intake workflows.

Hi @Bruce Jackman Welcome to the community! Can you check out the below steps? Step 1- Access the workspace directly. Go to bitbucket.org/<workspace-slug> (use the actual slug from your license details). If you were granted access to the subscription, you should be able to see it this way even if it's hidden from your…

Hi @Paula Morton This is a known edge case in Confluence Cloud. The root cause is almost always one of two things 1. The destination space already has a page at the same URL path. If the space you're moving back to already has a home page (which it almost certainly does), Confluence won't let you overwrite it by moving…

Hi @Hyrum Phelps The block happens because your Atlassian account is still the billing admin on a Loom workspace with an active subscription — even a free-tier one counts as an "active entitlement." Here's how to clear it: 1. Log into admin.loom.com (not loom.com) with your Atlassian credentials. 2. Navigate to Workspace…

Hi @JanetGilbert Welcome to the community! Your best bet right now is to check every local machine that had a clone of the repo. Run git remote -v to confirm it points to Bitbucket, and as long as the local clone exists, you still have the full history. You can re-create the Bitbucket repo and push it back up with git push…

Hi @luckypeic A few things you can try - Use the API directly to verify: GET <a href="https://api.bitbucket.org/2.0/repositories/%7Bworkspace%7D/%7Brepo_slug%7D/forks" target="_blank" rel="nofollow noopener noreferrer">https://api.bitbucket.org/2.0/repositories/{workspace}/{repo_slug}/forks</a> — this will tell you if the…

Hi @Neil L The problem is that {{issue.description}} pulls the raw ADF representation, which goes haywire in plain email contexts. Instead of that, try using {{issue.description.plainText}} in your automation email rule. This strips out the ADF markup and gives you readable text. If you're on a Jira Service Management…

Hi @Muthu Annamalai Welcome to the community! First, can you check if the invite email might have landed in your spam or junk folder? Atlassian invitation emails sometimes get caught there, especially with corporate email filters. Second - if you already have an Atlassian account under that email address, the invite might…

Hi @Laura Castro This could be a timing issue between your automation and the workflow! JSM fires the "Approval Required" email (with the Approve/Deny buttons) exactly once — the moment the ticket first enters the approval status. Your automation sets the Approver Group just after the ticket is created, but by then the…

Hi @Paul Pogonoski There's no dedicated "test" notification button in JSM, but here are the best approaches to verify your mobile notifications are working without polluting your queue: * Create a test project: The cleanest approach is to create a separate throwaway JSM project (e.g., "Notification Test"), set yourself as…

Hi @運営事務局 MLC This could be a audio routing limitation, not a Loom bug. Possible solutions - * Set your Zoom output to "MacBook Speakers" instead of earphones: In Zoom → Settings → Audio → Speaker → select "MacBook Air/Pro Speakers." You'll hear participants through your Mac speakers, and Loom will capture the system…

Hi @safa sahli This is a very common and well-documented Forge pitfall. The core issue is that Forge apps cannot use a plain Bearer token (API key) for the Atlassian Admin API — the Forge runtime has specific constraints on how external HTTP calls are authenticated. Why curl works but Forge doesn't: * curl uses your…

Hi @Xavier Ruiz Welcome to the community! Don't panic — organisation-level repositories in Bitbucket Cloud don't disappear without cause. The most likely explanations are: * Workspace vs user account confusion - Check ALL your workspaces at https://bitbucket.org/account/workspaces — the projects may be under a different…

Hi @Cat Ellen Welcome to the Community! You're right that Loom's AI-generated transcripts can have errors, and yes — you can edit your own transcripts in Loom. Here's how to do it * Open the video in Loom. * Click on the transcript panel on the right side of the video. * Click on the word or phrase you want to correct — it…

Hi @Callistus Neba Welcome to the community! Here are the key best practices for delegating project-level administration in Confluence while maintaining global governance: 1. Use Space Admin roles, not Global Admin: Give project leads Space Admin access to their specific spaces only. Space Admins can manage permissions,…

Hi @Scott Napolitan Hi Scott! This is a known and widely reported issue with the Jira Cloud changelog API. There are two separate problems likely occurring: The changelog endpoint itself has gaps: The /rest/api/3/issue/{key}/changelog endpoint with nextPageToken pagination has known inconsistencies where certain…