rss.livelink.threads-in-node

Why can’t I delete a file that I created in a team space?

rui_guo2 — Wed, 13 May 2026 02:14:36 GMT

Yesterday, I accidentally created an extra file due to a misoperation. I’ve now found that I don’t have permission to delete it. However, I remember that previously I was able to delete or move files that I created myself. Could you explain why this is happening?

Rovo dev agent code reviewer is not working

Liam Swift — Wed, 13 May 2026 01:40:48 GMT

Hello,

We've just gone through all the steps to get Rovo Dev running for the Bitbucket organisation and specific repos.

However, it seems to hang on `Reviewing pull request` for about 5 minutes before nothing happens.

Then, if I push another commit, I can see it has detected the code changes and prompted with a button to `Review code`, but when I press this it says that `Rovo dev is not activated in the organization.` This doesn't seem to make sense as we can obviously see it is activated in the organization, and my usage is currently at 0 credits.

We've tried to toggle it on and off at the org and repo level, and have double checked the users are in the appropriate Rovo user groups: https://support.atlassian.com/rovo/docs/add-rovo-dev-standard-to-your-site/

Thanks for your support!

Requesting help deleting my Atlassian account/org — stuck in a broken state, CCPA request filed

Bryan Callahan — Wed, 13 May 2026 02:01:23 GMT

Atlassian deleted all of my repositories, but my account and org still exist in a broken state that I can't clean up through the normal self-service flows.

Here's where I'm stuck:

Every deletion/account-management workflow I've tried ends with some kind of "null" error.
The org has an IDP configured through a Google Workspace that no longer exists, and I can't decouple it.
When I try to delete the IDP, I get: "This account is related to active accounts that are set to AUTO-RENEW" — but I have no active subscriptions or auto-renewing products that I can find.

At this point I just want all of my data — accounts, org, PII, everything — fully deleted. I've exhausted the self-service options and each one hits a dead end because the org is in this broken state.

Does anyone know how to reach Atlassian support directly for account/data deletion issues? It seems like this requires someone with backend access to resolve. Happy to pay for a support plan if that's what it takes to talk to a human.

On "Account 1" if I go to https://id.atlassian.com/manage-profile/close-account I get this after clicking the button:

You can't delete your account
Your account can't be deleted because:
This account is related to active accounts that are set to AUTO-RENEW.
This account is the primary billing contact for one or more products.
This account is a technical contact for one or more products.
To continue deleting this account the account owner needs to visit my.atlassian.com and designate a different user as a billing and technical contact.
Read our support documentation for more help and instructions: https://confluence.atlassian.com/x/pTgoP.
User is last billing admin of a transaction account that has one or more active entitlements.
User is last billing admin of a transaction account that has one or more non-cancelled subscriptions.

On "Account 2" if I go to https://id.atlassian.com/manage-profile/close-account I get this (don't get to see the button and also please note that the organization's admin is me, but the org is tied to a defunct Google Workspace IDP I can't remove):

Your account is managed
You can't deactivate or delete your Atlassian account because it's owned and managed by an organization. Contact your organization's admin for assistance.

On "Account 3" if I go to https://id.atlassian.com/manage-profile/close-account I get this after signing in:

You don’t have permission to access this content
It looks like your account has been deactivated.
We've sent you an email with details of who to contact to get more information about this.

Formal CCPA Request

I've since filed a formal CCPA data deletion request (Cal. Civ. Code § 1798.105) through both the support ticket system under "Personal Data and GDPR" and the standalone deletion form at atlassian.com/trust/privacy/gdpr/request-delete-personal-data. I also tried the privacy phone line at 1 (800) 804-5281, but it prompts for an extension and disconnects if you don't enter one (which is odd because the docs say to just leave a message there).

At this point I'm waiting on the 45-day CCPA response window. If anyone from Atlassian sees this and can help expedite, I'd really appreciate it — all three accounts are in states that make self-service deletion impossible, and every official channel either errors out or dead-ends.

Why have my tables been squished up in the centre of the page?

Si Scott — Wed, 13 May 2026 01:24:34 GMT

I used tables in my confluence page to create an Implementation plan. When I created it, it looked great. Now however, it appears squished up in the centre of the screen and the table has become elongated. This makes it very difficult to read. I've tried maxing the screen and reducing margins but nothing works. Please help me to restore my tables to the full width of my screen?

User has been removed from board but still has access

Office — Wed, 13 May 2026 00:10:33 GMT

A used has been removed from the board but can still see all the current cards. Board setting is Private. User is able to see options to copy/close board and share to other members but the option to leave board is not showing because the user is not technically a member.

Recorder does not open

Kennard Bell — Wed, 13 May 2026 00:03:42 GMT

When I click. On Video Record it says it access storage and nothing happens.

Multiple Activity tabs in Jira are no longer visible

dodonoghue — Tue, 12 May 2026 23:53:13 GMT

The activity tabs in Jira now only display one tab with the others accessible via 'More'.

This is very annoying
Once again Atlassian makes unnecessary changes for the customer and keeps the original behaviour for themselves - incredible!
Here is Atlassian's Jira:
You will also notice they still have access to the field 'Type', which they have removed from their customer offering

Premium customers: can we opt out of metadata contribution without Enterprise?

Cameron Farrier — Tue, 12 May 2026 22:39:54 GMT

I’m trying to understand Atlassian’s upcoming data contribution changes for customers whose highest active plan is Premium. Atlassian says these changes take effect on August 17, 2026.

Based on the documentation, the default for Premium is:

Metadata: On
In-app data: Off

Atlassian also says:

Enterprise customers can opt out of metadata contribution, but
Free, Standard, and Premium customers cannot opt out of metadata contribution because it is always on.

That seems to mean a Premium customer may be able to opt out of in-app data contribution, but not metadata contribution, even though Atlassian says metadata can include content attributes, common patterns, search activity, Rovo Chat patterns, and certain custom configuration data.

If that reading is correct, I think a few points need clarification:

Is Enterprise really the only standard way to fully opt out of metadata contribution?
If a Premium customer disables all available in-app data contribution settings, what data can still be used under metadata contribution?
How broad is “metadata” in practice? Does it include search queries, workflow/status naming patterns, custom field patterns, Rovo Chat prompts/responses, and other admin/configuration-derived signals?
Are there any non-Enterprise exceptions (contractual, compliance-based, or policy-based) for customers who do not want their metadata used to improve apps and experiences for all customers?

The core concern is simple: if a Premium customer does not want Atlassian using either in-app data or metadata to improve apps and AI experiences for all customers, is there any path to do that without upgrading to Enterprise?

Recording of May 11 Event is now available!

Robert Wen_Cprime_ — Tue, 12 May 2026 22:37:41 GMT

For those that missed last night's meeting or want to see it again, here is the recording. https://youtu.be/8slQpFxVSbw

Seeing empty values at Jira, when passing user(multi-select) attributes through iFTTT rules

Motamarri_ Muni Venkata Surendra Harasai-CW — Tue, 12 May 2026 22:12:34 GMT

We are using confirms to for intake requests to submit to Jira issue. in one of the form, we are using filed AppUsers user(multi-select), and propagating user name, I believe full name. and email attributes in description. we are using this syntax for JIra DC version and works fine. after migrating to cloud version I am seeing ifttt not processing values

"summary": "Add [entry.AppUsers.iterateAndPrint([entry.username],)] to Google PlayStore",
"description":"*App Name:* [entry.AppName2.label]\n *Requested Users :*[entry.AppUsers.iterateAndPrint([entry.email],)]"
}}

Can you please advise on this

Welcome Wednesday: What toy/object do you bring with you on your travels?

Dave LIAO — Tue, 12 May 2026 22:14:32 GMT

👋 G'day Atlassian Community adventurers!

It's time for another Welcome Wednesday, a chance for you to participate on the forums with questions and prompts that aren't necessarily about Atlassian tools. 🙃 (See past Welcome Wednesdays here.)

For this week's question: do you bring a toy or object with you on your travels and take photos of them? Yes - for those who know about it, that toy/object is commonly called a Flat Stanley (read about it on Wikipedia).

📣 Shout out in the comments if you've heard of this! Do you already do this? Planning on doing it? Comment away!

🪿 I'll start! For those who don't know, I've been toting a stuffed duck the last 8-9 months, and now that duck has a baby:

Yes, the duckling was searching for friends at Refined's booth at Team '26 in Anaheim! I did not successfully win them a companion.

Upcoming change to Bitbucket Cloud SSH access: move from bitbucket.org to ssh.bitbucket.org

Apurva Paralkar — Tue, 12 May 2026 22:07:00 GMT

As part of our security and anti-abuse posture, we are making an important change to how SSH traffic is handled for Bitbucket Cloud. If you use Git over SSH with Bitbucket today, you’ll need to update your configuration by November 12, 2026 to avoid disruption.

What’s changing?

Bitbucket Cloud is separating SSH and HTTPS traffic so that:

bitbucket.org will serve only HTTPS traffic (web and API)
All SSH-based Git operations must use a new hostname: ssh.bitbucket.org

This change affects Git over SSH only. Common SSH operations that will be impacted include:

git clone (over SSH)
git pull
git fetch
git push

If you currently use SSH URLs that look like:

git@bitbucket.org:<workspace>/<repo>.git

you’ll need to update them to use:

git@ssh.bitbucket.org:<workspace>/<repo>.git

HTTPS access is not affected. URLs such as:

https://bitbucket.org/<workspace>/<repo>.git

will continue to work as they do today.

Why we are making this change

By splitting SSH and HTTPS traffic onto separate hostnames, we can:

Apply more advanced and tailored security protections specifically to Bitbucket’s public web and API endpoints (bitbucket.org)
Better isolate different types of traffic, improving resilience and scalability over time
Reduce the blast radius of certain classes of attacks by separating protocols

In short, this is part of ongoing work to harden Bitbucket Cloud’s security posture and improve reliability for all customers.

What you need to do

If you use Git over SSH with Bitbucket Cloud, you’ll need to:

1. Update SSH remote URLs

For each repository that currently uses an SSH remote pointing at bitbucket.org, update the remote URL to use ssh.bitbucket.org instead.

From within your local clone:

git remote set-url origin git@ssh.bitbucket.org:<workspace>/<repo>.git

Repeat this for each remote or repository that uses SSH and bitbucket.org.

You can confirm your current remote configuration with:

git remote -v

Look for any entries that include git@bitbucket.org: and update them.

2. Trust the new SSH host key

The first time you connect to ssh.bitbucket.org, you’ll be prompted to verify and accept its SSH host key. When you see the prompt, review the fingerprint and, if it matches Bitbucket’s published values, choose “yes” to continue. This will add the host key to your ~/.ssh/known_hosts file.

If you prefer to pre-seed your known_hosts file (for example, in automated environments), you can manually add the ssh.bitbucket.org host key there in advance.

You can use the following command in the automation to add the host keys of the new server:

curl -s https://bitbucket.org/site/ssh | sed 's/bitbucket.org/ssh.bitbucket.org/' >> ~/.ssh/known_hosts

3. Update CI/CD pipelines and automation

Any automated system that uses SSH to interact with Bitbucket Cloud will also need to be updated. This includes:

CI/CD pipelines
Deployment scripts
Build servers
Mirroring/synchronization jobs
Any internal tooling that runs git clone, git fetch, or git push over SSH

Search your configuration for git@bitbucket.org: or ssh://git@bitbucket.org and update those references to git@ssh.bitbucket.org:.

4. Adjust network/firewall rules if needed

If your organization restricts outbound SSH connections via firewalls or security appliances, ensure that ssh.bitbucket.org on port 22 is allowlisted.

You may need to:

Add ssh.bitbucket.org to your outbound allowlist
Update any hostname-based rules that currently reference bitbucket.org for SSH
Coordinate with your network/security team to roll out the change across environments

If your network blocks port 22, Bitbucket provides an alternate hostname and port combination you can use. Follow the directions at Port 22 is blocked on local network | Bitbucket Cloud | Atlassian Support.

Timeline

This change is being announced now, and customers will have until November 12, 2026 to complete their migration.

During this migration window, SSH access via bitbucket.org will continue to work, but you should start updating to the new SSH server ssh.bitbucket.org as soon as possible.
After the migration period ends on November 12, 2026 , SSH connections to bitbucket.org will be refused. At that point, any Git operations over SSH that still target bitbucket.org will fail until they are updated to use ssh.bitbucket.org.

We encourage you to complete these updates well before November 12, 2026 to avoid last-minute issues.

Need help?

If you have questions about this change, run into issues updating your remotes, or need guidance for complex/large-scale environments:

Comment on this post with details of your setup
Or contact Atlassian Support via your standard support channels

We’ll monitor feedback and update this post with any additional clarifications or common troubleshooting tips as needed.

How to fix this overlap of the AI agent with the helpful prompt?

rraswant — Tue, 12 May 2026 21:55:43 GMT

The ai agent overlaps with the prompt. Not sure how to fix it.

how can I contact a human agent to find answer to my question

AdemXYZ — Tue, 12 May 2026 21:06:45 GMT

I need to contact a human being at atlassian who can help me with my email address that was given by atlassian.

I have tried again and again but...

SLA Breached. Now What? 5 steps to stop the damage and prevent the next one

Alina Kurinna _SaaSJet_ — Tue, 12 May 2026 20:18:19 GMT

The ticket sat in queue for 6 hours past the SLA target. Nobody noticed – until the client emailed your VP directly. Now there's an incident thread, a meeting request, and a very uncomfortable conversation about "what went wrong." The breach itself took minutes to happen. The aftermath will take days to manage.

Most teams know SLA breaches are inevitable at some point. What fewer teams have is a clear, practiced response – something that goes beyond "escalate to the manager" and actually covers the steps from detection to resolution to making sure it doesn't repeat. Here's how to run that process.

🚨 Step 1. Detect it before your client does

The worst version of a breach is when the customer discovers it before you do. It signals that nobody was watching – and it hands control of the narrative to someone who's already frustrated.

This is where pre-breach notifications matter. In native Jira Service Management, you can set up basic SLA tracking, but proactive alerting – especially "the SLA will breach in 30 minutes" type of notifications – requires either custom automation rules or an additional layer of tooling. SLA Time and Report for Jira handles this with configurable breach notifications: you can set alerts at any percentage of the SLA cycle (e.g., at 75% elapsed time, at 90%, or immediately on breach), and send them to specific Slack channels, assignees, or team leads – with custom message templates that include ticket context.

The goal is simple: the first person to know about an impending breach should be on your team, not the client.

👥 Step 2. Get the right people on it immediately

Once a breach is detected (or has just happened), the first operational step is identifying ownership. Not "who's responsible in a blame sense" – but who can actually act right now.

Pull up the ticket. Check: Is it assigned? Is the assignee available? Is there a blocker – waiting on a third party, waiting on the customer, stuck in a status it shouldn't be in? These questions take 90 seconds to answer if you have visibility into the current SLA state. They take much longer if you're digging through Jira filters manually.

A common pattern: the ticket technically has an assignee, but it's been sitting in "Waiting for review" for 4 hours and nobody looped in the reviewer. The breach wasn't caused by workload – it was caused by a handoff gap. Knowing this immediately changes who you alert.

If you use automated actions in SLA Time and Report, you can pre-configure what happens when a breach occurs: reassign the ticket to a backup agent, bump the priority to Critical, or post a Slack message to the on-call channel. Some of these responses can fire automatically without any manual intervention – which matters a lot for breaches that happen overnight or outside business hours.

🔍 Step 3. Diagnose before you communicate

This is the step most teams skip in the scramble – and it's the one that protects you in the client conversation. Before you reach out to the customer, take 5–10 minutes to understand what actually happened.

Was the SLA target realistic for this ticket type? Did the timer start at the right moment, or was there a misconfiguration that caused it to run during non-business hours? Was the ticket stuck in a paused state that should have been active – or the reverse? Was there a surge in ticket volume that day that overwhelmed the team?

The reason this matters: if you have a call with your client and say "we're sorry, we missed the deadline" – that's an apology. If you call and say "we missed the 4-hour response target because the ticket was mis-routed during a spike in P1 volume – here's what we're putting in place" – that's a professional service recovery. The second version only happens if you did the diagnosis first.

In SLA Time and Report, the SLA Grid Report and Chart Reports show exactly when the SLA clock started, when it paused, and where time was spent across the ticket lifecycle. You're not guessing – you can see the actual timeline and identify precisely where the process broke down.

📞 Step 4. Communicate: first the solution, then the apology

The sequencing here matters more than the wording.

Don't contact the customer while you're still figuring out what happened. Contact them when you have two things ready: a status update on what's being done right now, and a realistic timeline for resolution. The message doesn't need to be long – it needs to be honest and specific.

Something like:

"We've identified that your ticket missed our 4-hour response target. It's now assigned to [name] and marked as our highest priority. We expect to have an update for you within [X hours]. We'll follow up directly – no need to chase us."

What you want to avoid: vague reassurances ("we're looking into it"), over-explaining the internal cause before you have the fix, or silence, which the customer interprets as nobody working on it.

After the situation is resolved, a follow-up communication is worth the 5 minutes it takes. Thank them for their patience, confirm what was done, and if the breach was significant, acknowledge it directly. Some teams offer a small concession or gesture – that's a judgment call based on the client relationship.

🔁 Step 5. Run the retrospective (while it's still fresh!)

This is the step that separates teams who keep breaching the same SLAs from those who actually improve. The retrospective doesn't need to be a formal post-mortem with a 15-slide deck. It needs to happen within 48 hours of the breach, while the context is still accessible.

Three questions worth answering:

Was this breach predictable? Look at the last 30 days of data for the same ticket type or project. If you see a pattern – specific days of the week, specific request categories, specific agents – the breach wasn't a one-off. It's a systemic gap.

Was the SLA goal itself realistic? Sometimes teams set targets based on what they promised years ago, without revisiting whether current team size, volume, and complexity still support them. A breach can be a signal that the agreement itself needs renegotiation.

Did the tooling fail or the process fail? If your team didn't know the ticket was at risk until after the breach, the detection process failed. If they knew but couldn't act – that's a workload or priority problem. These have different fixes.

In practice: pull a sample of 20–30 breached tickets from the last month using the SLA Grid Report in SLA Time and Report. Group them by ticket type, assignee, and time-to-breach. In most cases, you'll find that 60–70% of breaches cluster around 2–3 root causes. That's where you focus.

Once you've identified the patterns, it's worth reviewing your SLA configuration – start/stop/pause conditions, calendar settings, and whether automated actions are in place to catch at-risk tickets earlier. A breach that happens because the SLA clock ran over a weekend (when it shouldn't have) is a calendar misconfiguration, not a team performance issue.

Final thoughts

An SLA breach is always uncomfortable – but it's also one of the clearest signals you'll get about where your service delivery process actually breaks. The teams that improve over time aren't the ones that never breach; they're the ones that have a practiced response and a habit of looking at the data afterward.

The five steps here – detect early, get ownership fast, diagnose before communicating, communicate with context, and run a real retrospective – won't prevent every breach. But they'll prevent most of the avoidable ones, and they'll make the unavoidable ones much less damaging to client relationships.

If you're working in Jira and don't currently have visibility into which tickets are approaching breach in real time, or if your post-breach analysis consists of "check the comments and try to remember what happened," it's worth looking at what SLA Time and Report for Jira can add to your setup – specifically the notification system, automated actions on breach, and the reporting layer that makes retrospectives something you can actually do in under an hour.

What does your current breach response look like? Is there a step in this process that consistently breaks down for your team?

Need to retrieve daily worklog summaries for time tracking and reporting

Kyle Barry — Tue, 12 May 2026 20:14:27 GMT

I'm using the Atlassian MCP server to automate Jira workflows, and I've hit a significant limitation with worklog querying that makes daily time tracking and reporting difficult.

The Problem

The current MCP tools don't provide an efficient way to retrieve all worklogs for a specific user on a given date. The available approach is to use searchJiraIssuesUsingJql with worklogDate and worklogAuthor filters, but this has major limitations:

The search returns issues that have worklogs, not the worklogs themselves
Each issue only includes the most recent 20 worklogs in the response (via the worklog field)
For issues with many historical worklogs, today's entries may not be included in that 20-item window
There's no way to aggregate or filter the worklog data directly

Real-World Impact

When I query for today's worklogs using the current tools, I get incomplete results. For example, today I logged time to 7+ different issues totaling 3 hours, but the MCP query only returned 2 issues with visible worklogs from today. The Jira Worklogs app shows all of this data correctly, but I can't access it programmatically through MCP.

What's Needed

A dedicated worklog query tool with parameters like:

author (user account ID or email)
dateFrom / dateTo (date range)
issueKey (optional, to filter by specific issues)
Response that returns actual worklog entries (time spent, comment, started timestamp, issue key) rather than issue objects

This would enable common use cases like:

Daily time tracking summaries
Weekly worklog reports
Time-by-project or time-by-epic aggregation
Automated timesheet generation

Workaround

The only current workaround is to use the Jira Worklogs app UI manually, which defeats the purpose of using MCP for automation.

Would the team consider adding a searchWorklogs or similar tool to the Atlassian MCP server? This seems like a common enough use case that it would benefit many users trying to automate time tracking workflows.

Subscription upgraded but 5-minute limit remains – is there a sync delay?

Jennifer Borkowski — Tue, 12 May 2026 20:11:33 GMT

I am asking for immediate assistance with my account. I recently upgraded to a monthly subscription for $24 to remove the recording time limits for my tutorial videos. However, despite the successful charge to my credit card, my dashboard still shows a five-minute maximum limit per recording.

Could someone please help me update my account to reflect the correct subscription status? If it is not possible to provide unlimited recording time or the upgraded features I paid for, I need to get a full refund.

Login/Sign Up Issue

Sam O_ Sullivan — Tue, 12 May 2026 19:55:31 GMT

When I try to login in/click sign up on loom - I get brought to a page that says the robots are setting you up on Loom, this will only take 1-2 minutes and the page loads across on a bar. When finished, the page goes blank and says the following error message

Oh no...The following error happened during authentication:« Could not authenticate with Atlassian, please try again. If the issue persists reach out to an admin or the Loom support team. »

My issue is that I am getting emails from atlassian stating my trial has started, so I have an account being setup, but upon trying to login, I am prompted to setup a workspace, brought back into the same page about being setup and then repeatedly encounter this error message.

I cant login to contact support either, bit of a catch-22.

Please help!

update editors for all filters and dashboards

Shawn Jamison — Tue, 12 May 2026 19:16:45 GMT

I'm looking for a solution to add an admin group to all filters and dashboards. After our cloud migration we need to standardize access and our admins can see and access all filters and boards.

I've already looked a bit into the api: https://docs.atlassian.com/software/jira/docs/api/REST/7.6.1/?_ga=2.79114772.1476107635.1526884318-593458345.1525875113#api/2/filter-addSharePermission

I was wondering if there was an easier way for a non programmer to tackle this?

Free Account and Transfer of Files

Aude Bauserman — Tue, 12 May 2026 19:15:11 GMT

Hello,

I am currently a high school teacher with a Loom account provided by my division. I am changing jobs and will be working for a community college. I was wondering if it would be possible to get a free account as a community college professor, and if I would be able to transfer my videos from my high school account to the new account.

Thank you for your time!

I love Loom!

rss.livelink.threads-in-node

Why can’t I delete a file that I created in a team space?

Rovo dev agent code reviewer is not working

Requesting help deleting my Atlassian account/org — stuck in a broken state, CCPA request filed

You can't delete your account
Your account can't be deleted because:

Your account is managed

You don’t have permission to access this content
It looks like your account has been deactivated.
We've sent you an email with details of who to contact to get more information about this.

Formal CCPA Request

Why have my tables been squished up in the centre of the page?

User has been removed from board but still has access

Recorder does not open

Multiple Activity tabs in Jira are no longer visible

Premium customers: can we opt out of metadata contribution without Enterprise?

Recording of May 11 Event is now available!

Seeing empty values at Jira, when passing user(multi-select) attributes through iFTTT rules

Welcome Wednesday: What toy/object do you bring with you on your travels?

Upcoming change to Bitbucket Cloud SSH access: move from bitbucket.org to ssh.bitbucket.org

What’s changing?

Why we are making this change

What you need to do

1. Update SSH remote URLs

2. Trust the new SSH host key

3. Update CI/CD pipelines and automation

4. Adjust network/firewall rules if needed

Timeline

Need help?

How to fix this overlap of the AI agent with the helpful prompt?

how can I contact a human agent to find answer to my question

SLA Breached. Now What? 5 steps to stop the damage and prevent the next one

🚨 Step 1. Detect it before your client does

👥 Step 2. Get the right people on it immediately

🔍 Step 3. Diagnose before you communicate

📞 Step 4. Communicate: first the solution, then the apology

🔁 Step 5. Run the retrospective (while it's still fresh!)

Final thoughts

Need to retrieve daily worklog summaries for time tracking and reporting

Subscription upgraded but 5-minute limit remains – is there a sync delay?

Login/Sign Up Issue

update editors for all filters and dashboards

Free Account and Transfer of Files

rss.livelink.threads-in-node

Why can’t I delete a file that I created in a team space?

Rovo dev agent code reviewer is not working

Requesting help deleting my Atlassian account/org — stuck in a broken state, CCPA request filed

You can't delete your accountYour account can't be deleted because:

Your account is managed

You don’t have permission to access this contentIt looks like your account has been deactivated.We've sent you an email with details of who to contact to get more information about this.

Formal CCPA Request

Why have my tables been squished up in the centre of the page?

User has been removed from board but still has access

Recorder does not open

Multiple Activity tabs in Jira are no longer visible

Premium customers: can we opt out of metadata contribution without Enterprise?

Recording of May 11 Event is now available!

Seeing empty values at Jira, when passing user(multi-select) attributes through iFTTT rules

Welcome Wednesday: What toy/object do you bring with you on your travels?

Upcoming change to Bitbucket Cloud SSH access: move from bitbucket.org to ssh.bitbucket.org

What’s changing?

Why we are making this change

What you need to do

1. Update SSH remote URLs

2. Trust the new SSH host key

3. Update CI/CD pipelines and automation

4. Adjust network/firewall rules if needed

Timeline

Need help?

How to fix this overlap of the AI agent with the helpful prompt?

how can I contact a human agent to find answer to my question

SLA Breached. Now What? 5 steps to stop the damage and prevent the next one

🚨 Step 1. Detect it before your client does

👥 Step 2. Get the right people on it immediately

🔍 Step 3. Diagnose before you communicate

📞 Step 4. Communicate: first the solution, then the apology

🔁 Step 5. Run the retrospective (while it's still fresh!)

Final thoughts

Need to retrieve daily worklog summaries for time tracking and reporting

Subscription upgraded but 5-minute limit remains – is there a sync delay?

Login/Sign Up Issue

update editors for all filters and dashboards

Free Account and Transfer of Files

You can't delete your account
Your account can't be deleted because:

You don’t have permission to access this content
It looks like your account has been deactivated.
We've sent you an email with details of who to contact to get more information about this.