Rovo costs for enterprises ?
What’s the cost of Rovo for large enterprises ?
Anyone has the price model ? Is it similar to Claude price per seat and APi token consumption or something else ?
What’s the cost of Rovo for large enterprises ?
Anyone has the price model ? Is it similar to Claude price per seat and APi token consumption or something else ?
We use Jira at work, it's a horrible tool, but hell, we are stuck to it. We also use Loom, and now we will move from 40 USD per month to 72 USD. No reason behind it besides greed after their new acquisition. Well done, Atlassian; you were once a company to love. The more I have to deal with you, the more I dislike you.
Hey Community👋
After working with Jira for several years, I kept running into the same challenge.
Jira lets you link issues, but once a Sprint grows, it becomes surprisingly difficult to answer questions like:
So I decided to build a Forge app called Linked Issue Dependency Mapper.
The goal wasn't to replace Jira—just to make linked issues easier to visualize and manage from a single place.
Linked Issue Dependency Mapper
Some of the things it supports today:
Visual dependency mapping
Cross-project linked issues
Filter and search dependencies
Export to Excel
Inline comments and @mentions
I'd genuinely love feedback from people who deal with dependencies regularly.
If you'd like to try it, there's a 30-day free trial, and I'd be happy to hear any suggestions or feature requests.
Thanks!
Built a quick demo video for the small Forge app I posted about a few days ago.
The idea is pretty simple: sometimes you need to share Jira project status with clients or stakeholders who don't have Jira access. Instead of sending screenshots or manually writing updates, the app generates a public link showing selected Jira issues and their current statuses.
After the feedback on my previous post, I realized I probably didn't explain the workflow clearly enough, so I put together a short video showing the actual flow from inside Jira to the shared external page.
I'm still trying to validate whether this solves a real pain point or if most teams already have a process they're happy with.
A few questions for people here:
• Do you ever need to share Jira task status externally?
• How are you doing it today?
• What would stop you from using something like this?
I'd genuinely appreciate any feedback, criticism, or ideas for improving it.
We have spun up jsm as our service desk tool. One of the main complaints is that users need an atlassian account verified in order to submit a ticket via email.
This happens for both users in our verified mail domain and outside email, Gmail, outlook.com, etc.
Our Atlassian account team had said there is no way around this. It’s a horrible user experience and makes me wonder how others manage this.
I could understand it for agents but not customers.
Thoughts?
I'm fairly new to all this, but was excited to see that you can connect Claude to Atlassian Rovo.
I'm struggling to see how to connect this to trello.
I'm a paid subscriber for trello, so hoping this gives me a way of connecting the two through Rovo, or any other solution for that matter!
Thanks
New research from Adaptavist finds 30% of career changers in the US are considering moving into an industry less exposed to AI
US workforces are facing a massive “white-collar exodus”, as fears surrounding AI are driving knowledge workers to look for alternative professions, new research from digital transformation consultancy Adaptavist reveals.
The research, which surveyed 500 knowledge workers in the US, found that nearly half (46%) are actively looking to change to a different industry due to fear of AI - the highest rate of any nation surveyed and well above the global average of 33% - with 30% specifically considering moving into an industry less exposed to AI, such as manual work.
This flight from white-collar office roles is most pronounced among millennials across the US, with 53% of those aged 30-45 contemplating a career change due to AI-related anxiety.
While much of the focus of AI disruption has been on the impact on entry-level and graduate roles, these findings highlight a broader risk. With Millennials now making up a significant proportion of mid-level and senior talent, businesses face potential disruption not just to early-career pipelines, but to experienced roles that are critical for continuity, leadership, and future business growth.
Hey everyone,
I recently built a small Forge app for a very specific Jira workflow.
Sometimes you need to share the current status of project tasks with clients or stakeholders who don't have access to your Jira workspace. Instead of sending screenshots or manually writing status updates, this app creates a public link that shows selected Jira tasks and their current statuses.
It's a very simple app and I'm still trying to figure out whether this is actually useful for teams or if most people already have a workflow they're happy with.
Here's what it looks like:
I'd love to hear:
If anyone wants to check it out, it's available on the Atlassian Marketplace; I can give a link in the comments.
Seriously, Atlassian. Why are you making me have to explain to our leadership why our employees' faces are being used to market your products to our other employees?
We’re currently looking into moving from Jira and Confluence Server to Atlassian Cloud and I’d really appreciate insights from people who’ve actually done it at scale.
Context: around 2000 internal users and a similar number for external/customer users, with a fairly mature setup (lots of projects/spaces, apps, integrations, custom workflows).
Server EOL + security + maintenance overhead are pushing us in this direction, but the jump in cost obviously makes the decision non-trivial.
For those who’ve gone through it: was it actually worth it?
How did you justify the ROI and get leadership buy-in, especially moving from a relatively low-cost on-prem setup to SaaS? What ended up being the real value drivers in practice?
On the ground, what changed for users? What did they genuinely gain from Cloud, and what did they lose or end up missing?
From an admin/ops perspective, how much did Cloud really reduce the burden vs what Atlassian markets? Any new constraints or surprises?
And on the migration itself, what hurt the most? Apps, integrations, permissions, data structure, anything you underestimated early on?
Finally, looking back now, what do you wish you had asked Atlassian before starting, what hidden costs or trade-offs caught you off guard, and would you still make the same decision today?
Would really value honest experiences, especially from larger orgs where this wasn’t a simple lift-and-shift.
We’re currently looking into moving from Jira and Confluence Server to Atlassian Cloud and I’d really appreciate insights from people who’ve actually done it at scale.
Context: s few thousand internal users and similar number for external/customer users, with a fairly mature setup (lots of projects/spaces, apps, integrations, custom workflows).
Server EOL + security + maintenance overhead are pushing us in this direction, but the jump in cost obviously makes the decision non-trivial.
For those who’ve gone through it: was it actually worth it?
How did you justify the ROI and get leadership buy-in, especially moving from a relatively low-cost on-prem setup to SaaS? What ended up being the real value drivers in practice?
On the ground, what changed for users? What did they genuinely gain from Cloud, and what did they lose or end up missing?
From an admin/ops perspective, how much did Cloud really reduce the burden vs what Atlassian markets? Any new constraints or surprises?
And on the migration itself, what hurt the most? Apps, integrations, permissions, data structure, anything you underestimated early on?
Finally, looking back now, what do you wish you had asked Atlassian before starting, what hidden costs or trade-offs caught you off guard, and would you still make the same decision today?
Would really value honest experiences, especially from larger orgs where this wasn’t a simple lift-and-shift.
Thanks all !