Viswanathan Ramachandran Community Champion

Hi, Welcome to the Community! 👋 TL;DR: Yes, 100% achievable. You won't lose PR/commit history, and Jira issue links will restore once re-indexed under the consolidated organization. Here are the details: 1. Does History & Jira Linking Stay Intact? Bitbucket History: Preserved. Commits, branches, PRs, comments, and…

On top of what Josh said, if you click Need more help, on the AI prompt type in your description and then you will be able to see "submit support ticket" You should be able to chat as well and they can raise a support ticket for you as well. Hope it goes well.

Hi, The workaround is a quick fix. Have you tried these: 💡 Option 1: Switch to OAuth (Smoothest HTTPS Experience) 🔑 Option 2: Switch to SSH Keys (Best Long-Term Fix for CLI) Add your public SSH key to Bitbucket Personal Settings > SSH Keys.

Hi, This change will be a shift from static reporting to dynamic reporting, AI-driven decision hubs. However, the bridge between legacy and modern is built on vendor readiness. Interesting to see how the 3rd party add-ons integrated will look like. As we evolve and adapt, treat this migration as an forward-looking metrics…

Great read and this will be very useful for organisation adopting Atlassian for their work especially when using JSM. I think you should put this as article and run a demo session on community events.

Hi there, Yes, this is one of the most common challenge. To answer your questions: 1. Has anyone encountered this issue during a phased Jira Data Center → Cloud migration? Yes, absolutely. I had this issues in server to DC migration. 2. Did you implement a temporary solution to surface issue relationships while linked…

You can do this on team space via Automation rule. I tested in my personal space. For ex: Setting this on In Progress transition is actually considered a best practice because it allows leads to assign tickets during backlog refinement/sprint planning, but strictly prevents developers from starting active work without an…

Ni Nicky, I have flagged this to support team. Hopefully, you get their attention.

Hi, I would rather start by requiring estimates on In Progress than on assignment. This prevents blocking triage/assignment while still ensuring no active work runs without an estimate. If you're on company managed projects, you can add workflow validator for In Progress transition.

Hi Nicky, If support ticket is raised, do you see updates on the ticket?

Hi there, Welcome to the community and accept the apologies for delayed response. Re: 1. Existing REST API Endpoints Currently, there is no public Bitbucket REST 2.0 API endpoint or filter (e.g., under /2.0/repositories/{workspace}) that exposes whether a Forge Dynamic Pipeline provider is enabled at the repository…

Hi, Can you add/set Delete flag to false in your pipeline and any extra flags under extra args? or as an alternative, if you prefer full control over the exact flags without using pipe defaults, you can also run your working CLI command directly inside the pipeline's script: block. Here, I assume bitbucket's default SSH…

Hi, Do you or anyone as Organisation admin still have access to admin.atlassian.com ? if so, you can disable the SSO and probably delete the SAML entries. once done, users can go to id.atlassian.com using email address, then select can't login to set Atlassian password if you don't have access to admin.atlassian.com? best…

Hi, I’m firmly in the accelerating safe change tier. The old gatekeeper model is dead and the new mandate is governed velocity. My vision: Every change in ours (Atlassian, DevOps toolchain) is visible before it lands, validated in a test environment, traceable end‑to‑end. Every risk is engineered out and not managed by…

Yeah, I wrote a similar it comes down to Atlassian's continued investment in Bitbucket as it remain a core pillar of its developer platform strategy and they continue reshaping its feature set to align strictly with a cloud-first infrastructure.

Exactly Nabeel. Bitbucket remains favourite for organisations using Atlassian ecosystems with exceptions for larger companies investing in multi toolset. but to me, it comes down to Atlassian continued investment in Bitbucket as it remain a core pillar of its developer platform strategy and they continue reshaping its…

Hi @yash.virmani Welcome to the community Older Atlassian OAuth apps typically use Classic scopes (e.g., read:jira-work) Newly created apps default to Granular scopes (e.g., read:issue:jira) If your client backend requests classic scopes in the authorization URL but the new app in the Developer Console only has granular…

Confluence Wiki Markup Editor Old school user macros Old-school Confluence Server dashboards Jira Classic Issue View & Admin Menu Above all, the biggest transition of Server to DC and now to Cloud. The Nostalgia: On-premise hosting (upgrades), manually tuning JVM heap sizes, managing database backups, integrations with…

For me.. Looking back at my tech origins as a System/Network Administrator, I somehow got handed the keys to Jira back in 2008 v3.13! I can still see that glorious, peak legacy UI. Naturally, my immediate reward was being crowned the ruler of custom workflow design. Then came the fire: using the Universal Wiki Converter…

Hi @Laura Mehrkens Thanks, this looks like a great step forward. I understand it’s still long way to go… but a couple of questions: Alerts & exports: Any roadmap for alerts, APIs, or data exports so we can integrate these metrics into existing dashboards and runbooks? Retention & granularity: What are the planned data…

Mine too.

Hi, I still don't see option to give direct kudos for any article. I need to click the kudos drop down, mention the user and then give kudos. Is that expected?

I see that in the bugs thread. Thanks. As long as I type the name, it comes.

Hi, thank you for the updates. I also notice, mention takes time. See below. I have to mention the user explicitly to see the person. In previous version, simply @ pops the name (who created the post, whoever commented). Not sure if this was told in the initial release. Not an issue, just asking/curious..

On top of what Gabriela mentioned.. Can you check if the user has the Set Issue Security permission ? Did you check your automation audit log ? Do you have any workflow properties set on the status? Are there any post functions for Issue Security? Try performing the exact transition using a Jira Site Admin account. If the…

for Jira, you can start with Atlassian Learning. https://community.atlassian.com/learning/catalog? search=scrum You can also see https://www.atlassian.com/agile/tutorials

Yes, this is a very common hurdle when getting started with A2A (Agent-to-Agent) integrations between Rovo and external agent frameworks like LangChain! By default, the A2A protocol’s request payload sends high-level context metadata. It does not automatically embed the full work item details into the message payload. The…

hi @susila selvaraju since you can't bypass the SSO, you need to contact Atlassian support use this form https://www.atlassian.com/company/contact/purchasing-licensing?redirectSource=sac-wac-redirect#/ choose your account login issues Need more help enter the details You can also perform live chat with the agent on the…

What error do you get? Is this company SSO? If so, you or ask the SSO admin to renew and generate new certificate. You/they need to log into their Identity Provider to renew or generate the new X.509 certificate. If SAML enforcement is preventing you from logging into Atlassian, Organisation admin can still log into…

Hi @NeelimaKondamoori Could you check whether CP-6760 is linked to the story twice? If so, remove the duplicate link and refresh the page. Since this happens whenever you create a Test Plan from a story, it may be caused by the creation workflow or automation linking the plan twice. If there’s only one link, check with…