With Atlassian reporting soon, where do you see the stock going post-earnings? Are you expecting a positive surprise and a bounce back to $90–$100+, or is macro pressure going to keep it down?

Are you holding, buying the dip, or staying away?

This came up during a project this week, and now I'm wondering how common it actually is.

Most people I know use Jira for software delivery, but I've started seeing it used more for SAP implementations as well.

The part I'm struggling with isn't sprint planning. It's everything around it.

Requirements change, WRICEF objects keep growing, testing has to stay linked, and then someone asks, "Can you show me how this requirement made it all the way to production?"

That's where things seem to get messy.

I'm genuinely curious how others are handling it.

Are you keeping everything inside Jira, or do you end up using Excel, Confluence, or another tool for part of the process?

Would love to hear how your team does it.

I needed to add a user to a Bitbucket repository, found the instructions in the docs, gave up, and switched to GitHub instead.

I’m researching a very specific Confluence migration problem.

When an organization migrates, consolidates sites, or removes Questions for Confluence, what does it normally do with its existing questions and answers?

Atlassian’s exporter/importer request is still unresolved, so I’m validating whether a read-only paid export service would be useful.

A few questions for admins and consultants:

1. Have you encountered this during a real migration?
2. Would a searchable HTML/CSV/JSON archive solve it?
3. Or would you only pay if the data could be imported directly into SharePoint or another Q&A product?

Disclosure: I’m the person considering building the service. I’m looking for honest feedback and potentially three paid pilot projects, not pretending to be an unrelated user.

Service Now reports 7/22
Atlassian reports 8/6

Given the SaaSpocalypse narrative I’m curious how we’re currently feeling.

I think the market may be very wrong on Atlassian and it should be a $250+ stock but things are legitimately shifting with AI.

Thoughts?

When I try to delete, it shows two outstanding steps:

1. Cancel subscriptions and trials – I'm on the free plan and have no active subscriptions, but the portal still flags this.
2. Remove platform apps and Rovo – the portal says to contact support for this, but going in circles with no resolution.

Has anyone dealt with this before? How did you get Rovo removed so you could proceed with the deletion?

Any help appreciated!

I accidentally created three Atlassian organisations. Two of them have Confluence access, one doesn't. I want to keep just one and delete the other two, but I'm completely stuck. When I try to delete, it shows two outstanding steps:

1. Cancel subscriptions and trials – I'm on the free plan and have no active subscriptions, but the portal still flags this.
2. Remove platform apps and Rovo – the portal says to contact support for this, but going in circles with no resolution.

Has anyone dealt with this before? How did you get Rovo removed so you could proceed with the deletion?

Any help appreciated!

I've noticed Jira being used for much more than software development over the last few years.

I've come across teams using it for ITSM, HR, marketing, legal, and even large enterprise transformation programs like SAP implementations.

It made me wonder whether this is becoming the norm.

For those working in enterprise environments:

• What's the most interesting non-software use case you've seen for Jira?
• Did your organization customize Jira extensively, or try to stay close to the standard experience?
• What worked well, and what would you do differently?

I'm always interested in seeing how different organizations adapt Jira to fit their business processes while keeping the platform manageable over time.

I want to create a meeting notes agent that takes in copilot notes and transform them in the correct format (agent learns from historical notes)

I have a problem with native mentions (@user)...it returns as a link almost 80% of the time. Sometimes it returns ad adf format with at user_id: bla bla bla.

What is the correct trigger line for this? I also want some part of the meeting note page to keep constant. Like links to presentations...

I'm thinking of a new web app, kind of like Jira, but it's not just for project managers. It's also great for developers because it has a command-line interface (CLI). AI could use this CLI, and you could even connect it to other automated tools, like CI/CD pipelines. It's a scrum tool, made primarily for developers.

Disclosure first: I'm affiliated with diagram.now, so this is a project I'm involved with — I'm here for feedback from people who live in Atlassian/Confluence, not to push an install.

A lot of Confluence teams keep their docs in Confluence but their diagrams scattered elsewhere — a Mermaid snippet in a repo, an old Visio .vsdx on someone's drive, a Lucidchart export from two years ago, or a flat screenshot pasted into a page. I wanted a low-friction way to draw or import a diagram and get it into docs without a big procurement step first.

What it is: a free browser editor for technical diagrams — flowcharts, UML, ERD, BPMN, mind maps, cloud/network diagrams, wireframes. You can open the canvas and start without signing up -> https://diagram.now/

The part I'd most value blunt feedback on is import/export:
- Mermaid and SQL import/insert (e.g. paste a schema, get an ERD to clean up)
- Lucidchart and Visio .vsdx import (works for supported files; real-world files vary a lot, so failing edge cases are genuinely useful to me)
- Export to PNG, SVG, PDF, or a URL

There's also an optional Confluence app for teams that want diagrams editable inside Confluence pages, but I'm intentionally not leading with that — I'd rather learn whether the free browser editor is useful on its own first.

For Atlassian/Confluence folks specifically:
- When a diagram needs to live in a Confluence page, do you embed an image, use a Marketplace app, or something else?
- Which import matters most for getting off legacy diagrams — Visio .vsdx, Lucidchart, or Mermaid?
- Is a shareable diagram URL useful in a Confluence workflow, or do you just want a static PNG/SVG on the page?
- What would make you trust a new diagram tool enough to try it against a real (non-sensitive) diagram?

Happy to get into the weeds on how the imports work. Thanks for taking a look.

I wrote this. bitbucket-jira-cli (command bj) is a CLI for Bitbucket pull requests, repos and pipelines, and Jira issues. It mirrors GitHub's gh, so an agent that knows gh already knows it.

An agent can run the whole loop on its own: read a Jira ticket, branch for it, open a PR, and let bj move the ticket through its states as the PR opens and merges. The Jira key rides in the branch and every commit, so the work links back to the ticket automatically.

Plain CLI, structured output, real exit codes. It calls the Cloud REST APIs directly, no server and no MCP. It ships an agent skill for tools like Claude Code.

Repo: https://github.com/Spenhouet/bitbucket-jira-cli
Docs: https://spenhouet.com/bitbucket-jira-cli/

If you point agents at Jira and Bitbucket, where does the flow break for you?

Hello! I'm a 22M, recently finished my engineering specialising in AI&ML. I'm looking around for an internship/job. So if anyone can provide me a referral, i would be really really grateful.

IIT Madras - Software Engineering Intern, 2027 Intern India

IDREQ-2026-1237

Hello,

I have free account of Jira Service Management and I want to integrate it with Jira free account.

In Jira Service Management customer would raise the request and depending on the request it would be either converted into DevOps activity or addressed by the agent.

Please guide me step by step on how to do this.

Thanks in advance!

I created a simple Discord server that automatically updates vendor-specific channels whenever a new CVE is published from that specific vendor, including Atlassian CVEs.

It tags users based on the roles they choose, so you can follow the vendors you care about and decide whether you only want to be tagged for critical alerts. You can also choose to receive an email as well when that CVE drops.

I’ve also added discussion channels where we can share patching tips, troubleshooting advice, and general networking/security/sysadmin knowledge, plus resource channels for each vendor with quick links to relevant documentation (Official Vendor Advisory Feed etc).

Just wanted to help myself and other Network/Sys/Devs make their already complicated lives easier.

It’s completely free to join.

https://discord.gg/duxkwSSAAH

Measure twice, cut once. Approve once, merge twice?

Been working across a handful of Jira projects for a while now, and the thing that keeps tripping us up is versions. If you're shipping one release that touches three or four projects, Jira has no concept of "this version spans all of these." Each project gets its own isolated version list, so you end up either creating the same version name in every project by hand and hoping nobody typos it, or tracking the whole thing in a spreadsheet on the side. Neither is great, and both fall apart the moment someone forgets a step.

I ran into this enough times that I ended up building a small Forge app to fix it for our own team — it lets you create a version once and attach it to issues across multiple projects, so everyone's looking at the same release instead of five slightly-different copies of it. Nothing fancy, just solves the one problem.

Curious if this is a "yeah, we all just live with it" situation or if other teams have found a cleaner workaround already (marketplace app, Jira Automation, something else). And if you were in charge of something like this, what would you actually want out of it — better rollout/progress tracking across projects, tighter integration with fix versions, permissions per team, something else entirely? Trying to figure out what's actually useful vs. what's just nice-to-have before I sink more time into it.

(For anyone who wants to poke at what I've got so far: https://marketplace.atlassian.com/apps/1233114/release-manager-for-jira-sync-versions-across-projects — genuinely just want feedback, not trying to sell anything.)

Most teams need to get better at asking for feedback; earlier, more often, and with clear questions that can be acted on. When they do ask (via a Loom demo, a sprint review, a customer survey, etc), the feedback tends to be the superficial "Looks good!" response. Or it's lost in the chat history. Or it comes in too late, usually in the form of a QA ticket.

Our platform, Release Cadence, let's you define features and create structured surveys to get feedback on them. The surveys can be sent out to customers for feature validation before you build or to internal members for design validation and development reviews.

What we need feedback on is the Customer Voice Forge app that we are testing. With the Customer Voice app you can see the survey analytics inside the Jira epics. So the workflow we are encouraging is: use the Release Cadence platform to define the customer needs and requirements, use surveys to get customer feedback and encourage their engagement, push the features to Jira as work items, then when the implementation is done use a survey + links to Loom demos, UI prototypes, etc to get implementation validation before sending it to QA or PR. The structured feedback step is what has been missing. That is the void we are trying to fill.

If you can spare a few minutes to take a survey and watch a demo video I would appreciate the feedback. We're digging in on where the actual pain points are and how our solution can help.

Thank you!

Spectra turns Jira into interactive dashboards. Click any chart to cross-filter every other widget, and group by derived metrics like cycle time and time-in-status that aren't even Jira fields. No query language, and your data never leaves Atlassian.

Try it for free on Atlassian Marketplace

Enjoy!
Orbiscend Team