Atlassian

Suspected Malicious Review by Competitor – No Response on ECOHELP-109591 Hi Atlassian team, We are a Marketplace vendor and are currently dealing with what appears to be a review submitted (one star) without actual app usage, and potentially by an affiliated competitor in the same category. We have opened support ticket ECOHELP-109591 and provided detailed backend evidence, including: Timestamp verification showing the review was submitted before the app was accessed Confirmation that no feature usage occurred Additional context indicating a possible competitor affiliation However, despite providing complete documentation, we have not received any response or update on the ticket. Our concern here is not about negative feedback — we fully respect the Marketplace review system. Our concern is about review integrity when a review appears to be submitted without usage and possibly influenced by competitive interests. We would appreciate clarification on: Expected SLA for review-related investigations Whether there is an escalation path when a ticket remains unaddressed How Atlassian evaluates potential competitor conflicts in reviews We are simply seeking fairness and timely handling of the issue. Thank you. 1 post - 1 participant Read full topic

Two Forge apps stuck in Marketplace review for months - No feedback provided Hello Atlassian community, I’m a Forge developer, and I’ve been trying to publish two apps on the Atlassian Marketplace for months without success. I’m reaching out here because I’ve exhausted all other support channels, and I’m hoping someone from the Atlassian team or experienced vendors can help. App 1 - Automatic rejection with no reason: My app “FlowPro | Intelligent Process Automation & Smart Checklists” is being rejected automatically within seconds of submission with the message “No reason was given.” This has happened repeatedly over several days and releases. What I’ve verified: forge lint passes with no errors forge deploy --environment production completes successfully All mandatory fields in the Marketplace listing are complete Pricing configured for all tiers Privacy & Security section fully completed Data Residency correctly set for Forge storage usage Screenshots and app icon meet all specified requirements No trademark violations in app name Vendor profile fully completed including payment details Despite all of this, the rejection happens in seconds, which clearly indicates an automated validation failure. However, no specific error or validation detail is provided, making it impossible to identify and fix the issue. Prior to that, the app was over 2 weeks waiting for approval. App 2 - Stuck in review for 3 weeks: My second Forge app has been waiting for review for 3 weeks with no updates, no feedback, and no communication from the Marketplace team. What I’m asking for: Can anyone from the Atlassian Marketplace team provide specific validation errors or logs for the automatic rejection of App 1? Is there any way to get a status update on App 2 after 3 weeks in review? Is there an official checklist or documentation that validates that all vendor profile requirements, legal agreements, and app listing requirements are correctly completed? I want to make sure nothing is missing on my end, but the current documentation is fragmented and unclear. Is th...

AI theater vs. AI fluency: The sneaky patterns that hold back AI results The future is already here – it’s just not evenly distributed.” William Gibson said this in 1984, but it’s very much where we are with AI today. AI tools for everything from coding generation to editing video have crash-landed into our workflows. Autonomous agents are just as capable as interns (or are they?). The race is on to become AI-native. But for many, it feels more like turbulence than a rocket launch. We’re all trying to harness the new product superpower – but how do we know if it’s working?! We don’t have any quick fixes. But through many in-depth conversations with product leaders, we have uncovered some patterns – some that drive us forward, and some that hold us back. Today, we’re unpacking how leaders and teams can thrive in this uncertain era. That starts with understanding behavior: what it means to be AI fluent, and how to avoid surface‑level ‘AI theater’ that only makes change look transformative without delivering real impact. We’re featuring voices from our podcast, Product in Practice , where we dive deep with product leaders experimenting in real workflows. What is AI theater? As with any new technology wave, a few familiar traps are already showing up in how teams approach AI. Watch out for these anti-patterns that hold back progress: Tool tourism: Collecting logins like souvenirs, without changing how work actually gets done. Think “we tried this one, and that one too.’ The illusion of progress masks the absence of impact. Automation theater: Glossy demos that wow in a team meeting but collapse when asked to live inside the backlog or the customer workflow. They look transformative, but they don’t survive contact with everyday reality. Prompt gatekeeping: Withholding knowledge, prompts, or workflows to protect personal value. This hoarding of tricks slows down collective learning and keeps wins from compounding across the team. These challenges are just symptoms: of the transition from individual craft to organizational capability. That shif...

Forge SDK Method for Triggering Jira Automation Webhooks Problem Statement Our Forge app (NASA Standup) needs to trigger Jira Automation rules when a standup meeting completes. Currently, the only way to do this is by calling https://api-private.atlassian.com/automation/webhooks/{webhook-id} using fetch(), which requires declaring external.fetch permissions. The paradox: api-private.atlassian.com is Atlassian’s own infrastructure The data never leaves Atlassian’s ecosystem Yet this disqualifies the app from “Runs on Atlassian” eligibility because Forge treats it as “external egress” Current Implementation We POST to Jira Automation webhooks with this structure: const webhookResponse = await fetch(webhookUrl, { method: ‘POST’, headers: { ‘Content-Type’: ‘application/json’, ‘X-Automation-Webhook-Token’: webhookSecret, }, body: JSON.stringify({ issues: [‘PROJ-123’, ‘PROJ-456’], data: { participant: ‘atlassian-account-id’, comments: { ‘PROJ-123’: ‘Comment text’ } } }), }); Security measures we’ve implemented: URL is hardcoded to only allow https://api-private.atlassian.com/automation/webhooks/ prefix Users cannot configure webhooks to any other domain Webhook secrets are stored securely in Forge Storage Use Case Users configure automation rules that trigger Jira Automation workflows when a standup completes: Create summary issues with flagged items Update issue statuses based on standup comments Send notifications via Jira Automation’s integrations (Slack, Teams, etc.) This is a valuable feature that connects our app with Atlassian’s first-party automation platform. Proposed Solutions Option 1: Exempt api-private.atlassian.com for Automation Webhooks Allow external.fetch to api-private.atlassian.com/automation/webhooks/* without disqualifying apps from “Runs on Atlassian”, since: It’s Atlassian-owned infrastructure It’s for a first-party Atlassian feature Data stays within Atlassian’s ecosystem Option 2: New Forge SDK Method import { automation } from ‘ @forge /api’; await automation.triggerWebhook({ webhookId: ‘webhook-uuid’...

Is it possibel to make backend api.atlassian.com as ingress? manifest.yml external: fetch: backend: - address: api.atlassian.com 2 posts - 2 participants Read full topic

Welcome to the future of creating and editing in Confluence with Atlassian Rovo Creating and managing content is core to how teams plan, share knowledge, and move work forward. But in practice, the process is often slow and fragmented. Teams struggle with creating content from scratch, reformatting documents, and hunting for context across tools, all before real collaboration even begins. Confluence already serves as the place where teams create, collaborate, and share knowledge. Now, they can use AI to move from idea to published content faster than ever by pairing it with Atlassian Rovo . Let’s dive into the new, modern way teams can now create and edit content in Confluence . Challenges teams face today Most teams don’t struggle with ideas — they struggle with turning those ideas into clear, impactful content they can then share with their teams. These pain points include: Struggling from blank page anxiety and trying to figure out how to get started from scratch Manually copying and pasting information , and then having to tailor that information for different purposes or audiences Searching across tools to find the right context or latest updates to bring in Spending time rewriting, reformatting, and editing content manually These slowdowns add friction at every stage of work, from early planning to creation to editing. Say hello to the new way of creating and editing in Confluence By using Rovo, teams can overcome that manual, time-consuming process of creating and editing and focus more time on where it matters. Rovo partners with you to quickly take your ideas to draft to published content in Confluence – whether it’s a page, live doc, whiteboard, or database. Simply describe what you want to create or refine and AI does the rest , pulling in data sources across Atlassian and 3rd party apps to to create context-rich, high-quality content in Confluence. The end result? You’ll get a beautifully formatted, structured draft that’s grounded in your team’s existing work – in seconds. How to use Rovo to create and edit content Teams can now ta...

Rovo Dev is now generally available in VS Code We’re excited to announce that Rovo Dev is now generally available in VS Code as part of the Atlassian VS Code extension. The Atlassian VS Code extension already connects your editor to Jira work items, Bitbucket pull requests, and more. Now, we’re building on that foundation with Rovo Dev — a context-aware AI agent that lives right inside your IDE. Rovo Dev brings AI-assistance directly into your IDE, helping you plan, code, review, and ship faster without breaking focus. Shifting fragmented workflows to focused development Developers spend a significant part of their day outside their code editor — hunting for ticket details in Jira, searching Confluence for specs, and checking Bitbucket or Github for related changes. When context, documentation, and code history live in separate tools, developers are forced to constantly switch just to understand what they’re working on. Every tab switch breaks focus. Every search takes time. That fragmentation slows down workflows on a daily basis. Powered by Atlassian’s Teamwork Graph, Rovo Dev connects to Atlassian context and third-party tools like GitHub through our Jira integration, enabling developers to access work items, documentation, code history, and team knowledge without leaving their editor. Rovo Dev in VS Code delivers a seamless native experience in your IDE. It lets you search, chat, apply edits, run tests, and prepare commits—automating key parts of your software development workflow directly in VS Code. With Rovo Dev in VS Code , you can: Start your tasks faster: Ask Rovo Dev questions about your codebase, Jira work items, or Confluence docs — without leaving the IDE. Get instant answers about architecture, dependencies, and best practices. Automate the busywork: Offload tasks like drafting Jira work items, pull requests, and even code changes to Rovo Dev, which automatically pulls in the right context. Stay in your flow: Get work suggestions, view your code reviews, and manage tasks directly from VS Code so y...

App rejected with no reason and unable to access ECOHELP space We’ve submitted a Forge app and completed all required steps, including the privacy policy and security questionnaires. However, I’m unable to access the approval ticket: http://go.atlassian.com/marketplace-support/ECOHELP-111810 When I open the link, I get an “Access forbidden” page. I’ve already tried “Request access”, but it doesn’t resolve the issue. I also tried to access https://ecosystem.atlassian.net/servicedesk/customer/portal/34/ECOHELP-111810 but same error Could you please check whether my Atlassian account is added to the ticket or grant access so I can track the approval progress? Thanks a lot. 1 post - 1 participant Read full topic

Codegeist GARBAGE Hackathon Hi All, I think everyone here in community already know that atlassian just announce a winner for Codegeist hackathon. But really, I think some winners should not be there at all. They have no video, their apps never tested working, and even some has not published link to try their apps, but still they win. I really don’t understand, what useful their imagination story for atlassian community ? Is judges unprofessional or just get drunk ? I don’t know. BUTTT, This is really undermined all participant who hard work to make their apps working. And can be use by atlassian community. And below is paste from their own judging criteria: Judging Criteria Quality of the Idea Includes creativity and originality of the idea. Implementation of the Idea Includes how well the idea was executed by the developer. Potential Impact Includes the extent to which the solution can help the most Atlassian users. How can implementation of the idea just judge from video, without test their apps working or not ? and what potential impact can help most atlassian users without any provided link to try out. Thank you. 3 posts - 2 participants Read full topic

No access to ECOHELP-110212 approval ticket Hi team, We’ve submitted a Forge app and completed all required steps, including the privacy policy and security questionnaires. However, I’m unable to access the approval ticket: https://ecosystem.atlassian.net/browse/ECOHELP-110212 When I open the link, I get an “Access forbidden” page. I’ve already tried “Request access”, but it doesn’t resolve the issue. Could you please check whether my Atlassian account is added to the ticket or grant access so I can track the approval progress? Thanks a lot. 1 post - 1 participant Read full topic

Jira 11.x Plugin Migration – Unable to Inject services Hello everyone, We are currently migrating our legacy Data Center plugin to Jira 11.x , adapting it to: Jakarta ( jakarta.* ), Updated Spring versions, Removal of legacy javax.* , modern plugin framework changes .. However, we are stuck on a dependency injection issue when accessing (for example) one of our servlets. When accessing our servlet (used for initial addon configuration), Jira throws: Caused by: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'com.sykorait.vmcon.ConnectorSettingsServlet': Unsatisfied dependency expressed through constructor parameter 0: No qualifying bean of type 'com.atlassian.sal.api.user.UserManager' available: expected at least 1 bean which qualifies as autowire candidate. No matter what combinations we try, we are not able to import and inject these components ( UserManager, ApplicationProperties, .. ) In previous Jira versions (javax-based, older Spring), this worked correctly using: @ComponentImport, @Inject, @Scanned .. We also tried what seems to be the now recommended JavaConfig-based OSGi approach using: pom.xlm 4.0.0 com.sykorait.jira.plugins USU-Service-Management-Connector 2.2.3 Sykora IT s.r.o. https://www.sykorait.com USU Service Management Connector for Jira Integration between USU Service Management (Valuemation) and Jira. atlassian-plugin org.glassfish.jaxb jaxb-core 2.3.0.1 org.glassfish.jaxb jaxb-runtime 4.0.2 com.sun.istack istack-commons-runtime 4.0.0 com.sun.xml.fastinfoset FastInfoset 1.2.17 com.atlassian.plugins atlassian-plugins-osgi-javaconfig ${osgi.javaconfig.version} jakarta.annotation jakarta.annotation-api 2.1.1 provided com.sun.activation jakarta.activation 1.2.2 provided commons-httpclient commons-httpclient 3.1 provided jakarta.activation jakarta.activation-api 2.1.1 provided net.sf.ehcache ehcache 2.10.10-atlassian-2 provided jakarta.xml.bind jakarta.xml.bind-api 4.0.0 provided org.glassfish.jaxb jaxb-runtime 4.0.2 provided jakarta.servlet jakarta.servlet...

Case sensitive search Hi, I am not a Confluence developer myself, I just work at a company where documentation is stored on a locally hosted Confluence website, one can search it with Confluence Query Language and so on. I wanted to know if CQL supports case sensitive search? I am trying to find out about a certain acronym “PReP” and I do not want to return results for “prep”, “preparation”, “prepping for”, … If I wanted to modify the code for our Confluence website to support this functionality where would I start? 1 post - 1 participant Read full topic

Date format as rendered by Atlassian Document Format I am building a confluence macro that returns a date in date format. I generate the date format by using the AdfRenderer from @forge /react like this: import React, { useEffect, useState } from 'react'; import ForgeReconciler, { AdfRenderer, useConfig, Label, useProductContext, DatePicker, Text } from '@forge/react'; const today = new Date().toISOString().split('T')[0]; const toTimestamp = (dateString) => { if (!dateString) return Date.now().toString(); const d = new Date(dateString); return isNaN(d.getTime()) ? Date.now().toString() : d.getTime().toString(); }; const Config = () => { return ( <> Define date ); }; const App = () => { const config = useConfig(); const dateValue = config?.datepicker; const timestamp = toTimestamp(dateValue); // Always render the REAL ADF in view mode const actualADF = { type: "doc", version: 1, content: [ { type: "paragraph", content: [ { type: "date", attrs: { timestamp: timestamp } } ] } ] }; return ( <> ); }; ForgeReconciler.render( ); // UI Kit config registration ForgeReconciler.addConfig( ); Everything works well, except for the problem that the rendered data is always in MMM DD, YYYY format (e.g., Feb 10, 2026). I have tried changing the global date configuration in Confluence, my Atlassian account’s language, my browser’s language, but all had no effect. Only the built-in date macro in Confluence changed as my configuration changed, but the value as rendered by the Forge macro stays the same no matter what I do. Could someone please advise how I can get the rendered date in the format of DD.MM.YYYY for example? Thank you very much! 1 post - 1 participant Read full topic

Confluence 11.0 release EAP available now Hi everyone, A Confluence 11.0 EAP milestone is now available. EAP releases provide a snapshot of our work in progress and give you an opportunity to test and fix your apps before the final release. During the development of Confluence 11.0, we’ll release monthly milestones and betas. To find out what’s changed, head to Preparing for Confluence 11.0 Get the latest EAP If you have any problems with an EAP release, please raise an issue to let us know. The earlier we know about problems, the more time we’ll have to fix them before the final release. Enjoy! The Atlassian Confluence team We now announce Confluence Data Center releases and more in the Atlassian developer changelog . Subscribe to the changelog to receive the latest updates. 3 posts - 3 participants Read full topic

Unifying teams and tools: How Personio scales smarter with Jira, Confluence, and Loom The learnings in this blog post are based on Personio’s session presented at Atlassian’s Team Europe ’25 conference. You can check out this session and others on demand. Modern companies are being pulled in two directions at once. Outside the organization, market and technology shifts demand speed, creativity, and constant adaptation. However, within the organization, fragmented systems and disconnected ways of working quietly undermine everything. Personio, a fast-growing HR software company based in Germany, found itself right in the middle of that tension. At the time, they aimed to massively scale their impact at work, improving the working lives of four million people by 2026. As they grew to nearly 2,000 employees to support that mission, they realized their existing collaboration tools couldn’t keep up. Personio’s answer was to unify collaboration on Atlassian Teamwork Collection and use it as the backbone for how work happens across the business. Teamwork Collection is Atlassian’s collaboration stack that brings together Jira, Confluence, and Loom, powered by Rovo. Internal friction at Personio: systems working against each other As markets, customers, and technologies evolve faster than their operating models, enterprises feel squeezed from all sides. Beneath the surface, long-standing organizational habits, legacy systems, and ways of working can quietly amplify that pressure, making it harder to adapt with speed and confidence. At the same time, AI is lowering the barrier to entry for new competitors, shipping cycles are accelerating, security expectations are non‑negotiable, and customer and employee expectations for clarity, speed, and polish continue to rise—leaving market leaders increasingly vulnerable to faster, more agile disruptors. Personio’s experience will sound familiar to many: Disconnected data weakens AI outcomes: Without a unified data foundation, even strong AI investments struggle to deliver meaningful, context-rich help where work actua...

RovoCon SF 2026: Say Hello to Your New AI Teammate I joined the Atlassian team just weeks ago as a Developer Advocate, and within my first few days, I was already headed to my very first RovoCon in San Francisco. Hosted by our Atlassian Community Champions, the event made one thing crystal clear: AI agents aren’t just chat tools anymore, they’re doers . They can now execute complex tasks while keeping you perfectly in the loop. It’s like having a little minion in your pocket. Here is my recap of the day from a “Newlassian” perspective. Arriving at the Office I arrived shortly after 9:00 AM and was greeted with signs and arrows directing me exactly where I needed to go. Friendly office staff met me with a lanyard and a swag bag (socks and a beanie, shout out to the organizers for the top-tier choices!). A beautiful platter of breakfast was available with all the goodies: muffins, fruit, and coffee. I grabbed my assortment and took a seat. RovoCon was already off to a great start. Once the talks began, I saw the real magic of the new way of working. Rovo: Your New AI Teammate The morning kicked off with a deep dive into how AI is transitioning from a tool to a teammate. We’re talking about unlocking unprecedented productivity by handing off mundane, repetitive tasks to a dedicated AI assistant. A few stats really jumped out at me: 78% of users now prefer Rovo search over traditional Confluence search. Context Reigns Supreme: Having used Confluence search for years, I’ve watched it miss the mark more than once. Rovo changes that—it doesn’t just find a page; it grasps your intent . Atlassian even created a chatbot specifically for us “Newlassians,” which has made my onboarding seamless. It turns a 30-minute documentation hunt into a 5-second natural language query. Count me in that 78%! The Shift: From Chatbots to Action Agents The theme “From Chat to Action” is where the sheer velocity of AI change became visible. We aren’t just talking to LLMs anymore; we are giving them “Skills” (formerly known as Actions) so they ca...

Why standardizing workplace technology is the next competitive advantage for CIOs Over the past decade, the enterprise tech stack has expanded dramatically – with hundreds of workplace apps, including numerous overlapping collaboration and productivity tools used across teams. But what began as digital empowerment has evolved into fragmentation – with disconnected systems, duplicate workflows, inconsistent data, and rising governance and security risks. It couldn’t come at a worse time: 93% of executives say cross-functional collaboration is more crucial than ever. Yet, employees struggle to collaborate across tools – constantly chasing context, toggling between apps, and recreating work – while IT teams face mounting integration, licensing, and security burdens that slow transformation and increase costs. The result is a silent productivity tax: reduced visibility, fragmented decision-making, and slower execution across the business that ultimately undermines performance. For CIOs, the next competitive edge isn’t adopting more tools – it’s creating operational excellence by uniting departments on a secure, extensible, standardized digital workplace foundation. Standardization: the new lever for operational excellence To reclaim control over costs, risks, and velocity, leading CIOs are bringing teams across the organization together on a unified, extensible collaboration stack that has the flexibility to be tailored to each team’s requirements. A consolidated platform unifies teams, systems, and strategy – giving IT visibility and control while empowering business units to execute more effectively and adapt quickly. With one governed foundation, IT reduces redundancy, strengthens security, and improves the employee experience. The payoff is operational excellence, simplified governance, and more time for IT to focus on innovation rather than maintenance. CIOs gain unified visibility into system governance while delivering a more consistent, reliable user experience across the enterprise. Driving workplace productivity and business outcomes On a s...

Scrum Board Issue List x Backlogs Hi Everyone, Anyone aware about the issue on the scrum board when you create a backlog, it moves to the list page when you refresh and there’s no way to move it back? It’s kinda weird 1 post - 1 participant Read full topic

Can’t update or get unpublished page drafts via REST API v2 Related topic: Can't update page draft via REST API v2 I am trying to update the draft of an unpublished page using update page rest v2 . Like the documentation suggests my request uses status=”draft” and version.number = 1. However, I am met with a 404 status code. The http error message doesn’t include anything other than NOT FOUND. This behavior is consistent with the update page by id API, which also returns 404. Now I wonder if that is supposed to work or not. The topic I linked at the top sort of makes me think it should. Can someone verify? Thanks! 1 post - 1 participant Read full topic

Multiple Forge apps stuck in "Submitted" status for over 2 weeks Hi Atlassian Community & Marketplace Team, I recently developed and submitted two new apps built on Forge and I’m excited to share them with the ecosystem, but I’m concerned about the review timeline. All two apps have been in the “Submitted” status for over 14 days now, with no updates or feedback. The apps are: JMeter Performance Analytics for Jira k6 Performance Analytics for Jira I understand the team might be busy, but I just wanted to check if this delay is normal currently? Or perhaps I missed a step in the submission process? If there is any additional information or action required from my side to move the review forward, please let me know. Thanks in advance for your help! Best regards, Nick 1 post - 1 participant Read full topic

Api requests sent through forge have outaded responses in comparison to connect ones Hey everyone, I’m developing a feature for a Forge app that works with labels. When I add a new label to a Work Item, it takes 10 minutes or more for that label to become available through the API. I’m using the following endpoint: /rest/api/3/jql/autocompletedata/suggestions?fieldName=labels&fieldValue=lam The issue only occurs with Forge ( requestJira via @forge/api or @forge/bridge ). When I make the same request through a Connect app or simply access the URL directly in the browser , the newly added label appears immediately. Is this a known issue? Has anyone else experienced this? Any insight into why Forge requests would return stale data compared to Connect or direct browser requests would be appreciated. 1 post - 1 participant Read full topic

Function timed out. Limit of 25.03 seconds Our 2 Forge apps have the function time out error logs reported in the last 24 hours. Previously, those customer sites operate successfully. Could you please take a look? This issue have an impact on the customer retention. ecosystem.atlassian.net Jira Service Management 1 post - 1 participant Read full topic

Pressing the forge ready button Hey, we are in the process of migrating apps connect → forge however We would like to know if we create forge manifest with connect webhooks and select in developer console that we are now on forge will those webhooks be disabled? The ideal solution would be to just use your script to transfer descriptor to manifest and don’t worry about any issues like disabling webhooks (which is mentioned in docs) until Q4 2026. We would also like to be certain that we will be able use those webhooks and JWT authentication still after saing we support forge manifest. And third “just to be sure” question, will we be able to modify connectModules section after march and you will only stop reading connect descriptors? Thank you, Mateusz 1 post - 1 participant Read full topic

How long forge connectModules will be working? Hey, will connectModules in forge manifest work unitl Q4 of 2026 or longer? Thank you, Mateusz. 1 post - 1 participant Read full topic

Is AI the ultimate hackathon buddy? What we learned at ShipIt 61 Subscribe to Work Life Get stories like this in your inbox Subscribe What if you had a hackathon buddy who had almost infinite knowledge and no need for caffeine? Rovo’s Impact on ShipIt 61 Participants Rovo usage among participants was 11% higher than the rest of Atlassian during the hackathon period. Participants using Rovo reported higher confidence in their solutions and final presentations. Rovo, Atlassian’s AI-powered assistant, is designed to help teams work smarter by finding information, summarizing content, and helping with tasks across Atlassian tools. Rovo streamlines workflows, answers questions, and boosts productivity. Now, imagine what Rovo could do in a high-stakes, time-crunched challenge like a hackathon. Having Rovo or another AI tool is a huge advantage for time-crunched hackers. A brief history of ShipIt at Atlassian Atlassian’s ShipIt hackathon events provide a way for Atlassians to work cross-functionally with team members they wouldn’t otherwise collaborate with. Atlassian’s ShiptIt hackathons started in 2005 with a small group of developers looking to accelerate some debugging work. Related Article “24 hours of opportunity”: behind the scenes of ShipIt By Philip Braddock In Inside Atlassian ShipIts have been aptly described as “24 hours of opportunity” and a “quarterly creativity fest”. These events are an invitation to drop what you’re working on to explore an idea, test a theory, fix a recurring issue, or plainly have some fun with colleagues. At the end of the event, teams share a three-minute presentation. From there, finalists are chosen to compete for a selection of awards. It’s exhilarating, beloved, and still going strong after 20 years. Over the years, Atlassians have used quarterly ShipIt events for everything from designing speakeasies hidden behind bookcases to innovating a restroom-friendly laptop tray. Some Atlassian products (like Jira Service Management ) came directly from ShipIt events! ShipIt is a living example of Atlass...

Our Q2 FY26 letter to shareholders Prefer a PDf? No worries! Get it here From the CEO We had a fantastic Q2. We’re building a bloody great business. I’m convinced AI is great for Atlassian. Others think software is dead. In this environment, it seems that noise swamps signal, nuance gets lost. So this quarter I’m going to give you straight signal. The Q2 facts that make me bullish. And let our customers do the talking. Revenue grew 23% YoY to $1.6 billion. Cloud revenue grew 26% YoY $1.1 billion – our first ever $1 billion+ cloud quarter. RPO up 44% YoY to $3.8 billion, continuing to accelerate – reflecting enterprise adoption and long-term customer commitments to us as a strategic platform. Rovo sailed past 5 million MAU. Teamwork Graph now well past 100 billion+ objects & connections – our AI transformation continues to deliver for our customers’ workflows, with record agent & token use. Record number of $1 million+ ACV deals, up nearly 2x YoY. 600+ customers with >$1 million of ARR, up almost 40% YoY – our enterprise transformation continues is delivering, with us becoming an ever-more strategic partner to our customers. Cloud net revenue retention rate (NRR) is 120%+, ticking up for the third consecutive quarter – customers are expanding use of our enterprise AI platform with more users, apps, and upgrades. Over 350,000 customers, including 80% of the Fortune 500 and 60% of the Forbes AI 50 – with 50% of our users in finance, HR, marketing, ops, and other non-technical teams. Teamwork Collection, our primary AI monetization, passed 1 million seats and 1,000 customers – exceeding our expectations, consolidating tools, and expanding seat counts by 10%+ over their standalone app footprint. Service Collection launched Customer Service Management and passed 65,000 customers, including half of the Fortune 500 – while our enterprise business grew 60% YoY in Q2. Software Collection launched, DX joined the team, and had a record Q2 – customers are choosing us for their AI-native software development lifec...

Experiencing inconsistent timeouts for Rovo MCP We have been experimenting with integration our Claude Code agents with Jira via the remote MCP to facilitate integrating those agents in to work flow. We experience inconsistent timeouts causing the Claude Code loose authentication much quick than would be expected. At least it appears as a auth timeout that requires the user to reauthenticate to get the MCP server to work again. It is short enough that it is frustrating our engineers working to use the MCP server to pull/update/create issues in Jira or generate docs to be added to Confluence. I really hope an answer can be determined. As I look to a future that leverages AI agents more and more, being able to integrate those with our Jira flow will be critical. 1 post - 1 participant Read full topic

Webinar on Feb 10th: How to use AI to speed up your code review workflow With the rapid increase in AI-generated code, do you find yourself spending more time buried in PRs? Join us live on Feb 10/11th, 2026 to learn how to use Rovo Dev to speed up code reviews, improve code quality, reduce merge conflicts, and get to production faster. We’ll show you the AI-powered workflow Atlassian teams use to cut PR cycle times by up to 45%. What we’ll cover How to enable Rovo Dev code review for your repositories How to have Rovo Dev check your code against your organization’s custom coding standards at scale (including security and compliance) in every AI-powered review How to link Rovo Dev to a Jira issue and have it automatically check your code against issue details Practical ways to improve code quality and reduce review friction that you can implement in your organization right away. There will be a live Q&A so bring your questions. Sign up here The post Webinar on Feb 10th: How to use AI to speed up your code review workflow appeared first on Work Life by Atlassian .

Codegeist 2025 share link problem Hi all, I just read that all apps needs to be on developer space now, but it was working even without i move apps into developer space at all using different account and different site. But i don’t know about judges site, is they able to install it or not. Lots of weird things happen though. So, because till today, i don’t see any installation log from judges, i try to move into developer space. And i inspect that my shared link still intact there, not changes at all, but now i test with different account and different site, not working. Is it links really not working after moving into developer space ? Why still there then if already not workin ? And if it should be working, why i can’t install it then ? Thank you for any help. Hope judges can reply too. Update news: now it even has problem. My question is it will impact to judging process ? As when i develop for last 2 weeks of hackathon period it always failed to forge install to aws ( with aws error messages) every night jakarta time. Cheers, Hendra 1 post - 1 participant Read full topic

From stable to unshakeable: announcing upcoming major releases for Atlassian Data Center Hi Data Center Community, We’re excited to announce the next major versions of Atlassian Data Center products. We’re making further investments to help ensure your self-managed environments stay secure, reliable, and easy to operate . Building on the work we did for previous major upgrades, these upcoming changes will sit underneath: Jira Software 12 Jira Service Management 12 Confluence 11 Bitbucket 11 Bamboo 13 Crowd 8 This work is now in the scoping and planning phase. We’ll share more details and timelines as soon as they’re available, and individual product teams will communicate specific changes, release plans, and upgrade guidance. Scope at a glance Stronger security by design The upcoming changes share a united goal: meet and maintain a strong security posture . To achieve this, we are: Tightening how Java Naming and Directory Interface ( JNDI ) is used and configured to close off types of historical vulnerabilities. Strengthening protections against Server‑Side Request Forgery ( SSRF ) across the stack. Upgrading and hardening core HTTP client libraries. Moving to Jackson v3 for JSON processing. Infrastructure updates We’re making significant updates to our core technology stack, including: Upgrading to Spring 7 and Jakarta 11 Adding support for Java 25 and removing support for Java 21 Upgrading to React 19 Upgrading to jQuery 4 How these changes help you Modernize core components by updating the underlying libraries and frameworks to supported versions that follow today’s security best practices. Make it faster to ship security fixes quickly and consistently across products that share the same foundations. Reduce reliance on legacy or hard‑to‑upgrade pieces of the stack, which often show up in customer security scans and audits. Provide a stronger secure‑by‑default baseline when you upgrade to the next major versions. Reduce surprises where older, forked, or out‑of‑support libraries become a long‑term risk. Clarify communication about which APIs and compon...

Planning ahead for Teamwork Graph... Team and Team Member / Role Management I am enduring a Cloud migration from Jira DC now that needs to be done to be able to begin to explore TeamWork Graph. I am being asked to evaluate the Teamwork graph to replace a home-grown app we have for managing teams and all their attributes, team hierarchy (teams / projects / portfolios), and Team Members (including their Team Roles and gearing ratios. I wonder if anyone would be able to just chat back and forth with me on some of my questions and what Teamwork Graph does or does not do so that I can be prepared for future planning of the transition. And I can’t find a Category that fits this topic… is there a better forum to be asking these questions?? (I will be submitting a ticket through support for advisory services, but thought I’d start here. Thanks! 1 post - 1 participant Read full topic

External Links in IFrames Do Not Open After Migrating to Forge (Confluence) Hello, after moving my module to forge in atlassian confluence, Intercom usage had a problem, links inside don’t work (only using open new tab) so this is mainly because of the forge security layer.. As I think that popups and opening links but with forge router , in case like that how to solve that problem, and allow links to open in iframes : THE ERROR: Blocked opening ‘``https://google.com/``’ in a new window because the request was made in a sandboxed frame without the ‘allow-popups’ permission. Btw i added the link to manifest external fetch client Appreciated ! 1 post - 1 participant Read full topic

Marketplace app approval pending for over 14 days – status request Hello Atlassian Marketplace team, I’m reaching out to follow up on a Marketplace app submission that has been pending review for more than 14 days. App name: Ziggy Submission date: 22JAN Marketplace listing URL (if available): Jira Service Management i dont have access to the link above to keep track of the submission The app has been in a “Pending approval” state since submission, and I haven’t received any updates, questions, or requests for changes so far. I wanted to check whether: the review is still in progress, there is any additional information or action required from my side, or there were any issues blocking the approval that I may have missed. All required documentation and vendor details should be complete, but I’m happy to provide anything further if needed. Thanks in advance for the help, and I appreciate any update on the current status or expected timeline. Best regards, Oleg 1 post - 1 participant Read full topic

Atlassian Rovo MCP Server is now GA The first wave of generative AI gave us insanely cool models and AI-powered features, but it also created way more places to go. Another tool, another context switch, another hitch in your workflow that just might be the proverbial straw on your camel’s back. The Atlassian Rovo Model Context Protocol (MCP) Server is our promise that your work can come to you. Staying true to our open ecosystem values, you get the choice to evolve your AI strategy as fast as the market does, without ever having to rewrite how Atlassian fits in. Now generally available and more connected than ever, the Atlassian Rovo MCP Server gives you a single, secure way to let a broad set of AI clients—AWS, ChatGPT , Claude, Cursor, Devin, Docker, Figma, GitHub, Google, Lovable, Mistral, Postman, Resolve, VS Code, WRITER, and more—work with Jira and Confluence. AI that reads and writes where your teams actually work When MCP first appeared, it felt like a very promising experiment. Today, it’s closer to infrastructure, underpinning how serious AI tools connect, share context, and take action. We were quick to join the ecosystem with our MCP Server in beta , and the signal from partners continues to be loud and clear: Jira and Confluence are the connectors they get asked for again and again. Taking it GA is our way of turning that early interest into something durable and enterprise‑ready. Now, from within an external AI client’s MCP server setup, there’s even more your teams can do. Connect your AI client to the Atlassian Rovo MCP Server, consent to scopes and sign in with an Atlassian account, and bring your context-rich Jira and Confluence work right to you. Rovo search and fetch : Let your AI assistant run rich, semantic searches across Jira and Confluence (e.g., “find the latest incident postmortem for checkout failures”) and pull the right issues, pages, and services into the conversation. Create and update Confluence pages : Turn a drafted spec or summary into a real Confluence page in the ...

Products

Bug: Time picker dropdown stays open after clearing input with Backspace in @atlaskit/datetime-picker When using the time picker part of the component, clearing the value using the Backspace key causes the dropdown to remain visible. Most importantly, it doesn’t close even when clicking outside the component or on other UI elements. Steps to Reproduce Open the @atlaskit/datetime-picke . Select a time or focus the input so the dropdown appears. Press Backspace to clear the value. Try to click anywhere else on the screen. Actual Behavior The dropdown stays open and overlayed on the screen. It seems to lose its “click-outside” listener or focus state once the input is cleared via keyboard. Expected Behavior The dropdown should either close upon clearing or, at the very least, close when the user clicks elsewhere (blur event). 1 post - 1 participant Read full topic

Bitbucket Pipelines OIDC now supports multiple audiences Bitbucket Pipelines now supports multiple audiences in OIDC claims, so you can extend the suite of resource servers your pipelines integrate with without storing credentials in Bitbucket. Multiple audiences allows you to use a single identity token across multiple resources for cleaner, simpler workflows. Customising your audiences To customise your audiences, declare them under the ( step or global ) → oidc → audiences list, as shown in the example below: options: oidc: audiences: - https://your.service0.com - https://your.service1.com pipelines: default: - step: oidc: audiences: - https://your.service0.com - https://your.service1.com script: ... Limitations: Maximum of 10 audiences Maximum audience name length: 150 characters. What is OpenID Connect (OIDC) OIDC provides an Access Token in addition to the ID Token , and it is the Access Token that is used to authorise at the Resource Server or API. Here is how they work together: ID Token: The client application uses this to verify who the user is (authentication) — in our case, it’s the pipeline. The token is read and validated by the client application. Access Token: This is the token the client presents to a separate Resource Server (API) to prove it has permission to access specific data (authorisation). Role of Audience ` aud ` in OIDC The audience is part of the Access Token identified by the aud key. Resource servers must check that their identifier appears in the aud claim to confirm the token was issued for them and reject it if not. Why multiple audiences unlock flexible integrations Multiple audiences allow us to avoid the need to obtain separate access tokens for each individual API or resource server. Learn more about OIDC and integrating pipelines with resource servers here: Integrating Pipelines With Resources Servers Using OIDC Open ID Connect The post Bitbucket Pipelines OIDC now supports multiple audiences appeared first on Work Life by Atlassian .

Is there official documentation for error responses in Jira Cloud REST API v3? I would appreciate documentation that specifies which fields in error responses are required and which are optional. I have reviewed the documentation linked below, https://developer.atlassian.com/cloud/jira/platform/rest/v3/intro/#async-operations and while I can understand the field types and names to some degree, there is no official specification regarding which fields are mandatory. This makes it difficult to write robust error handling code. 2 posts - 2 participants Read full topic

5 micro-challenges to make your team stronger this week Subscribe to Work Life Get stories like this in your inbox Subscribe Strengthening your team’s performance doesn’t have to mean a complete overhaul of your rituals and tools. A little consistency – in how you collaborate, connect knowledge across projects, and bring people together around shared goals – goes a long way. If your team is busy but still feels a little scattered, try this series of five micro-challenges over the course of a week. Each day has a distinct focus designed to help your team move faster, work smarter, and stay connected. 5 easy challenges that will strengthen your team Day 1: The 5-minute async standup Replace one meeting with a quick written update (or record a Loom !). Share in your team’s usual Slack channel or project board. Ask each teammate to share: What they completed yesterday What they’re focused on today Any blockers Skim, react, move on – no meeting needed. Why it works : It creates visibility without stealing calendar time, connects distributed team members, and leaves a written record (or video) your team can reference – turning individual updates into shared knowledge. Day 2: Change one ritual From the Playbook: ritual reset Team rituals, like meetings and events, help people stay connected and make progress. Revisit your team’s rituals once in a while to ensure they’re still working for everyone. Run the Play Choose one recurring team ritual and redesign it so it feels lighter and more useful. Recommended prompt: List 2–3 recurring rituals you do almost on autopilot (e.g., weekly standup, status report, project check‑in, etc.) Choose one that feels too long, low‑value, or confusing As a team, answer: What is this actually for (clarity, decisions, alignment, connection)? What will we change to make this ritual feel significantly lighter (shorter, fewer people, or less prep) and make outcomes/owners clearer? Decide when you’ll start the new version, how long you’ll test it, and where you’ll capture notes and next steps. Why it w...

Expose Forge app REST APIs - scope does not match Hi, I have been trying to expose custom REST API endpoints in my Forge app for some time now, and I can’t figure out how to troubleshoot the issue. I have followed this documentation step by step: https://developer.atlassian.com/platform/forge/access-rest-apis-exposed-by-a-forge-app/ manifest.yml: modules: jira:globalPage: - key: forge-test-rest-hello-world-full-page resource: main resolver: function: resolver title: forge-test-rest routePrefix: hello-world function: - key: resolver handler: index.handler - key: handler1 handler: index.handler1 - key: handler2 handler: index.handler2 apiRoute: - key: employee-api-1 path: /employeeName operation: GET function: handler1 accept: - application/json scopes: - read:employee:custom - key: employee-api-2 path: /employeeName operation: POST function: handler2 accept: - application/json scopes: - read:employee:custom - write:employee:custom resources: - key: main path: static/hello-world/build app: runtime: name: nodejs24.x memoryMB: 256 architecture: arm64 id: ari:cloud:ecosystem::app/xxxxxxx custom-scopes.yaml version: 1 scopes: read:employee:custom: displayName: Read Employee Info description: >- Read employee information such as name, date of joining, etc. write:employee:custom: displayName: Edit Employee Info description: >- Edit information related to an employee such as name, dob, payroll info, etc. I have created a new OAuth 2 app in the developer portal and assigned the right scopes: After generating the refresh token, I then proceeded in getting an access token (following this doc: https://developer.atlassian.com/cloud/confluence/oauth-2-3lo-apps/#2--exchange-authorization-code-for-access-token ) Using this access token, calls made to /oauth/token/accessible-resources return an empty array. Any API call to my forge app endpoints result in unauthorized: https:// .atlassian.net/gateway/api/svc/jira/apps/ _ /getEmployeeName Result: { "code": 401, "message": "Unauthorized; scope does not match" } How can I figure out th...

Console error "Client must be initialized" when embedding JSD widget on external website i’m using the embedded JSD widget on my site, it works well but it throws a warning in the console when loading the page: { msg: “An error has occurred checking the feature gate. Only the first occurrence of this error is logged.”, gateName: “platform_editor_typography_ugc”, error: Error: Client must be initialized before using this method at Object.assertInitialized (``https://jsd-widget.atlassian.com/assets/iframe.js:136:168946``) at Object.checkGate (``https://jsd-widget.atlassian.com/assets/iframe.js:136:170157``) at L.checkGate (``https://jsd-widget.atlassian.com/assets/iframe.js:136:179259``) … } To reproduce it, just add the standerd JSD widget in the code and load the page. I found a workaround in Console warnings when feature gate can not be evaluated , adding this before the embed script removes the error: window. CRITERION = { getFeatureFlagOverride: () => false }; 1 post - 1 participant Read full topic

How to get your team unstuck from constant miscommunication “Wait… what did they mean by that?” “We need to talk.” “Can you fix this?” “?” Two or three words in a message, and suddenly you’re not doing the work in front of you, you’re replaying it in your head. Did I mess up? Am I in trouble? Is this urgent or just… urgent‑ish? That little spiral isn’t just modern work life; it’s adding up. New research from Loom and Wakefield Research shows miscommunication is now a material business problem. Using Bureau of Labor Statistics data, that adds up to, on average, about $203 billion¹ in annual productivity losses in the U.S. alone — more than the annual economic output of roughly two-thirds of the world’s countries. In just the past month: 80% of workers spent time on work that turned out to be unnecessary or had to be redone because they misunderstood a written message. Almost a third lost more than half a workday to avoidable mistakes caused by confusing emails and chats. Nearly nine in ten say they regularly spend time each week just trying to interpret vague or unclear written messages. This isn’t “people need better soft skills.” It’s bigger than that. Most teams don’t just have a people problem; they have a channel problem. The hidden productivity tax of “What did you mean by this?” Written communication is the backbone of modern work. It’s also the place where, if we’re not careful, a lot of effort quietly gets lost or misunderstood. Across teams, people are burning hours rewriting tasks, chasing clarification, and decoding messages that felt clear in the sender’s head but landed muddled in everyone else’s inbox. We see this pattern over and over. At the leadership level, the impact is brutal: 1 in 5 VP‑level and above execs lost more than 24 hours in a single month to work that was later scrapped or redone because of miscommunication. That’s three full workdays gone. Miscommunication makes it harder to think straight. More than four in ten workers say they’ve struggled to focus at work because of fear or anxiety over a m...

Forge usage questions - how to decide app pricing based? Hello, I have few fundamental questions related to Forge usage. The app pricing is based on users but if I understand correctly the usage - compute, storage etc will contribute towards to usage. In this case how do we set the pricing of the app? Let us say a simple app for 20 users cost the client USD 100 but the vendor (us) are charged USD 120 based on the usage. We cannot control how even a small instance using our app will used. For instance if the app is storing data based on number of issues (which we cannot control) then it will increase the bill for the vendor. Any suggestions? Also another question related to billing - if we are developing an app without deploying it to production - will that count towards the usage? 1 post - 1 participant Read full topic

Getting license work in Forge Here is front-end code to get license to work: useEffect(() => { const fetchContext = async () => { try { const ctx = context || await view.getContext(); // In development environments, license is null - treat as licensed for testing const isDevelopment = ctx?.environmentType === 'DEVELOPMENT'; const isActiveLicense = ctx?.license?.active === true; if (isActiveLicense) { setIsLicensed(true); console.log('App is licensed (dev mode: ' + isDevelopment + ', active license: ' + isActiveLicense + ')'); } else { setIsLicensed(false); console.log('App is not licensed - license:', ctx?.license); } } catch (err) { console.error('Error fetching context: ', err); setIsLicensed(false); } }; fetchContext(); }, []); With commands forge deploy forge install --environment development --license active --upgrade 1 post - 1 participant Read full topic

Power up your pipeline workflow with 24x and 32x step sizes Last year we launched 16x step sizes as part of our commitment to improve Bitbucket Pipelines performance. Demand continues to increase by customers working on increasingly complex projects. In response, we are excited to introduce the 24x and 32x build size. New CPU and memory upgrades The 24x and 32 builds offer increased CPU and Memory options for builds. For reference: 16x builds will be provisioned with 16 CPU cores and 32GB of memory 24x builds will be provisioned with 48 CPU cores and 96GB of memory 32x builds will be provisioned with 64 CPU cores and 128GB of memory Example — using the size option to increase the memory available to all pipeline sateps options: size: 24x pipelines: default: - step: script: - echo "24x memory and CPU is probably not needed for an echo command" Example — using the size option to increase the memory available to one pipeline step pipelines: default: - step: size: 32x script: - echo "This step gets 32x the memory and CPU of 1x steps!" For more information on setting up and using the larger step sizes, check out the Pipelines documentation . The post Power up your pipeline workflow with 24x and 32x step sizes appeared first on Work Life by Atlassian .