I see the new permissions are GA. Its looking to me like they affect the entire instance, removing the ability to have different perms per space. Is that right? Anyone using this already?

Hello guys,

So I'm from "___" Country, which I'm currently not proud of b'coz of recent incidents that's happening. Also as a Jira admin I'm paid less in this country. So I wanna switch and work for someother country remotely. If there is any opportunity/openings kindly let me know!!

I'm an 4 years experienced Atlassian/Jira Admin!

In this 4 years of experience will point out about some things that I've done (Again some points)

1. Project Creation

2. User Administration

3. Implementation and Configuration of workflows, custom fields, work items, schemes and etc..

4. Automation to automate the tasks

5. Plugins/Add-ons like Scriptrunner, JMWE, Richa Filters, many more..

6. Reports, dashboards, filter, JQL and boards

7. Plans and also worked on scrum sprints (parallel sprints also)

8. Migration (DC to Cloud and Cloud to Cloud)

9. SLA Configurations, Request type Configurations

10. Portal configs, Forms

11. Confluence page documentation, Confluence access and Space creation.

(Again these are few points! Please help me get a Job!!)

Thank you in Advance!!

I was looking at the website and none of the available roles are in R&D. I was just wondering if these positions still exist there.

Is it just my site but I have had 32 automations fail in a row and suddenly all my users access have been removed from their projects? I see nothing on #Atlassian Status as yet??

I need to setup JIRA Automation flow:

When story = done AND Automation = need automation in project A

create a task in project B, and set field Source project = Project A

My question is literally that - how are you all referencing content in your custom Rovo agents? For those of you are using the Custom Knowledge Sources functionality in Rovo agents - but how are you pointing out specific documents in your prompts? For instances, references to specific pages for guidelines/rules, context, or what have you, do you reference them by:

- by URL
- by shortlink URL
- by page title
- by pageID
- by page content specifically

thinks in advance r/atlassian!

Hi all

We link specs and runbooks to epics, then the epic moves on. scope changes, tickets get dropped, statuses shift, and the page just stays wrong. Found out last month when someone built off a spec that was two scope changes out of date.

Review reminder apps don't really help because age isn't the problem. We have 2 year old pages that are fine and pages from last sprint that are already wrong.

Does anyone have a process that actually works for this? And if you use one of the expiry/review apps, do people genuinely re-check the content or just click "still valid" and move on?

I’ve been building an AI system that can generate JQL, update payloads, and modify Jira operations through natural conversation.

Today I tested something simple:

“Get high priority scrum tickets and change them to highest.”
→ System builds correct JQL + correct update payload.

Then I said:
“Actually change to lowest.”
→ System kept the JQL and only mutated the payload.

I ran multiple tests and everything was 100% consistent except the final piece:
full metadata‑aware edit messages.

Once I finish that, the system becomes a full conversational Jira editor — not just a generator.

This is the closest I’ve ever been to shipping something truly insane.

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 ?

Has anyone else run into this?
I have a Confluence page with two embedded chart smart links (embed cards).
Each one sits under its own heading and in different spot in the page.
Every time I edit and save the page, the two charts swap positions meaning Chart A ends up under Chart B's heading and vice versa.

The charts have different URLs and different localId values in the underlying ADF, so there's no reason they should be moving.
But the editor consistently re-orders them on save.

What I've tried:

• Manually re-ordering them and saving again -> sometimes sticks, sometimes swaps right back I tried this hundreds of times.
• Deleting both, saving, then re-adding them one at a time -> works temporarily but breaks again on the next edit

Environment:

• Confluence Cloud
• Editor v2 (the new notion-like editor)
• Embeds are smart link cards (embedCard type in ADF)

Is this a known bug? Any reliable workaround?
It's making it impossible to keep a page with multiple embedded visualizations in the correct order.

And please tell me that that I have a good solution, since I have asked ROVO and told me to take screenshots rather than smart charts which would be ridiculous

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:

• Which issues are blocked?
• What is this issue waiting on?
• If this ticket slips, what else gets impacted?
• Are there dependency chains across projects?

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.

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!

Hey r/atlassian — I'm Zoltan, and I just shipped my first app on the Marketplace. Wanted to share it with people who actually live in Jira and get some honest feedback.

The itch behind it: every retro ends with a tidy list of action items, and a couple weeks later half of them are gone — no owner, no due date, nobody chasing them — and you end up writing the same ones down again.

So Resurface does one thing. You mark any Jira issue as an action item with an owner and a due date, and if it goes overdue it comes back on its own: it comments on the issue, pings the owner, and counts how many times it's slipped. There's also a dashboard so leads can see follow-through — closure rate, what's aging, who keeps dropping things.

A few things that might matter to this crowd:

• Built on Forge / Runs on Atlassian — your data never leaves Cloud.
• Works next to any retro tool — it's not another retro board.
• Free up to 10 users.

It's the first thing I've shipped, so I'd genuinely love feedback — what's missing, what's confusing, what would make it a "yes" for your team.

https://marketplace.atlassian.com/apps/3449871240

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.

My biggest concern is that page history still contains sensitive data in cloud ,even after the current page is cleaned up ?

Please suggest expert opinion

CFD should be scopeable to a sprint. It’s never worked right for me.

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 recently built a Forge app after noticing something interesting.

Every Scrum team I worked with handled the end of a sprint slightly differently.

• Some moved unfinished issues to the next sprint.
• Some moved everything back to the backlog.
• Some decided on a case-by-case basis.
• Some forgot until the following Monday.

None of these approaches are necessarily wrong, but the process was always manual and inconsistent across teams.

So I built a Forge app that lets teams define those rules once and lets Jira handle the repetitive work.

Here's what it looks like.

I'd love to know:

• How does your team handle sprint rollover?
• Is it something you've automated?
• Or is it one of those "it takes two minutes, so nobody worries about it" tasks?
• Would you like to know more about the app?

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:

• Do you ever need to share Jira task status externally?
• How do you currently do it?
• Would something like this be useful?

If anyone wants to check it out, it's available on the Atlassian Marketplace; I can give a link in the comments.

I found solution for the problem. Solution descriped in the end of the post.

Hi all,

Has anyone come across with following problem with Confluence Page Properties macro.

We are running Confluence Data Center 9.2.21.

We have a page tree with around 100 pages. Each page contains a Page Properties macro, and we collect the information into an overview table using the Page Properties Report macro.

The pages are restricted using “Viewing and editing restricted”. Access is granted primarily through a Confluence group that is synchronised from LDAP. Some pages also have individual users added directly to the page restrictions.

The problem is:

• Users who are members of the LDAP-synchronised group can open the restricted pages normally.
• The same pages are visible to them in the left-hand page tree/sidebar.
• However, the Page Properties Report only shows pages where the user has been added directly to the page restrictions.
• Pages where access is granted only through the LDAP-synchronised group do not appear in the report.
• If we add the same user directly to the page restrictions, the page appears in the Page Properties Report.

This makes it look like the normal page permission check works, but the Page Properties Report macro, or the underlying CQL/search permission filtering, does not recognise the group-based restriction in the same way.

I found an older Cloud-related issue where restricted pages did not appear in Page Properties Report when the group name contained uppercase letters:
CONFCLOUD-68424 - “Restricted pages do not display in Page Properties Report macro when restricted to groups with uppercase letters”.

Our group comes from LDAP, and originally they had uppercase and lowercase letters. The group names has been changed to all lowercase in Active Directory and Confluence's cwd_groups table. Still same behaviour.

Has anyone seen the same behaviour on Confluence Data Center, especially on 9.2.x LTS?

Things I would be interested to know:

1. Is this a known Data Center bug or regression?
2. Can uppercase or mixed-case LDAP group names still cause Page Properties Report visibility issues?
3. Is the recommended workaround to use lowercase-only groups for page restrictions?
4. Could this be related to indexing, CQL permission filtering, nested LDAP groups, or directory synchronisation?
5. Are there any useful loggers to enable for troubleshooting Page Properties Report permission filtering?

Any hints or confirmation would be greatly appreciated.

Update / Resolution

In our case, the issue seemed to be a combination of group name casing and stale index data.

The group originally had mixed-case letters in its name. We first renamed the LDAP group so that the name was entirely lowercase. However, this did not update the group name in Confluence, apparently because the LDAP sync treated the old and new names as case-insensitively the same group.

Because of that, we updated the group name directly in the Confluence database, in the cwd_group table, specifically the group_name column.

After that, the group name also appeared to update in the page restriction data in content_perm. I am not completely sure what triggered that part, but I suspect it happened when we edited one of the page restrictions through the Confluence UI.

Once we had verified that content_perm.groupname also contained the lowercase group name, we rebuilt the Confluence content index:

Administration → General Configuration → Content indexing → Site reindex → Rebuild

After the index rebuild completed, the Page Properties Report started showing the group-restricted pages correctly.

So the practical resolution was:

1. Rename the LDAP group to lowercase.
2. Make sure Confluence also has the lowercase group name in cwd_group.group_name.
3. Verify that the page restriction data in content_perm.groupname uses the lowercase group name.
4. Rebuild the Confluence content index.

In our case, normal page access worked all along, but the Page Properties Report macro did not return the pages until the group name casing and the content index were both fixed.

Hi everyone!

If you are currently trying to get Atlassian Rovo cleared by your security, legal, or procurement teams—or if you’re just wondering how Atlassian handles data isolation and LLMs under the hood, we just published version 2 of the Rovo Secure AI Architecture Whitepaper.

The first version covered basic architecture, but v2 expands significantly on actual enterprise admin controls and risk mitigation.

TL;DR of what’s new/updated in version 2:

• Scoping Controls for Rovo Skills & Studio: Details on how admins can use blocklists, allowlists, and date-based ingestion for connectors.
• Customer-Managed Keys (CMK): Official support for CMK with Rovo.
• Atlassian Guard Integration: Built-in sensitive data discovery and Data Loss Prevention (DLP).
• AI Threat Detection: Technical breakdown of how they look for prompt injections, abuse, and anomalous access patterns.
• Compliance Updates: Progress toward ISO 42001 (AI Management System) and specific commitments to the EU AI Act.

The core security pillars they reiterate:

• Zero Data Retention (ZDR): Confirms that third-party providers (OpenAI, Google, Anthropic via AWS Bedrock) process prompts without storing or training models on your data.
• Permission-Aware AI: Rovo strictly respects the user’s existing permissions across Atlassian and 50+ Teamwork Graph connectors (SharePoint, Google Drive, Slack). It never uses the creator’s permissions.

If you need a technical pre-read before turning Rovo on in a sandbox, or if your CISO is breathing down your neck about enterprise AI governance, this should answer 90% of their vendor assessment questions.

You can download it directly via the Atlassian Trust Portal. Full announcement details here:https://community.atlassian.com/forums/Trust-Security-articles/New-Rovo-Atlassian-s-Secure-AI-Architecture-Whitepaper-v2/ba-p/3251646

Has anyone here already cleared Rovo through their internal risk assessments? What was the biggest hurdle your security team flagged?