rss.livelink.threads-in-node

An auditor asks who could access a Jira project last March. Can you answer?

Abaho Katabarwa _Katabarwa Labs_ — Sat, 12 Sep 2026 10:00:00 GMT

An auditor asks something that sounds simple: show me everyone who could access the Payments project on March 3rd. If that date is more than about six months back, Jira only shows access as it is right now, never as it was. The audit log retains roughly 180 days, then the event is gone.

Raising that cap is a long-standing open request: JRACLOUD-68267 has been gathering votes for years, about 226 and counting. And access is rarely direct: a user sits in a group, the group holds a project role, the role grants access, so answering who could reach a project on a given day means replaying change events and expanding every group as it was then.

You can build the evidence yourself: on a schedule, enumerate projects, read each role's actors, expand groups to effective users, store each day's matrix keyed by date, and diff each run against the last. It works, but you now operate a scheduled pipeline with rate-limit handling, per-project failure isolation, retention, and pruning, forever, and a missed week is an unanswerable week.

Disclosure: I work for Katabarwa Labs, and we build a small app for exactly this gap, so treat it as one option among whatever you evaluate.

Access Snapshot & Drift takes that daily snapshot for you: every project's roles, group grants, and effective users (groups fully expanded), stored under its date and retained by default around 400 days, well past the native cap. Pick any retained date and read its access matrix back verbatim, review each run's drift (users and groups added or removed per role) as a delta instead of a re-audit, and export any date to audit-ready CSV. It runs on a Forge scheduled trigger inside your own tenant, so nothing leaves your instance, and the snapshot and reporting path is read-only.

Listing, if it helps: Access Snapshot & Drift. If the snapshot or export shape is not quite what your audit needs, tell us and we will build it.

Screens say whether, layouts say where — so which one is hiding my field?

Hugo Mora — Fri, 11 Sep 2026 16:24:39 GMT

Hi everyone,

The most common question I get from project admins is some variant of "I added the field, why can't I see it?" And the honest answer is that there are at least five places it could be dying, in a specific order, and you have to check all of them.

Field context (is the field even scoped to this project and work type) → field configuration (is it hidden) → the screen (is it on the right one for create/edit/view) → the screen scheme and work type screen scheme (is that screen actually associated here) → and now the layout (is it placed in a section, and which one).

Five layers, two different admin roles, and no single page that tells you the answer. The old "Where is my field?" helper answers part of it, but nobody I train remembers it exists.

So why do layouts exist at all?

I think the reasonable answer is that screens were designed for a form. A screen is a membership list plus an order, rendered top to bottom, and that model worked perfectly when creating, editing and viewing were three separate pages that each looked like a form.

The current work item view isn't a form. It's a page with regions — description, a details panel, context, more fields. Screens simply can't express "put this in the sidebar," because position wasn't a concept they were built to carry. Layouts were the answer to that: the docs are explicit that the fields available to you in the layout come from the global screen configuration for viewing the work type. Screens decide whether a field exists here; layouts decide where it lands.

That's a defensible split. The problem is everything around it.

What it costs in practice:

Ownership is split down the middle. Jira admins own screens and tabs; project admins own layout. So the person who can move a field often can't add it, and the person who can add it isn't the one being asked.
The blast radius is genuinely unclear. The documentation says layout settings are for individual projects, but there are multiple threads here from admins who changed a layout and got warned it would affect other projects sharing the same screen scheme — and it did. I've seen both behaviours and I still can't state the rule confidently, which is not a great place to be when you're advising a client.
The layers leak into each other. Add a field in the layout editor and Jira quietly adds it to the underlying screen for you. Remove a field from the edit screen and it can still sit there in the view configuration, visibly present and mysteriously uneditable.
Hiding in a layout is cosmetic. It's not a permission and not a data control. The field is still there via API, automation and bulk edit. I've had to explain that one in a compliance conversation.

What I'd like to hear from this group:

Have you settled on a policy — configure everything through screens and treat layout as cosmetic, or lean on layout and let it manage the screen for you?
For those running many projects that must look identical: how are you keeping layouts in sync? Copy layout gets you the first version and then drift starts on day two.
Has anyone actually nailed down the shared-screen-scheme behaviour? A definitive answer with a test case would be worth a lot to this forum.
And the bigger one: if the view is no longer a form, is there still a reason for screens and layouts to be two separate models — or is this a merge waiting to happen?

Thanks,

--Hugo

Bring External Systems into Jira with Action Hub

Eva — Fri, 11 Sep 2026 15:29:05 GMT

What if Jira could do more than display the information already stored in it?

Most teams rely on multiple systems to run their day-to-day operations. Identity providers, endpoint management platforms, CRMs, and workspace tools all contain information that Jira and Jira Service Management teams need to act on.

The problem is usually the same: the data is there, but it is somewhere else.

That's where Action Hub for External Systems comes in.

Action Hub connects Jira and JSM to external systems and brings their data and actions directly into the work item experience. Instead of copying external information into Jira or switching between applications, teams can search external records, display relevant attributes, run approved actions, and use the results in Jira Automation.

Connect. Contextualize. Act.

Action Hub is built around a simple idea: external systems should become part of the Jira workflow rather than another place agents have to visit.

Connections provide authenticated access to external systems, while reusable field templates define how that data is presented and searched in Jira.

This means an administrator can create a field that searches a connected system, presents the relevant information to the user, and exposes only the actions that have been approved for that workflow.

For example, a Jira Service Management request could include an Entra Users field. An agent can search for an employee directly in the request, select the relevant identity, view the configured user information, and access available Entra actions without leaving Jira.

Govern the actions, not just the connection

Connecting an external system is only the beginning.

External platforms can expose a wide range of operations, and not every action should be available to every Jira workflow.

Action Hub provides layered control over external actions, allowing administrators to govern availability across the action catalogue, connection configuration, and individual field templates.

This creates a model where:

Available actions → Connection permissions → Workflow-specific actions

Read-only operations can be exposed for investigation and lookup, while higher-impact write actions can be restricted to the connections and workflows where they are actually required.

The result is an integration that is not simply connected, but controlled.

Turn external data into automation

One of the most useful parts of Action Hub is what happens after an external action runs.

The result can be passed directly into Jira Automation.

Take a simple identity workflow:

Employee selected in Jira → Get user's manager → Manager returned from Entra ID → Jira Automation uses the result

The external response can provide structured data that automation can then use for assignments, conditions, field updates, notifications, or other workflow logic.

For example, the manager's email returned by Microsoft Entra ID can become the input for Jira's Assign work item action.

This turns an external lookup into an automated Jira workflow rather than simply displaying information to an agent.

And it doesn't have to stop at one system

Action Hub also supports cross-connection workflows, allowing a field to use one external system as its primary source while exposing approved actions from another connected system.

Think:

Entra ID + Intune for identity and device workflows
Entra ID + Google Workspace for employee administration
Identity providers + business systems for access workflows
External user or device records + Jira Automation for operational processes

The goal is not to recreate every external system inside Jira.

The goal is to bring the right context and the right actions into the place where the work is already happening.

Built for Jira and JSM teams

Action Hub gives administrators the building blocks to create reusable integrations without turning every project into a separate integration.

With connections, field templates, governed actions, cross-connection capabilities, and Jira Automation support, teams can build workflows around live external data while maintaining control over what is exposed and how it is used.

The Microsoft Entra manager lookup is just one example.

The same pattern can be applied to onboarding, access requests, endpoint support, identity management, workspace administration, and other workflows where Jira needs to interact with systems outside Atlassian.

Connect your external systems. Bring their data into Jira. Turn the results into action.

For the full configuration and implementation details, see the Action Hub documentation: https://piosoftware.atlassian.net/wiki/spaces/WS/pages/1239220226/Action+Hub+for+External+Systems

Ready to connect your external systems to Jira? Install Action Hub for External Systems from the Atlassian Marketplace and start bringing external data and actions directly into your Jira workflows.

JSM Automation - Multiple Request Participants from comma-separated emails using an Advanced Branch

Lucas Cardoso Soares — Fri, 11 Sep 2026 14:50:29 GMT

Hi everyone,

I am investigating an issue in Jira Service Management Cloud related to populating the Request participants field from a text field containing multiple email addresses separated by commas.

I was able to reproduce the behavior in a test environment and isolate the issue.

The automation flow is:

A text field receives multiple email addresses separated by commas.
An Advanced Branch iterates over the values using a smart value similar to:{{issue.FIELD_NAME.replace(" ","").split(",")}}
For each email, the automation calls:
GET /rest/api/3/user/search?query={{emailParticipante.urlEncode}}
The request returns HTTP 200 and a valid accountId.
The automation then calls:
POST /rest/servicedeskapi/request/{{issue.key}}/participant

Request body:

{ "accountIds": [ "{{webResponse.body.first.accountId}}" ] }

The issue is that when multiple emails are processed, only one participant remains in Request participants, even though both GET requests return valid users and both POST requests return HTTP 200.

I also tested storing the accountId in a variable inside the branch:

accountIdParticipante = {{webResponse.body.first.accountId}}

Then I used:

{ "accountIds": [ "{{accountIdParticipante}}" ] }

In this case, each branch preserved the correct accountId, but the final result still contained only one participant.

As a comparison, I tested a single POST request with multiple fixed accountIds:

{ "accountIds": [ "accountId1", "accountId2" ] }

This worked correctly.

HTTP 200 was returned, the response showed size=2, and both participants were successfully added to Request participants.

Because of this, my current hypothesis is that the issue is related to parallel execution of Advanced Branch iterations, where multiple updates to the same request may interfere with each other.

I also tested using an auxiliary text field to accumulate the accountIds before performing a single POST request, but the updates inside the branch were still inconsistent.

Has anyone successfully implemented a similar scenario?

I am mainly looking for guidance on:

How to reliably resolve multiple email addresses into accountIds and then perform one single POST.
Whether an Advanced Branch can be processed sequentially.
Whether there is a recommended way to collect values from multiple branch iterations.
Whether using two chained automation rules would be a better approach.
Whether there is any known limitation involving webResponse, variables, or updates performed inside parallel branches.

Any examples or guidance would be greatly appreciated.

Thanks!

Jira Automation “Send customised email” fails for all recipients

Jan Stożek — Fri, 11 Sep 2026 13:24:29 GMT

Hi,

We are configuring Jira Service Management Cloud on the Free plan.

Standard Jira/JSM email notifications are working correctly and outgoing email is enabled. However, the Automation action “Send customised email” consistently fails.

We reproduced the issue with a minimal test rule:

Actor: Automation for Jira
Trigger: Manual trigger from work item
Action: Send customised email
Recipient: manually entered external Gmail address
Subject: static text
Body: plain static text
No smart values or other conditions

The audit log returns:

“We couldn't send emails to any recipients. This may be for data privacy or recipient email account configuration reasons.”

The same issue occurs when using Assignee or Reporter as the recipient, as well as when using regular email addresses from the company domain. Changing the rule actor from Automation for Jira to a licensed user makes no difference. Other automation actions seem to work correctly, so far.

What else should we check to make the customised email go out?

Looking forward to seeing your suggestions.

Thank you very much in advance for your help.

[Giveaway] File Field for Jira - custom attachment fields for Jira Cloud

Contextra Labs — Fri, 11 Sep 2026 13:14:32 GMT

Hi everyone,

we built a Jira Cloud app file field for jira that adds configurable file/document custom fields , with options such as file limits, file type restrictions, and preview.

The app is already available on the Atlassian Marketplace. I've recently made several improvements based on early user feedback, and I'm looking for a few Jira users/admins to try the current version and share honest feedback.

If you'd like to try it with your company's Jira Cloud environment, I'm happy to provide a free access voucher.

No obligation to purchase or leave a review - I'm mainly looking for genuine feedback from people who actually use Jira.

If you're interested, DM me and I'll send you the Marketplace link and free voucher.

Thanks : )

Hi I am unbale to create API token

Dnyaneshwar Jogdand_ Vodafone — Fri, 11 Sep 2026 13:14:04 GMT

here i am getting error while creating token

We just forged an upgrade for PlantUML Diagrams for Confluence

Boris Jockov — Fri, 11 Sep 2026 14:22:51 GMT

Greetings fellow diagrammers,

We're happy to announce the latest release of PlantUML Diagrams for Confluence for Confluence cloud.

The aim of this release was to move the app to the Atlassian Forge platform as well as the full redesign of the UI. Furthermore, this release paves the way for the integration with AI agents.

What's new

Diagram editor design. And a splash screen.

The look and feel of the diagram editor is already familiar to all Confluence users.

Click the diagram name to reveal the rename feature.

Navigate your GitHub and GitLab repositories with ease.

New editor also features enhanced support for dark theme, for all you night time diagrammers.

Egress visibility

From this point on, the app will be using a new backend registered in the app's manifest. This means increased visibility where your diagram text is sent to rendering.

Same privacy policies apply as before. Zero data retention.

We should note that this egress is a consequence of the nature of the PlantUML library. And that is changing quickly. We're closely watching the progress of the client side implementation of the library. Once it's mature and ready for production, egress will be a thing of the past.

Editions

Standard edition gives the basic diagramming experience, which will include AI diagramming.

Advanced edition enables integrations with repositories such as GitHub, GitLab and Bitbucket(soon).

Compatibility

The app retains backward compatibility. Diagrams made with the previous version of the app will work without any additional work needed.

What breaks

Technically, this is a new app running on a new infrastructure. This means, connections previously made with repositories like GitHub or GitLab will break. Simply navigate to the admin page and reconnect using provided instructions. This was imposed by the Forge architecture and it only takes a few minutes to reconnect.

What's coming soon

Diagramming support for AI agents for Standard edition. Are you using Claude Code, Codex or Rovo? We'll get you covered.

Bitbucket support for Advanced edition. Similar to what's already implemented for GitHub and GitLab, user will be able to source their diagrams from Bitbucket repositories as well as reference them using !include directive.

Ending note

While much has been done to improve the UX, we're constantly working to continue to improve it. If you feel like there's something we're missing in terms of features, drop us a feature request and well get on it.

Happy diagramming,

Stratus Add-ons team.

The new issue transition screen toggle - choosing your experience (new vs old)

Christine Kong — Fri, 11 Sep 2026 12:40:29 GMT

Hi everyone,

Thank you for your patience while we worked through your feedback on the new transition experience within Jira. We've heard your concerns, and we want to share a new toggle that allows you to switch experiences.

You can choose your screen

We have now rolled out this experience. From now on you'll be able to switch between the new modernised transition screen and the old classic screen. If you'd prefer the classic screen for now, it's available to you again!

There's no deadline here and nothing you have to do.

The toggle stays available in both directions.

Switching to the new experience sticks, so if you're happy there you don't need to do anything again.
Switching to the old classic screen lasts 8 weeks, and then you'll move back to the new experience automatically.
If you'd rather stay on classic, just switch again for another 8 weeks. You can do that as often as you need, so you're never locked out and nothing gets removed from under you.
If you're on the old classic screen, we'll occasionally offer a one-click switch to the new experience. It's easy to dismiss, and the toggle is always there if you'd rather do it in your own time.

One place for updates

From now on, this thread is the home for updates on the transition screen as we work through ongoing bugs or feature requests. Follow us here to keep up with updates.

On this new thread we plan to release a feature roadmap that shows when we plan to address the issues you've raised. You can see what we're prioritising and where each item sits.

Tracking Feedback

Thanks again for sticking with us and sharing your feedback. It's shaping what we build next. Drop any questions in the thread and we'll pick them up there or use the feedback button located in the new experience.

Thank you!

Christine Kong

Associate Product Manger, Jira Work Items

Something went wrong on our end

Kamalakkannan Kalichetty — Fri, 11 Sep 2026 12:31:46 GMT

Something went wrong on our end

If this keeps happening, share this information with your admin, who should contact support.

Hash 6IWB89 Trace f28e28d3316246caa6f3b3402bf5c3ea

Feel Good Friday - Moving Day!

Amanda Barber — Fri, 11 Sep 2026 12:17:36 GMT

Happy Feel Good Friday, Atlassian Community!

The forums are about to go into read-only mode for a bit as they migrate to a new home. Learn more here: https://community.atlassian.com/forums/Community-Announcements-articles/Beep-beep-The-forums-platform-is-moving/ba-p/3283286#M7414

Setting up customers in your Jira project to work alongside them

Priscilla Hancock — Fri, 11 Sep 2026 12:14:05 GMT

Hello All

I'm currently working with a client where they have agreed to do some testing for us off the back of development work, however what would be the best way to set up the guest user within our project where they only get to see the tickets assigned to them.

The issue I have is that you have to invite the guest to a whole project (we're working off a company managed project) and we have all our tickets in one project. So giving them access to this one project will allow them to see all tickets being worked on, including other customers. Which if what we don't want to do.

Has anyone been able to find a work around with this, without having to build out a customer service board (as we already have a main one)?

Thank you

Потерен доступ к проекту jira

Дмитрий Пяркиев — Fri, 11 Sep 2026 12:00:50 GMT

В 2023 году на базе обучения был создан проект. Сегодня вошел с систему и проекта нет. пишет что системная ошибка и данные не найдены. что делать в данной ситуации? кто сталкивался с данной проблемой и как вернуть доступ? или же его безвозвратно удалили?

Has anyone experienced Loom recaps containing content from a completely unrelated meeting?

Mike Maurer — Fri, 11 Sep 2026 11:05:32 GMT

We had a case where the meeting transcript is correct, but the Loom AI recap contains completely unrelated topics, names, and action items that were never discussed in the meeting.

Even more concerning: the names and content in the recap are not related to our company at all.

This raises a serious question about where this content came from, and whether content from our meetings could potentially appear in someone else’s recap.

I already have a high-priority Atlassian support ticket open, but have not received any feedback yet.

Has anyone experienced something similar with Loom AI for Meetings?

Trello Paid Plans – Automation and AI Capabilities

saber kliti — Fri, 11 Sep 2026 10:00:22 GMT

Hello Trello Support Team,

I am currently evaluating Trello for managing our maintenance operations and would like to understand which paid plan would best fit our needs.

Our objective is to implement a more advanced workflow for managing both corrective and preventive maintenance tasks, including:

Managing a preventive maintenance schedule based on equipment, maintenance frequency and due dates.
Automatically creating preventive maintenance cards according to the planned frequency and equipment schedule.
Automatically managing and updating preventive tasks based on their status and deadlines.
Managing corrective maintenance requests coming from clubs, technicians, management and maintenance audits.
Automatically moving cards between lists according to their status.
Taking into account technician workload, active tasks, priorities, clubs/sites and intervention deadlines.
Preparing a D-1 intervention plan and automatically prioritizing or assigning tasks to technicians for the following day.
Using AI or intelligent agents to assist with task prioritization, assignment and workflow management.
Integrating Trello with external planning tools such as Excel, Google Sheets, Power Automate or Outlook.
Using API, webhooks or other capabilities to develop a more intelligent and customized maintenance workflow.

Could you please advise us on:

Which paid Trello plan (Standard, Premium or Enterprise) would be the most appropriate for these requirements?
What advanced automation and AI capabilities are available with each plan?
Whether Trello currently offers AI agents or intelligent automation capable of considering technician workload, priorities, existing active cards and preventive maintenance deadlines when assigning or moving tasks.
Whether preventive maintenance schedules can be automated based on equipment and maintenance frequency.
Whether Power Automate, API or webhooks can be used to build this type of workflow.
If there are additional costs, limitations or integrations required for these advanced features.

We are considering migrating to a paid Trello plan and would appreciate your recommendation based on these requirements.

Best regards,

Saber Kliti

Maintenance Manager

Tél : +216 28 794 562

E-mail : maintenance@california-gym.com

Someone asks for your entire JSM Assets CMDB in a file. Where is the export button?

Abaho Katabarwa _Katabarwa Labs_ — Fri, 11 Sep 2026 10:00:00 GMT

A migration lead wants the current state, an auditor wants evidence, or you want a backup before a big change. You go looking for the export-this-schema button in Jira Service Management Assets and there is no one-click export of a whole object schema.

It is one of the longest-standing asks on the JSM tracker: JSDCLOUD-9967 ("Ability to export Assets data from Object Schema") has over 580 votes and is still open. You can build the export yourself, but it is a real script you then own: find the workspace id, AQL-page every object, resolve each attribute id to its name and flatten to display values, honor Assets rate limits (429s and Retry-After), and escape CSV against formula injection.

Disclosure: I work for Katabarwa Labs, and we build an app for exactly this, so treat it as one option among whatever you evaluate.

Assets Export Manager does that whole flow as a single action. You pick an Assets object schema, choose CSV (one row per object, audit-ready) or JSON (full-fidelity and re-import-friendly), and it AQL-pages every object, flattens each object's attributes to display values, and streams the finished file to your browser. Each export carries a manifest: schema, object count, per-object-type breakdown, timestamp, and a truncation flag, so you know exactly what you got. It runs entirely on Atlassian Forge inside your own tenant, so nothing leaves your instance, and it reads only the schemas you grant it on each schema's Roles tab.

Listing, if it helps: Assets Export Manager for Jira Service Management. If your export workflow needs a shape this does not cover, tell us and we will build it.

Slack Assist app errored but no alerts to admins

Myles Boyd — Fri, 11 Sep 2026 09:17:52 GMT

We experience an issue following the latest Atlassian chat updates, that changed the permissions structure.

We had limited who could raise the default request type and it worked for ages with Assist.

We have Assist installed on our Slack support channel

But post the change it broke. Unfortunately, in our support channel everything looked to be working.

However, the users (who pay no attention to the Assist app!) got this in the private DM from the Assist app

Strangely enough it says it alerted the agents, but I can find no evidence of that (I am also one of the agents)

Is anyone aware of away to monitor and alert on this?

Unable to change text style in a Live Doc

Melanie York — Fri, 11 Sep 2026 08:59:35 GMT

Whenever I click to change the style of a block of text (i.e. Heading 1 to Heading 2), no options show up when I click it. The 'T' icon turns blue so it's recognizing that I'm clicking on it for more options, but the dropdown menu with the style options does not appear.

I was able to do this previously, so I'm not sure why I'm having issues now. It's the case for all my Live Docs, not a specific one. I've tried logging in and out, but still no luck.

Any advice?

Edit: Never mind -- it's working now for some reason. I didn't do anything; it's just suddenly fine. Unsure how this happened but I'm happy about it, ha

Git push hang/freeze in Windows - with solution

Michael Haben — Fri, 11 Sep 2026 08:27:20 GMT

For the last few days I've been seeing a problem on my Windows 10 PC where "git push origin main" (pushing to a BitBucket-hosted repo) in Git-Bash would hang:

$ git push
Enumerating objects: 134, done.
Counting objects: 100% (116/116), done.
Delta compression using up to 8 threads
Compressing objects: 100% (48/48), done.
Writing objects: 100% (101/101), 111.82 KiB | 27.95 MiB/s, done.
Total 101 (delta 65), reused 82 (delta 52), pack-reused 0

Adding verbosity options "GIT_TRACE=1 GIT_CURL_VERBOSE=1 git push" showed more:

...
Enumerating objects: 134, done.
Counting objects: 100% (116/116), done.
Delta compression using up to 8 threads
Compressing objects: 100% (48/48), done.
Writing objects: 100% (101/101), 111.82 KiB | 37.27 MiB/s, done.
Total 101 (delta 65), reused 82 (delta 52), pack-reused 0
14:59:37.459035 http.c:843 == Info: Found bundle for host: 0x20854357e30 [can multiplex]
14:59:37.459035 http.c:843 == Info: Re-using existing connection #0 with host bitbucket.org
14:59:37.459035 http.c:843 == Info: Server auth using Basic with user 'mike_h3'
14:59:37.459035 http.c:843 == Info: h2 [:method: POST]
14:59:37.459035 http.c:843 == Info: h2 [:scheme: https]
14:59:37.459035 http.c:843 == Info: h2 [:authority: bitbucket.org]
14:59:37.459035 http.c:843 == Info: h2 [:path: /h3-structuraltech/pc_test_app.git/git-receive-pack]
14:59:37.459035 http.c:843 == Info: h2 [authorization: Basic <redacted>]
14:59:37.459035 http.c:843 == Info: h2 [user-agent: git/2.41.0.windows.3]
14:59:37.459035 http.c:843 == Info: h2 [accept-encoding: deflate, gzip, br, zstd]
14:59:37.459035 http.c:843 == Info: h2 [content-type: application/x-git-receive-pack-request]
14:59:37.459035 http.c:843 == Info: h2 [accept: application/x-git-receive-pack-result]
14:59:37.459035 http.c:843 == Info: h2 [content-length: 114684]
14:59:37.459035 http.c:843 == Info: Using Stream ID: 7 (easy handle 0x20854366320)
14:59:37.459035 http.c:790 => Send header, 0000000532 bytes (0x00000214)
14:59:37.459035 http.c:802 => Send header: POST /h3-structuraltech/pc_test_app.git/git-receive-pack HTTP/2
14:59:37.459035 http.c:802 => Send header: Host: bitbucket.org
14:59:37.459035 http.c:802 => Send header: Authorization: Basic <redacted>
14:59:37.459035 http.c:802 => Send header: User-Agent: git/2.41.0.windows.3
14:59:37.459035 http.c:802 => Send header: Accept-Encoding: deflate, gzip, br, zstd
14:59:37.459035 http.c:802 => Send header: Content-Type: application/x-git-receive-pack-request
14:59:37.459035 http.c:802 => Send header: Accept: application/x-git-receive-pack-result
14:59:37.459035 http.c:802 => Send header: Content-Length: 114684
14:59:37.459035 http.c:802 => Send header:
14:59:37.519034 http.c:843 == Info: We are completely uploaded and fine

I tried a "git bundle create", then cloning from that Git-bundle, adding the same remote repo to the new cloned repo and pushing, but saw exactly the same behaviour.

TLDR is... files that were initially included in a commit, but later excluded via the .gitignore file were still present, and deleting them fixed the issue.

Shortly before the problem showed itself, I'd added an entire new Visual Studio project to my repo: "git add MyNewProj/", which had of course added not just the project file and source-code files, but build-artefact files in folders MyNewProj/bin and MyNewProj/obj. I'd then edited my .gitignore file to make Git ignore these two sub-folders, but hadn't deleted them (or "git rm"'d them) from the filesystem. I have TortoiseGit installed, and both of these folders were still being shown by Windows Explorer with TortoiseGit's green overlay-icon. I'm pretty sure these two subfolders + contents had also been included by the "git bundle create" and were then present when I "git clone"'d a new copy of the repo from that bundle. I Shift-Deleted MyNewProj/bin and MyNewProj/obj in Windows Explorer, then went back to Git-Bash and did "git push" - and it worked as normal.

Versions: git version 2.41.0.windows.3, TortoiseGit 2.14.0.0 (Hotfix 2.14.0.1).

I'm not sure whether this is a problem inherent in Git, or specific to BitBucket. I'll try to find time to reproduce the issue in a "demo" repo that doesn't contain customer code, but don't wait up for that.

Feature Focus 2026 Vol. 11 (September)

Suzie Ahlers — Fri, 11 Sep 2026 08:15:55 GMT

*Special Note: Due to the move of the Atlassian Community forums to a new platform currently planned for September 22, the forums will be in read-only mode for at least 10 days starting today. The Feature Focus will recommence once content publishing resumes on the new platform.

State of AI SDLC is a single-day digital summit for technical leaders responsible for planning, building, and running software in the AI era. Hear directly from Atlassian CEO and Co-Founder Mike Cannon-Brookes, Atlassian Chief Product & AI Officer Tamar Yehoshua, and industry leaders at DX, Lovable, and more as they reveal how AI is transforming the modern software development lifecycle. Related to this, we’re bringing governed agent loops to the AI-Native SDLC.

Why AI ROI Still Stumps Leaders And How Context Closes The Gap: Forbes spoke with Avani Prabhakar, Chief People Officer at Atlassian, to understand why capturing AI ROI remains a challenge and how organizational change can drive lasting, measurable impact.

Inside Atlassian

Plan your Team ’26 Europe experience in Amsterdam: Get ready for Team '26 Europe by using the Agenda Builder to create your personal schedule. Check out inspiring keynotes, breakout sessions, and live demos designed to help you craft game-changing product experiences.
You don’t need a team of AI experts. You just need one. Atlassian’s Teamwork Lab set out to find out: does it matter how many AI-skilled people are on a team? The answer was clear and surprisingly specific. The biggest jump in team performance came from adding just one AI superuser to a team that previously had none.
Introducing our connector blog series: Because connected context provides AI with more complete information and less fragmentation, it can help Rovo and external AI agents use tokens more efficiently and produce higher-quality outcomes. To explore these possibilities, we’re publishing a series of blog posts highlighting the value of individual Teamwork Graph connectors and the ways they can help teams work with more context.
- How Teamwork Graph Saves Agent Tokens YouTube | 5.5 min.
- How Teamwork Graph Helps AI Agents YouTube | <5 min.

Apps & Collections

Platform Apps

Administration

A smarter way to understand which Atlassian Cloud changes need your attention: We’re adding AI-generated impact ratings to the new Release Notes on Atlassian Community to help you quickly understand the likely significance of each release note.
Space policies give teams autonomy with admin guardrails: Space policies are now available in open beta to customers across Jira, JSM, and JPD. Space policies let teams create and manage team-managed spaces within guardrails you define once.
An improved audit log experience for Jira and JSM: With this release, eligible admins will see a more consistent audit log experience directly in Jira and JSM, with expanded coverage for product activity.
Teamwork Graph (TWG) connectors now have a top-level home in Atlassian Administration: From Atlassian Administration → Connectors, admins can start setup, review connector-specific details and settings, reauthorize connections when needed, monitor connector health, and disconnect apps when appropriate.
Share your experience with managing Atlassian licenses: We’re looking to speak with administrators to learn about your current license management workflows, including challenges, manual steps, or issues you encounter along the way. Sign up here. 60 min. | $100 digital gift card | Feedback Opportunity

Atlassian Teams

New Features: Custom Field, Rovo Skills, JQL improvements and more! We’re excited to share a bunch of new features and Rovo skills designed to make Atlassian Teams even more powerful and easy to use. From smarter automation in Jira to AI-powered cleanup, here’s what’s new.

Goals & Projects

Now available: restricted goals, plus an upgrade for projects: We're rolling out restricted goals to limit an individual goal or project to specific people, so sensitive work gets tracked properly without being visible to everyone. Restricted goals and projects use the same Can view and Can edit permission levels you already know.
More accurate metrics: You can now record a value as of the date it was true rather than the day you entered it, remove values you don't want, see who added what, and have your goal's progress automatically update.
🎯 Stop Drowning in Spreadsheets: How to Actually Track Goals & OKRs in Jira: You don’t need a mountain of spreadsheets or a maze of projects to keep your team aligned. You can track your goal progress in a simple, lightweight way directly within Jira.

Teamwork Collection

Confluence

🚀 Confluence Slides is here: Simply describe what presentation you want, and Rovo pulls context from across Atlassian and connected third-party apps to create impactful, visual presentations. Then, share your slides directly in Confluence without having to switch between different apps.
- Your next presentation is already in Confluence
How to Create Accessible Articles in Confluence Cloud: Accessible documentation helps people with permanent, temporary, and situational disabilities, as well as readers who are multitasking, using mobile devices, reading in a second language, working in bright or noisy environments, or relying on keyboard navigation. This guide includes practical steps for structuring, writing, formatting, and reviewing Confluence articles so they are easier to access with assistive technology and easier for all readers to understand.
The Confluence/Rovo Cheat Sheet You Didn't Know You Needed: Here are some of the most common, actually-useful ways people use Rovo in Confluence day to day.
Offline Mode for Confluence Mobile: Offline mode lets you save content ahead of time and read it later without Wi‑Fi or cellular service. We will continue to improve on this functionality, so add comments to share feedback and help steer the future of this feature.

Jira

Stop exporting your work to figure it out. Jira now does it for you. We just shipped a batch of updates to Jira that we're really excited about, especially if your team has been managing capacity, budgets, or reporting outside of Jira. Explore formula fields, custom dashboards and work items types, business team templates, and more.
- Individual capacity planning Premium/Enterprise
Create Jira work items right from Trello: Now you can use a Trello card to create a new Jira work item without switching tools or starting from scratch. If you used the Jira Power-Up before it was retired, this is the new native functionality.
Turn any Microsoft Teams conversation into Jira work with natural language: The Jira Cloud for Microsoft Teams app now understands natural language. Your team can create, update, and assign work to teammates or AI coding agents without leaving the chat.
- Using @jira in Microsoft Teams to create, update and assign work from chat YouTube | 1.5 min.
Bulk Fetch Gets a 10× Boost: We've raised the ceiling on the Jira Cloud POST/rest/api/{version}/issue/bulkfetch endpoint. Where a request could previously return 100 issues, eligible requests can now return up to 1,000 issues.
Multiple field contexts per space is coming to Jira: We’re getting ready to introduce support for multiple field contexts per space, and we’re looking for customers to help us test it through an Early Access Program. Participants will test this on their sandbox site (only), and new field schemes must be enabled on the site. Sign up here. EAP
Introducing Jira Planner: now in early access: Jira Planner is particularly useful for tech leads, senior engineers, engineering managers, and PMs working on architectural decisions, multi sprint features, or any work where the team needs to agree on scope before implementation begins. You will need Rovo enabled, Teamwork Graph connected, and Confluence available on the same site. Join the waitlist. EAP

Loom

Loom Migration Guide: Transitioning to Atlassian Workspaces Safely and Seamlessly: This guide will help you use the self-serve path to move from a Legacy Loom workspace or to consolidate across Atlassian sites, while keeping your content safe and your workflow uninterrupted.

Rovo/AI

What’s new and what’s next to securely scale Rovo: Our goal is simple: help you unlock AI’s value while keeping the controls, visibility, and safeguards your organization needs.
Introducing Studio Templates: You can browse a curated gallery of ready-made agent and automation templates, customize them in seconds with guided setup, and activate them directly from Rovo Studio.
Rovo Agent Reasoning: choose how your agents think: Agent Reasoning gives you a practical way to match your agent’s effort to the work in front of it, meaning you can keep everyday agents fast and focused, while giving more demanding work the extra reasoning capacity it needs. It’s control over both the depth of the work and the model powering it.
Rovo Skills are available in Rovo Agents! Rovo Skills are now available for all customers building custom agents in Rovo Studio. You can now add Skills directly to your agents, giving them access to the same reusable, opinionated workflows that already power Rovo Chat. Open Beta
- Turn Rovo into a practical teammate with skills: In our first public session on Rovo Platform Skills, we recreated a release-readiness scenario and show how platform skills can turn scattered work context into a researched next step.
- Did you know there are 40+ Rovo Platform Skills ready to make your workday more efficient? Community Champion
Why is my Rovo Agent saying that? Let's Debug Smarter. You built your Rovo Agent, tested a few prompts, and something feels off. Try these tips to improve your Rovo responses.
Create with Rovo for Automation: We know that getting started is often the hardest part of building an automation. Instead of building a flow component by component, simply tell Rovo what you’re trying to do in natural language.
- From blank page to better work with Rovo: During the Generate and improve content with Rovo session, we explored practical ways to use Rovo to get started faster, improve work you have already drafted, and uncover useful information across Jira, Confluence, and connected tools. Find the recap and links here!
Rovo app for Microsoft Teams is now live! 🎉 Mention @rovo in a channel, a group chat, or chat with it one to one, and it answers using the full context of your work: Jira, Confluence, SharePoint, Google Drive, and the other tools you've connected to Rovo.
New research shows AI polish makes it harder to spot problems. But there’s a quick fix. Adding an “Early Draft” label on an AI-polished doc increases your chances of receiving better feedback on your work, according to a recent Atlassian Teamwork Lab study revealing an “AI polish effect.”

Service Collection

Assets

Display Names Update for Assets and What It Means for Your CMDB: We've introduced Display Names for all Assets configuration entities: schemas, object types, attributes, statuses, and reference types. Every entity now has two identifiers.
From Chaos to Control with Assets: In this upcoming webinar we’ll share how Assets can help teams build a more reliable view of the things they run, own, and support. We’ll explore how a unified data foundation, hardware lifecycle management, and a more intuitive data-management experience can help IT teams move from reconciling records to acting on trusted context. Register here. September 16 | 11 AM AEST/CEST/PDT
Common Data Model and Hardware Asset Management (HAM) GA in JSM: The CDM gives teams a standardized, out-of-the-box foundation for cleaner, more consistent asset data across your Atlassian stack. The new Hardware Asset Management console (Premium/Enterprise), connects hardware schemas, workflows, reporting, and lifecycle processes to a shared data model built for scale.
What's New in Assets Data Manager: This September 2026 release brings a significant set of improvements to the new admin journey, and a new wave of capability additions covering Lansweeper, bulk operations, saved search, default attribute mapping, and a new cloud-enabled data source → for flat files. Premium/Enterprise
AI-Powered capabilities in HAM: Asset managers can now see proactive risks like expiring warranties and dormant devices, query inventory in plain English, and configure HAM rules in just a few clicks. Premium/Enterprise

Jira Service Management

🎉 Case Management in JSM is now GA: Case Management gives HR and Legal teams a native, structured and secure way to handle sensitive cases directly inside JSM. Whether you're managing an employee misconduct investigation, a legal matter, a grievance or a complex employee case, Case Management offers purpose-built structure, granular access controls, and case note capabilities.
Help us shape JSM Headless: We’re looking for feedback on JSM Headless, a new way for agents to work on JSM requests from Slack, Teams, Rovo, Claude and other tools without opening the web portal. Sign up here. EAP, Feedback Opportunity
Sign-up for the new JSM AI Control Center: If your team is turning on AI across JSM and needs a single place to see it, control it, and prove its value, this one's for you. EAP, Premium/Enterprise

Software Collection

Bitbucket

Monitor test health at a glance in Bitbucket: See a quick health summary for a test suite; use the Needs attention card to spot tests with high flakiness scores; open an individual test to review its execution history, failure details, and trends over time; and move from a Pipelines build to the related test details with the View in Tests action.
Bitbucket Repository Attributes Now Use Workspace-Scoped Search in Assets: This change affects commercial JSM Assets Cloud customers who use Bitbucket Repository attributes in their Assets schemas. Bitbucket Repository attributes will search only the Bitbucket workspaces configured for that attribute. This update helps Assets continue to work with Bitbucket Cloud’s current API model and gives admins more control over which workspaces are available for each attribute.
Help shape the future of AI Safety Net in Bitbucket: We’re exploring how software teams use AI across the software lifecycle, and how they build trust, governance, and safety as AI becomes more autonomous. We’re opening a research study so you can share your experience and help shape the design of AI safety and governance features in Bitbucket. 15 min. | $20 digital gift card | Feedback Opportunity
Bitbucket multi-region architecture and EU data residency coming soon: These changes will help us meet GDPR and regional data sovereignty requirements. Data Center customers can migrate to the cloud with confidence, knowing their data is hosted in their region of choice.

Strategy Collection (Premium/Enterprise)

Goals and Projects capabilities in Strategy Collection: Starting in August 2026, some new capabilities in Goals and Projects will require a Strategy Collection license. Currently, these include the following capabilities:

Manage app permissions at the group level: Centrally control user permissions across Goals and Projects using groups, simplifying governance and permission management at scale.
- Manage Goals app group permissions
- Manage Projects app group permissions
Adding and editing metric period targets: Set targets by months or quarters for metrics on goal success measures.

Focus

Prepare your Focus area updates with Drafts! You can now jot down notes throughout the week to keep track of what’s happened; prepare your updates in advance; and allow for multiple contributors to draft the update together.

Jira Align

You're Invited: September Jira Align Customer Forum: Our monthly Jira Align Customer Forum is returning! Starting this month, we’ll host one session per forum and alternate the meeting time between AMER/EMEA and APAC-friendly hours every month so more customers can join at a convenient time. This month’s forum will include a Team Amsterdam preview; Jira Align roadmap updates; and a live discussion with product. Register here. September 24 | 8 AM PDT/11 AM EDT

Additional Updates

Community and Learning

How We Gamified Jira, JSM, Confluence & Bitbucket to Drive Adoption: Rather than write "here's how Confluence search works" as a wiki page, we built it as a Confluence Ninja Quest: a self-guided challenge where completing each step actually requires using the feature, not just reading about it. Community Champion
Interview With an Expert: How Chris Rainey Found His Place in the Atlassian Community: This article is part of an ongoing series that features real-world Atlassian professionals and their helpful insights. This particular article is a departure from its predecessors because in this case, the expertise Chris had to share wasn’t solely about using the Atlassian Service Collection, it was also about the importance of embracing the Atlassian Community. Community Champion
Upcoming changes to the Jira Cloud Administration exams: As part of the ongoing effort to keep Atlassian credentials current and valuable, the Managing Jira Projects for Cloud (ACP-620) and Jira Administration for Cloud (ACP-120) exams will be merged into a single exam in January 2027.

Data Center

Secure Tunnels now built into DC–Cloud setup: Last year we introduced OAuth 2.0 and Cloud Connectors and today we’re excited to share the next step. If your Data Center instance sits behind a firewall, connecting it to Cloud just became dramatically simpler.
Application Links via Cloud Connector for Jira and Confluence Cloud: You can now set up Jira Cloud and Confluence Cloud application links to Data Center via Cloud Connector, with OAuth 2.0 handled automatically and no manual credential copying.
Moving from Data Center to Cloud? Don't let silos slow you down. 🛑 In a self-managed environment, silos often feel like a natural byproduct of infrastructure. But in Cloud, those same silos can become invisible blockers that prevent you from leveraging the full power of AI and analytics. Join the live session Unlocking Momentum: Leadership Strategies for Cloud Transformation to help you bridge that gap. Register here. September 16 | 11-11:30 AM EDT

Trust & Security

A practical IAM reference architecture for Atlassian Cloud: Identity and access management is the foundation of a secure cloud environment. To help customers navigate this landscape, Atlassian has published a new white paper, IAM reference architecture for Atlassian Cloud in the Atlassian Trust Center.
Vulnerability Management at Atlassian: We've published the second one-pager in our Trust series: a concise, exec-ready overview of how Atlassian finds, prioritizes, and fixes security vulnerabilities across 29,000+ repositories and every layer of our cloud infrastructure.

Events

See the full Class Calendar of upcoming live sessions
6-8 October 2026 | Register today for Team '26 Europe!
October 27-28, 2026 | Build IT Together (BIT) Conference | Dallas, Texas: This is a FREE Conference with two days of sessions and activities to make you a better a Jira admin! Each presentation will show you real use cases for how to leverage the power of Forge, Rovo, or AI. Atlassians will be on site with Forge and Rovo workshops to expand your skills, and there will be stations for you to take Atlassian Certified exams.
More upcoming ACE Events in List and Calendar views