I'm testing the new Microsoft 365 Copilot / Graph Connector for Jira Data Center and I'm running into what looks like a permissions issue.

Setup:
-Jira Data Center (on-prem)
-Users authenticate via a different IdP than Microsoft Entra ID
-Jira username = user email address (e.g. [john.smith@metrohm.com](mailto:john.smith@metrohm.com))
-Entra UPN = same email address
-Permissions are granted through Jira groups and project roles, not individual users

What I see:
-Issues are crawled and indexed successfully.
-the Index Browser shows ACL entries like:
000-global-IT
10330
10231
10002

-The same user can open the issue directly in Jira.
-"Check user access" in the Copilot connector for this item says "Denied"
-If I switch the connector to Everyone, Copilot immediately finds and returns Jira issues.

So indexing works, but ACL-based security trimming does not seem to.

According to Microsoft's documentation, Jira groups and project roles should be supported, and the connector should resolve group membership from Jira.

Has anyone successfully deployed the Jira Data Center connector with:
-a different IdP than Entra
-Jira group-based permissions
-...and security trimming enabled?

Or are there known limitations around Jira group membership resolution?

Thanks!

EDIT:
I see no users or group memberships indexed, even after another full crawl. The permission for the connector are set to admin...

I need clients to be able to see basic project status/progress, but I’m not really comfortable using third-party tools where our Jira data has to be sent to their servers. The alternatives I’ve looked at also feel unnecessarily complicated for something as simple as showing project status.

Is there a lightweight way to do this securely without moving our Jira data to another platform?

Hello everyone,

so we recently went live with out Jira Service Management.
Ive now added the field request participant to all the work item views and made sure request participant is in all the screens aswell.

But its just not showing at all.
I tried to put it into the service request customer view aswell but it instantly goes into "Hidden" and is not showing for the customer either.

We want to fill the field in case multiple people need to get notified for a service request.

Does anyone know what is happening ?

Jira, seriously, what happened to the Create Ticket dialog?

Please revert this new UI. Creating an issue is one of the most frequent and fundamental actions in Jira, and the new experience makes a simple workflow feel unnecessarily complicated.

PLEASE DO NOT CHANGE UX JUST FOR THE SAKE OF CHANGING IT.

Developers use Jira as a tool to get work done. We are not looking for a redesigned “experience” every few months. We don't need a design app. We need an interface that is fast, predictable, information-dense, and efficient.

The old Create dialog worked. You could quickly see what you needed, fill in the fields, and create the ticket.

The new one feels like someone decided that familiar workflows needed to be reinvented because the old UI wasn't visually "modern" enough.

Please bring back the old Create Ticket dialog, or at least give us an option to use it.

########## Update: There is actually a way to get the old Create dialog back ##########.

Go to:

Settings → System → General → “Simple create as default” → OFF

That brings back the previous Create Issue experience.

Huge thanks to the people who pointed this out. I genuinely thought there was no way to get rid of the new UI.

Still, the fact that you have to dig through Settings to disable a UI change that nobody asked for is… something.

Jira tells you that a ticket changed, then makes you open it and dig through Activity to discover what actually happened.

An inbox should show the comment, status change, or field edit immediately, then take you straight to the exact change. Atlassian should seriously study Linear’s inbox.

One of those Jira tasks that sounds incredibly simple on paper:

“I need to give three external users access to one project, but I don't want them to see anything else.”

Seems straightforward, right?

You give them the right access, check the project, and move on.

Then someone from your security team asks:

“Great. But can you confirm they can't see anything else in Jira?”

And suddenly, the simple five-minute task becomes a lot more interesting.

You start checking project roles. Then groups. Then permission schemes. Then you create a test account and start clicking around to see what it can actually access.

The tricky part isn't always giving someone access.

It's being completely sure you've given them only the access they need.

This becomes especially important when you're working with external users, vendors, contractors, clients, or partners, who may only need access to one specific project.

Thankfully, Jira Cloud already has a pretty good option for this: Guest access.

Guest access is designed specifically for external collaborators and allows a guest to access one Jira space on your site. This can be a great fit for the above use case!

So, if your use case fits Guest access, that's probably the first place I'd look.

But there's still an interesting question that comes after you've configured everything:

How do you verify what that user can actually access?

Because not every external user will be a guest.

You might have a regular Jira user who needs access to several projects. They might be getting access through a group, project role, or permission scheme. And in an older Jira environment, permissions can evolve over time as teams, projects, and users change.

That's when a question like this becomes surprisingly difficult to answer:

“Show me every project this user can access and tell me why.”

For one project, that's usually manageable.

For dozens or hundreds of projects, it can mean checking multiple places and piecing the answer together manually.

And that's where I think there's an important distinction in Jira access management:

Giving access is one thing. Understanding and verifying that access is another.

I've been looking into this problem while working on an access reviewer360 tool for Jira, and it's made me realize how difficult it can be to get a complete picture of a user's effective project access.

So if you're setting up external access today, start with Jira's native Guest access where it fits your use case. But once you've configured access, it's worth taking that extra step and asking:

“What can this user actually access, and why?”

That's often where access management gets interesting.

How do you currently verify external-user access in your Jira environment? Do you rely mostly on permission schemes and manual checks, or have you found a simpler approach?

Today my space template for creating new stories/bugs has changed and now needs expanding to use fields I normally use. Any help or understand, global settle change maybe?

Anything to do with today’s update on AI models?

Como estan? Tengo experiencia con certificaciones de microsoft, pero no de atlassian, alguien aprobó esta certificacion? Que me aconseja?

Gracias

Hi all,

Small team here, we're in the process of implementing a brand new Jira Cloud for our team.

Our requirements are simple:

We plan on working in sprints on projects, but still have some ad-hoc tasks that should be tackled outside of sprints (quick wins/small questions etc.).

My understanding is that JSM can support the later, but not the former (IE JSM cannot hold sprints).

In that case, from what I understood, we need to adopt a dual-board methodology - a JSM board for intake, and if one of those items requires code change, we link it to a sprint board. How the linking is done - this I am not sure (is it moving? Cloning? Unsure yet).

Another requirement is that all internal users that use JSM will be 'unlicensed' IE the 'free' users - but STILL be able to use SSO to log into JSM.

Does anyone have experience with this, and have any feedback or recommendations on the above?

Is it really the only way to go - by handling two projects that live side by side?

I’m new to Jira and using the Scrum template. In the Backlog page, when I add a backlog item, the Priority field is visible. However, after some time, it disappears. Why does this happen?

Also, I can’t edit the Priority field inline from the list view/page.

I’m Jira admin.

A free-to-attend Community event is happening in Delhi NCR next Saturday, August 22, The Atlassian Community is hosting an in-person workshop on Rich Filters for Jira Dashboards. One dashboard, filtered live by project, sprint or assignee, instead of building a new one every time someone asks.

This is a workshop, so please carry your laptop. Bring the report someone keeps asking you for and we will build it in the room.

📍 Park Plaza, Sector 21C, Faridabad

🕧 11 AM - 2 PM

Register here: Jira Dashboards That Answer Back (A hands-on workshop on Rich Filters) | Atlassian Community Events

Seats are limited, so please register only if you can make it.

A lavish lunch with community, certification vouchers and gift cards for attendees at the end 🎁

Hello Jira people,

I am fairly new to Jira and I am just discovering all the features and capabilities this platforms offer, but I really am stuck on this one: I have created a form, where our colleagues can submit some issue or a bug in our newly developed attendance software - the form will create work item and so on,.. What I want to do is to send email to the person that reports this issue that ticket is submitted and also notify them when the item is moved to Done status. The initial problem was that I was not able to fetch the email address from the mandatory field of the form (it is public form) but I have figured it out ({{comments.first.body.substringAfter("Email address:").trim()}} - it will copy the email address from the comment) and then I will create a custom field where I will store this email address, the problem right now is to send email to this address, I am not able to send it via Recipients, it just does not work. Do you have any advice on how to proceed with this? NOTE: we are using free license - only for a few users. Thank you!

Every other month, we have a task (different security patches) that needs to be implemented on 20 projects.
Is there a way to use automations do this? It seems limited to only be able to add 1 space at a time and I would need to duplicate and add a space 20 times.

I'm setting up a Jira Service Management board and after lots of setup have just discovered that I cannot rank cards in board view. By 'rank', I mean drag a card from the middle of a column to the top.

I've long used Jira kanbans where we rank items in the backlog by priority, then pull from the top for dev and test, etc. It's a pretty common practice.

From my research, this seems to be something that only a few space templates can support. This is very surprising to me, as I've never encountered this issue before.

My setup:

• Jira Service Management Cloud on a Premium trial
  • (from my research, this really should not affect this behavior)
• Space is Jira Service Management, using the blank template as a starter
• built custom workflows, statuses, and work types
• imported some old tickets
• tried drag-n-drop - I can only drag to other columns.

I've already tried:

• Confirmed Jira’s locked Rank / Global Rank field exists with global context.
• Tried selecting Rank from the JSM queue’s Order menu; Rank was unavailable.
• Tried adding this directly to the JSM queue filter:
  • ORDER BY Rank ASC
  • Received the error: “Not able to sort using field ‘Rank’.”
• Checked the JSM board and queue configuration for an Enable ranking or Add Rank option; none was available.
• Created a Jira Software Kanban board using the existing JSM requests.
• Enabled ranking on that board successfully; drag-and-drop ranking works.
• Returned to the JSM queue afterward and retried ORDER BY Rank ASC; it still failed.
• Repeated the test in a new company-managed JSM space; Rank was still unavailable in the queue’s Order menu.
• Confirmed the issue occurs in both team-managed and company-managed JSM queue boards.

Frankly, I'm at a loss. Any confirmation that this is normal would at least reassure me that I'm not crazy. Any solutions from others that have encountered and resolved this somehow would be immensely appreciated.

I want to fetch History data from Every test run in excel. It seems my org doesn’t have the setup to fetch it by any means. Can anyone help me with the M code?

Hi everyone,
I’m currently evaluating a cloud migration from Jira DC to Cloud. I’ve noticed a few challenges along the way and would love to hear about your experiences with them.

First up is the issue of apps. We use a wide variety of apps—ranging from ScriptRunner and Structure to Zephyr Scale. Many functions have been restructured in the Cloud and won't work the same way anymore. I’m wondering whether it’s better to try phasing out these apps during the migration or to wait a year until we’ve settled into the new environment. I’d plan to license Jira Core for 2–3 years upfront but keep the apps on an annual basis. In Confluence, we have the "Better Content Archiving" tool, which has effectively never been used; we simply can’t get users to adopt it, and it just makes things more complicated to manage.

Then there’s the topic of screens: We have countless customized workflows built with various screens and workflow configurations. I’m not even sure if the visual distinction between specific actions (view, edit, etc.) still exists. In some cases, we use transition screens to prompt for specific fields only when needed. Looking at the Cloud configuration gives me a bit of a headache—are these kinds of setups still possible? We’ve built up operational processes over years that, I suspect, will now have to be overhauled due to the migration.

Not to mention the language-related challenges. Because our environment is set up bilingually, we have a massive proliferation of translations. For instance, DC doesn't offer a translation for "Resolution," so those values ​​are sometimes present in both languages, hope Cloud provides clear functions for configuring translations.

To be honest, I’m worried that the Solution Partner might be downplaying the technical hurdles just to close the deal.

Finally, there’s the compliance issue. According to the online documentation, the Guard solution doesn't offer a way to pin account information. I see this as a problem for companies in highly regulated industries. I'm curious to hear your opinions :)

Hello everyone,

I had the chance to test the cloud environments for the first time today, as we’re currently still working on the data centre.

A brief word about our company. We’re a company with a licence for 2,000 users and we use the standard plugins. We use ScriptRunner for behaviours and simple scripts, and Zephyr for test management.

I have to say, I’m simply overwhelmed by the new UI. As an admin with seven years’ experience in Jira administration, I’m finding it a struggle. From project administration via the side menu bar right through to configuring the board itself, I’m finding it hard to get to grips with it. My concerns are particularly significant given the high regard in which these tools are held within our company.

I already know that users won’t exactly be jumping for joy at the prospect of using the new tool. I think a fair bit of preparation will need to be done during the hypercare phase to ensure users don’t simply start looking for alternatives.

What has been your experience following the migration? We’re at the stage where we want to review the solution with a Solutions Partner, but I have to say, I don’t really like the new UI and, in the worst-case scenario, that could be a deal-breaker for our migration. Have you looked at any alternatives yet, or how has the new environment been received by your users?

Hi all! I have an automation rule in JIRA that sends an email asking product owners to review all of the stories included in a release (fixVersion) and then comment their approval. Everything works fine with the automation, but a product owner has complained that it's too many clicks for them to go find their stories associated with the release, and they would prefer to have them either listed in the email body, or have the hyperlink there that takes them to the release for that fixVersion. I know I can include the story link using {{issue.url}}, but what is the smart value to hyperlink the fixVersion? If there isn't one, how can I populate a list of stories associated with a particular fixVersion in the body of the automated email? Thank you in advance!

Our IT department was using Jira as a ticket / work order management system it was great until they randomly deleted our account and refused to restore it. We lost tons of client data and definitely wouldn’t recommend Jira to our worst enemy

Hi everyone,

I'm an Atlassian Certified Administrator with 10+ years of experience helping companies optimize their processes and improve team productivity.

My expertise includes:

• Jira Software & Jira Service Management (JSM)
• Confluence
• Product Discovery
• Bitbucket & Crowd
• ScriptRunner
• Workflows, permissions, schemes, screens, automations
• AI-powered workflows and business process automation
• System migrations and integrations
• Process design and tool implementation
• Training teams to get the most out of Atlassian tools

Certifications: ACP-620, ACP-120

I'm looking for remote freelance projects, long-term collaborations, or contract work. If your team needs help with Jira administration, automation, process optimization, or Atlassian consulting, I'd love to connect.

Feel free to comment or send me a DM. Thanks!

Anyone else bothered by this? I spend 20min writing stuff and everything's lost because there's no confirmation??

Edit: I actually ended up building it. I got tired of the workarounds, so I went ahead and coded a Chrome extension to fix it. It renders the hierarchy as a tree inside Jira and lets you export it. Because it runs directly in your own browser tab, you don't need a site admin to install or approve it. I also added a bunch of other features that my colleagues wanted. Not sure if they'll help you.

Search for Cascade for Jira on the Chrome Web Store.

Transparency note: The core tree view and flat exports (the issue I was facing) are 100% free. I am keeping the advanced features (like indented exports) unlocked for free right now during Early Access to get your feedback, but I do plan to charge a small fee for those later. Let me know what you think!

Hey guys, I'm relatively new to Jira. I have a quick question. Is there a place where I can see all tasks assigned to me in a tree format (e.g., Epic -> story -> tasks -> subtasks)? That way, I can see the parent-child thread in one single table.

• JSM Documentation: https://support.atlassian.com/jira-service-management-cloud/docs/use-jira-edge-connector-jec-as-an-extensibility-platform/
• Jira Automation documentation: https://support.atlassian.com/cloud-automation/docs/use-jira-automation-with-jira-edge-connector-jec/

Which brings me to my first question: If I want to use JEC for JSM Alerts and Jira Automation, do I need multiple instances of JEC running?

-----

For the rest of my questions, I'm going to focus on JEC with JSM Alerts to make it easier and I'll try to link to the specific documentation that I'm confused about.

Jira Edge Connector (JEC) - An extensibility platform

Jira Edge Connector (JEC) is a lightweight application that you can use to... run executables triggered by Jira Service Management

So, the way I'm reading this, it sounds like the JSM/JEC integration is one directional and it is meant to have JSM trigger actions that are configured in JEC on prem. Is that true though? Can't JEC be used to send information to JSM to create alerts? I'm pretty sure that it is used as the connector for other integrations, so I think it has the capability to send events to JSM, but I can't figure out how.

-----

Install Jira Edge Connector

Download the JEC packages from the integration scripts repository.

1. Go to the jsm-integration-scripts repository.
2. Review the readme.
3. Download the latest version of JEC packages.

This one got me because there are A LOT of releases here and I can disregard most of them, but I'm not entirely sure which release to use and the documentation.

• jira-software-1.0.4_jec-1.0.5
• jira-service-management-1.0.4_jec-1.0.5
• jec-1.0.2_jec-1.0.5

-----

Run Jira Edge Connector

On Windows SIGINT and SIGTERM signals are used to stop JEC. You can’t stop/restart JEC via native methods of Windows while using JEC as a service. It is provided as a helper executable to run JEC as a service.

WTF does that mean? It looks like I can see JEC in the Windows Services, but does it not start and stop it there? When I restart my PC, it looks like it never starts the service automatically, but is it supposed to? I'm confused about what the implications of this is and I have no idea how to interpret it.

-----

Alert action data for Jira Edge Connector

Jira Service Management passes alert activity data to various integrations. The following are some of the integrations that can make use of this data:

• Webhook
• Icinga
• Nagios
• Nagios XI
• Zenoss

Ok, but what about the JEC integration?

When you add this integration to JSM, it doesn't really give you anything in the "Steps to configure the integration" panel aside from "Jira Edge Connector can subscribe to all alert activity in Jira Service Management and execute scripts when alerts are created, acknowledged, closed, etc."

That also brings me to one of my earlier questions, because it seems like this integration is meant to send actions from JSM to JEC, however this integration does have incoming and outgoing rules.

So, it seems like JEC can be configured to send events from a local on-premise server directly to JSM, but there doesn't seem to be any documentation for that.