<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Mihai Perdum</title>
    <description>The latest articles on DEV Community by Mihai Perdum (@mihai_leanzero).</description>
    <link>https://dev.to/mihai_leanzero</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4130453%2Fdb62e2a0-c593-4f6c-a75e-49ca13efbeb5.jpeg</url>
      <title>DEV Community: Mihai Perdum</title>
      <link>https://dev.to/mihai_leanzero</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/mihai_leanzero"/>
    <language>en</language>
    <item>
      <title>Forge app not loading with a Jira IP allowlist: what to allow</title>
      <dc:creator>Mihai Perdum</dc:creator>
      <pubDate>Tue, 17 Nov 2026 09:00:34 +0000</pubDate>
      <link>https://dev.to/mihai_leanzero/forge-app-not-loading-with-a-jira-ip-allowlist-what-to-allow-261n</link>
      <guid>https://dev.to/mihai_leanzero/forge-app-not-loading-with-a-jira-ip-allowlist-what-to-allow-261n</guid>
      <description>&lt;p&gt;On 23 June 2022 someone asked the Atlassian developer community why a Forge app wasn't loading on a Jira site with an IP allowlist, and which addresses to add. Atlassian staff answered the same day: "That's a known limitation at the moment and there isn't an option to add the IPs to an allow list." That thread, "&lt;a href="https://community.developer.atlassian.com/t/forge-app-not-loading-when-ip-allowlists-enabled/59337" rel="noopener noreferrer"&gt;Forge app not loading when IP allowlists enabled&lt;/a&gt;", has 898 views. Nobody has posted in it since, and it was still the first result when we searched "forge app not loading ip allowlist" on 17 November 2026.&lt;/p&gt;

&lt;p&gt;It was true then. It stopped being true on 26 June 2024, when Atlassian shipped "Forge support for IP allowlisting". Atlassian closed the last bug ticket about it on 13 December 2024. So if a Marketplace app is blank for your users today, an old answer may be sending you to the wrong place. The newer reports point at your own network, and the thing to allow there is the domain &lt;code&gt;*.atlassian-dev.net&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;The app can be blocked by two different lists. (Forge is Atlassian's platform for Marketplace and custom apps, and it runs them on Atlassian's own infrastructure. An IP allowlist is a list of network addresses that are allowed in, with everyone else refused.) One is the IP allowlist an organization admin sets in Atlassian Administration, and the other is your company network's own list of allowed domains and addresses, in a firewall or web filter.&lt;/p&gt;

&lt;p&gt;I'd look at the network first. The newest reports I found, from October and November 2025, are about one address that company firewalls and web filters block: &lt;code&gt;*.cdn.prod.atlassian-dev.net&lt;/code&gt;. Atlassian's domain list covers it with the row &lt;code&gt;*.atlassian-dev.net&lt;/code&gt;. That's probably also why an app is blank for some people and fine for others. The people on the office network or the company VPN go through the filter, and the people at home don't.&lt;/p&gt;

&lt;h2&gt;
  
  
  Four things we found
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Atlassian's support page now says it doesn't apply IP allowlist restrictions to "Forge apps with 2LO and 3LO" (two kinds of app calls, explained further down).&lt;/li&gt;
&lt;li&gt;On 17 November 2026 we activated an allowlist on our own test site. A Forge app kept loading with no Forge address in the list.&lt;/li&gt;
&lt;li&gt;The allowlist wizard has 3 steps and no setting for Forge apps, Connect apps (Connect is Atlassian's older app framework) or Marketplace apps.&lt;/li&gt;
&lt;li&gt;The old workaround is still printed on Atlassian's closed bug ticket. The 8 addresses listed there aren't in Atlassian's address file any more.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Which allowlist is blocking the Forge app: Atlassian's IP allowlist or your network
&lt;/h2&gt;

&lt;p&gt;These two get mixed up all the time, and I get why. They're both called allowlists. They both make an app "not load".&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;&lt;/th&gt;
&lt;th&gt;Atlassian's IP allowlist&lt;/th&gt;
&lt;th&gt;Your network's allowlist&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Who sets it&lt;/td&gt;
&lt;td&gt;An organization admin&lt;/td&gt;
&lt;td&gt;Your network or security team&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Where&lt;/td&gt;
&lt;td&gt;Atlassian Administration, under &lt;strong&gt;Security&lt;/strong&gt;, &lt;strong&gt;Device security&lt;/strong&gt;, &lt;strong&gt;IP allowlists&lt;/strong&gt;
&lt;/td&gt;
&lt;td&gt;The company firewall, proxy or web filter&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;What it checks&lt;/td&gt;
&lt;td&gt;The address a person or script comes from when they open Jira, Jira Service Management or Confluence&lt;/td&gt;
&lt;td&gt;Which domains and addresses your people's browsers may reach&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Needs&lt;/td&gt;
&lt;td&gt;A Premium or Enterprise plan on Atlassian Cloud&lt;/td&gt;
&lt;td&gt;Nothing from Atlassian&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;What a blocked person sees&lt;/td&gt;
&lt;td&gt;Per Atlassian's knowledge base: "There was a problem accessing this content" for the site&lt;/td&gt;
&lt;td&gt;Jira opens, and the app's panel is empty or shows a browser error&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Atlassian describes its own in "&lt;a href="https://support.atlassian.com/security-and-access-policies/docs/specify-ip-addresses-for-product-access/" rel="noopener noreferrer"&gt;Specify IP addresses for app access&lt;/a&gt;". (Atlassian now calls Jira and Confluence "apps" too. In this article "app" means a Marketplace or custom app.) You can enter up to 500 addresses for a given product across your active policies. They can be single addresses, countries, or ranges in CIDR notation. (CIDR writes a whole block of addresses as one address plus a slash and a number, like 131.162.88.0/21.)&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fykmq5scrpssofymbdyuw.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fykmq5scrpssofymbdyuw.png" title="Our test allowlist while it was Active. Look at the Applies to column: this one targets Jira on one site. Where Atlassian writes apps here it means its own products. Nothing on this screen or in the wizard is a setting for Forge, Connect or Marketplace apps." alt="Atlassian Administration IP allowlists page on our test organization on 17 November 2026: the line Powered by Atlassian Guard, one allowlist row with Access origin IP address, the Jira icon under Applies to and a green Active status" width="800" height="556"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  "There was a problem accessing this content": what a person outside the IP allowlist sees
&lt;/h3&gt;

&lt;p&gt;Atlassian's allowlist decides whether a person gets into the site at all. Atlassian has a &lt;a href="https://support.atlassian.com/confluence/kb/there-was-a-problem-accessing-this-content-error-message-atlassian-cloud/" rel="noopener noreferrer"&gt;knowledge base article on the error&lt;/a&gt;, updated on 21 August 2026. A user coming from an address outside the list sees "There was a problem accessing this content". Under it: "Check your network connection and try again, or contact your administrator for help." We didn't see that screen ourselves, because our own address was on our list.&lt;/p&gt;

&lt;p&gt;So if Jira opens fine for someone and only the app's panel is empty, Atlassian's allowlist has already let that person in. That's my reading of the two pages, and it has two exceptions. In 2022 Jira opened and the allowlist still broke the app, which is the bug that's now closed. And an app with its own remote backend may still be affected (the Forge Remote section near the end has what's known).&lt;/p&gt;

&lt;h2&gt;
  
  
  *.cdn.prod.atlassian-dev.net blocked on the network: the domain Forge apps load from
&lt;/h2&gt;

&lt;p&gt;The newest reports I found of a blank app all name one domain. On 24 October 2025 David Benson from draw.io opened a thread called "&lt;a href="https://community.developer.atlassian.com/t/cdn-prod-atlassian-dev-net-domain-network-blocks/96394" rel="noopener noreferrer"&gt;*.cdn.prod.atlassian-dev.net domain network blocks&lt;/a&gt;". His words: "We're seeing widespread problems amongst larger users not knowing that *.cdn.prod.atlassian-dev.net is required to allow forge apps to run." The "cdn" in that name stands for content delivery network (CDN), the set of servers that hands an app's screens to your browser.&lt;/p&gt;

&lt;p&gt;Sean Bourke from Atlassian answered on 25 November 2025. Some customers, he wrote, "may have applied it before this was required, or have missed this", and the requirement "isn't well communicated in our Connect to Forge and Forge documentation". That thread has 670 views, and I think it deserves more.&lt;/p&gt;

&lt;p&gt;This comes up now because so many apps moved from Connect to Forge. An app that used to load from its vendor's own servers now loads from Atlassian's. Our article "&lt;a href="https://dev.to/blog/connect-end-of-support-app-might-stop-working"&gt;This app might stop working soon&lt;/a&gt;" covers that move. A network rule that allowed the vendor's domain doesn't help any more. Nobody told the firewall.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fglo6q9sotmb9tnx4hpnt.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fglo6q9sotmb9tnx4hpnt.png" title="Illustration, generated locally with ERNIE-Image. An app that moved from Connect to Forge now loads from Atlassian's own domain, so the network rule that allowed the vendor's domain no longer covers it. The guard's list is perfectly accurate about a house that is no longer the delivery address." alt="A brick-walled red robot gatekeeper at a locked turnstile checks two clipboards while a violet rocket-shaped app carrying a star-marked parcel is stopped by a striped barrier, and behind the gate an open doorway with green arrows leads to a little house with a flag." width="800" height="448"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;You can sometimes spot it on screen. Tempo's &lt;a href="https://help.tempo.io/kb/latest/the-forge-ui-iframe-analytics-might-be-temporarily-down-or-it-may-have-moved-permanently-to-a-new-web-address" rel="noopener noreferrer"&gt;help article&lt;/a&gt; shows the browser's own error inside the app's panel: the page "might be temporarily down or it may have moved permanently to a new web address", for a host name ending in &lt;code&gt;cdn.prod.atlassian-dev.net&lt;/code&gt;. It puts the cause on "OpenDNS, Zscaler, Cisco Umbrella, or another filter". Vendors are still writing these pages. Asset Management for Jira updated its own on 3 November 2026.&lt;/p&gt;

&lt;p&gt;What should your network team allow? Atlassian's page "&lt;a href="https://support.atlassian.com/organization-administration/docs/ip-addresses-and-domains-for-atlassian-cloud-products/" rel="noopener noreferrer"&gt;IP addresses and domains for Atlassian cloud apps&lt;/a&gt;" has a table of 9 Atlassian domain rows. Apps need these two:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;code&gt;*.atlassian-dev.net&lt;/code&gt;, described as "Marketplace and custom apps use this"&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;*.atlassian-3p.com&lt;/code&gt;, "Used to host third-party assets for Forge apps, user-generated content transforms, and sandbox development environments"&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;You won't find the exact string &lt;code&gt;cdn.prod.atlassian-dev.net&lt;/code&gt; on that page (I checked on 17 November 2026). It's covered by the wider &lt;code&gt;*.atlassian-dev.net&lt;/code&gt; row, but only if your rule allows several levels of subdomain. It's easy to miss. Atlassian's page asks for exactly that: the rule has to permit "the top-level domain and multiple levels of subdomains".&lt;/p&gt;

&lt;h2&gt;
  
  
  Checklist for admins: what to allow so the app loads
&lt;/h2&gt;

&lt;p&gt;You'll need two people for this. One is an organization admin for the Atlassian side, on Jira or Confluence Cloud with a Premium or Enterprise plan. The other manages the company firewall or web filter. When you're done, the app loads from the network where it failed.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;From the network where the app fails, open Jira or Confluence itself. If the site opens, skip to item 6. If you get "There was a problem accessing this content", the person's address is probably outside your IP allowlist.&lt;/li&gt;
&lt;li&gt;On that same network, find its public address. Your network team knows it, or any "what is my IP" page shows it.&lt;/li&gt;
&lt;li&gt;In Atlassian Administration, select your organization, then &lt;strong&gt;Security&lt;/strong&gt;, then &lt;strong&gt;Device security&lt;/strong&gt;, then &lt;strong&gt;IP allowlists&lt;/strong&gt;. The list shows each allowlist with its &lt;strong&gt;Status&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;On an &lt;strong&gt;Active&lt;/strong&gt; row, open the row menu and select &lt;strong&gt;Edit&lt;/strong&gt;. The allowlist opens for editing. (On an Active row the menu reads &lt;strong&gt;Edit&lt;/strong&gt;, &lt;strong&gt;Deactivate&lt;/strong&gt; and &lt;strong&gt;Delete&lt;/strong&gt;. We didn't open &lt;strong&gt;Edit&lt;/strong&gt; in our own test, so I can't show you that screen.)&lt;/li&gt;
&lt;li&gt;If the address from item 2 should be allowed and isn't there, add it and save. Do items 4 and 5 for every &lt;strong&gt;Active&lt;/strong&gt; row. Then open the site again from that network. If it's still refused, wait and retry before you change anything else, because we saw changes stay in progress for a long while.&lt;/li&gt;
&lt;li&gt;If the site opens and only the app's panel is empty, open &lt;code&gt;https://test.cdn.prod.atlassian-dev.net/&lt;/code&gt; in a new tab on that network. A short "Invalid URL" answer means the network can reach the app domain, so go to the vendor with the exact error text. A timeout or "this page cannot be reached" points at your network. (Asset Management for Jira's help page describes this test with its own address on the same domain. We ran it with this one on 17 November 2026 and got "Invalid URL".)&lt;/li&gt;
&lt;li&gt;Ask your network team to allow &lt;code&gt;*.atlassian-dev.net&lt;/code&gt; and &lt;code&gt;*.atlassian-3p.com&lt;/code&gt;, with all levels of subdomain, along with the rest of &lt;a href="https://support.atlassian.com/organization-administration/docs/ip-addresses-and-domains-for-atlassian-cloud-products/" rel="noopener noreferrer"&gt;Atlassian's domain table&lt;/a&gt;. The test in item 6 now answers "Invalid URL".&lt;/li&gt;
&lt;li&gt;Optional: if someone added Forge addresses to the Atlassian IP allowlist in 2023 or 2024, Forge doesn't need them there any more. Before you remove them, check that nothing else relies on them, such as Automation calling back into your own site.&lt;/li&gt;
&lt;li&gt;Reload the app from the same network. The app's panel fills in.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;If it still doesn't load, send the vendor the exact error text and tell them which of the two cases you're in. And if a Forge app is blocked for one person while Jira and the network are fine, look at app access rules, which are a different admin control. Our tutorial on &lt;a href="https://dev.to/tutorials/forge-app-access-rule-data-security-policy"&gt;the Forge app access rule&lt;/a&gt; shows what that one looks like.&lt;/p&gt;

&lt;h2&gt;
  
  
  "The IP address has been rejected because it is not on the allowed list": what the error means
&lt;/h2&gt;

&lt;p&gt;Scripts and integrations get this message. Atlassian explains it in "&lt;a href="https://support.atlassian.com/atlassian-cloud/kb/what-is-the-scope-of-ip-allowlists-in-atlassian-cloud/" rel="noopener noreferrer"&gt;Scope of IP allowlists in Atlassian Cloud&lt;/a&gt;", updated on 26 September 2025. The REST API is the set of web addresses programs use to read and change data in Jira or Confluence. Call it from outside the allowed addresses and you get this back:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight json"&gt;&lt;code&gt;&lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nl"&gt;"errorMessages"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt; &lt;span class="s2"&gt;"The IP address has been rejected because it is not on the allowed list. See your admin for more information."&lt;/span&gt; &lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nl"&gt;"errors"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;It doesn't name an HTTP status code, so I won't either.&lt;/p&gt;

&lt;p&gt;In 2022 Forge apps got this exact message. A developer &lt;a href="https://community.developer.atlassian.com/t/62283" rel="noopener noreferrer"&gt;posted it on 7 October 2022&lt;/a&gt;, spelled "allowedlist" back then, from a Forge app calling REST on a site with an allowlist. Adam Moore from Atlassian replied two days later: "Sorry, but there are no current workarounds. We are currently working on the problem and expect to have a solution by the end of the year." The first part of that fix did arrive in December 2022, and the bug has since been closed.&lt;/p&gt;

&lt;p&gt;Today you're most likely to meet the message from your own script or server. The &lt;a href="https://community.atlassian.com/forums/discussion/2176142/the-ip-address-has-been-rejected-because-it-is-not-on-the-allowedlist" rel="noopener noreferrer"&gt;Community question with this title&lt;/a&gt; has 2,230 views, and it was a company server calling Confluence's content API. That Atlassian article also says the allowlist doesn't cover admin.atlassian.com or the organization-level APIs, such as user management and user provisioning.&lt;/p&gt;

&lt;h2&gt;
  
  
  What Atlassian's IP allowlist does not apply to: Forge apps with 2LO and 3LO
&lt;/h2&gt;

&lt;p&gt;Atlassian's support page has a list of exceptions. It reads: "We also don't apply your IP allowlist restrictions to the following: Application links that use TwoLeggedOAuth, Connect applications, Forge apps with 2LO and 3LO, OAuth 2.0 (3LO) apps".&lt;/p&gt;

&lt;p&gt;OAuth is the standard an app uses to get permission to call a service such as Jira. 2LO and 3LO are short for two-legged and three-legged OAuth. The page doesn't define them and it never uses Forge's own words. My reading is that 2LO covers the calls an app makes as itself, which Forge developers write as &lt;code&gt;asApp()&lt;/code&gt;. 3LO would then cover the calls it makes on behalf of the person using it, written as &lt;code&gt;asUser()&lt;/code&gt;. The history in the next section supports that reading, because those are the two kinds of calls Atlassian fixed, one after the other.&lt;/p&gt;

&lt;p&gt;There is no switch for any of this. When we created our allowlist the wizard had three steps: name it, select targets, select the access origin. The targets on offer were Rovo, Confluence per site, "Jira Apps" per site and service accounts. Forge, Connect and Marketplace apps weren't in it anywhere. At least one Marketplace vendor now tells customers the same thing. Starware's &lt;a href="https://thestarware.atlassian.net/wiki/spaces/GWD/pages/3721658370/Using+the+App+When+Jira+IP+Allowlist+Is+Enabled" rel="noopener noreferrer"&gt;page on IP allowlists&lt;/a&gt;, dated 5 June 2026, says "there are no app IP ranges for you to add to your allowlist".&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fdfadmpfxa1ncrfjlqzz0.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fdfadmpfxa1ncrfjlqzz0.png" title="Illustration, generated locally with ERNIE-Image. The IP allowlist wizard offers Rovo, Confluence per site, Jira Apps per site and service accounts as targets, and Forge apps are not among them. The plug is fine, the panel simply has no hole for it." alt="A blue robot with a sweat drop on its head stands in front of a wall panel of differently shaped slots, holding a round star-marked plug that fits none of them, while two little rocket-shaped apps sit on the floor at its feet, one with a loose cable" width="800" height="448"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;You might not love this exemption if you're on the security side. It means an app's calls reach your site from outside your listed addresses. Someone has asked Atlassian to change that for the last item on the list, OAuth 2.0 (3LO) apps, in &lt;a href="https://jira.atlassian.com/browse/ACCESS-2439" rel="noopener noreferrer"&gt;ACCESS-2439&lt;/a&gt;, opened in September 2025. It had 1 vote when I looked.&lt;/p&gt;

&lt;h2&gt;
  
  
  Forge asApp requests fail when the IP allowlist is enabled: the bug Atlassian closed in December 2024
&lt;/h2&gt;

&lt;p&gt;Atlassian tracked this as &lt;a href="https://jira.atlassian.com/browse/ACCESS-1442" rel="noopener noreferrer"&gt;ACCESS-1442&lt;/a&gt;. It collected 44 votes and 54 watchers, and it is Closed as Fixed. The fix came in stages.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Date&lt;/th&gt;
&lt;th&gt;What happened&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;21 March 2022&lt;/td&gt;
&lt;td&gt;
&lt;a href="https://jira.atlassian.com/browse/ACCESS-1427" rel="noopener noreferrer"&gt;ACCESS-1427&lt;/a&gt; is opened: Forge apps "may not work as expected" with an allowlist on. The next day a vendor comments, "We received a 1-Star review because of this bug."&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;23 May 2022&lt;/td&gt;
&lt;td&gt;A comment on the ticket confirms that requests from an app's backend functions are blocked, and suggests sending them through the browser side of the app where possible.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;22 December 2022&lt;/td&gt;
&lt;td&gt;Atlassian's IP allowlisting team: apps invoking &lt;code&gt;api.asUser()&lt;/code&gt; "should not be impacted by IP allowlists".&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;5 February 2023&lt;/td&gt;
&lt;td&gt;ACCESS-1427 is closed and ACCESS-1442 is opened for the &lt;code&gt;asApp()&lt;/code&gt; calls that still fail.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;19 September 2023&lt;/td&gt;
&lt;td&gt;Atlassian publishes 8 Forge outgoing addresses, with the note "Per-app IP allow listing is not supported". ACCESS-1442 points to them as the workaround.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;15 March 2024&lt;/td&gt;
&lt;td&gt;The published list grows to 88 addresses.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;26 June 2024&lt;/td&gt;
&lt;td&gt;"Forge support for IP allowlisting" ships (changelog entry CHANGE-1778).&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;13 December 2024&lt;/td&gt;
&lt;td&gt;ACCESS-1442 is closed as Fixed.&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;The June 2024 entry in the &lt;a href="https://developer.atlassian.com/platform/forge/changelog/#CHANGE-1778" rel="noopener noreferrer"&gt;Forge changelog&lt;/a&gt; settles it. Forge apps on sites with IP allowlisting enabled, it says, "can now make Jira API requests and Confluence API requests by default". It adds that customers "no longer need to manually add" Atlassian's outgoing addresses to their allowlist.&lt;/p&gt;

&lt;p&gt;The old advice is still around, though, and I think it trips a lot of people up. The description on ACCESS-1442 was never updated, so it still says "Any &lt;code&gt;asApp()&lt;/code&gt; requests will be blocked" and still shows the command for collecting Forge addresses. I also read two vendor help pages that still tell admins to add Forge addresses to the allowlist. One was last edited in May 2024, a month before the change, and one in May 2025. If you followed that advice in 2023 you did the right thing for 2023. Back in February 2023, before Atlassian had published any Forge addresses, one customer on the ticket had Atlassian support raise their limit so they could enter "the 400+ IP ranges for the region we are in".&lt;/p&gt;

&lt;h2&gt;
  
  
  Our test: 19 of 19 app calls answered with an allowlist Active
&lt;/h2&gt;

&lt;p&gt;We ran this on our own test organization on 17 November 2026. The app was LeanZero Management, a planning app for Jira that my colleague Mihai builds, in its development install.&lt;/p&gt;

&lt;p&gt;Before the allowlist existed, the app's page loaded and its 6 backend calls succeeded. We then created one allowlist for Jira on that site with a single address in it (our own) and activated it.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fu0rwclf8mu1dq2jw3wdx.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fu0rwclf8mu1dq2jw3wdx.png" title="The confirmation you get before an allowlist goes live. Read the sentence in the dialog: Atlassian applies it immediately, so check the addresses first." alt="The Activate IP allowlist dialog in Atlassian Administration over the allowlist table, with the text Before you activate this IP allowlist, check the information as we apply the IP allowlist immediately, and the test row still marked Inactive behind it" width="800" height="556"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;With the status showing Active, we reloaded the app and opened a plan. The page made 19 calls to the app's backend, and all 19 succeeded. There was no error on screen. After we deleted the allowlist, 5 of 5 calls succeeded again.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F5ft04e5y0k3eiifjfbbl.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F5ft04e5y0k3eiifjfbbl.png" title="The app while the allowlist was Active, version 9.86.0 on screen. What to notice is that everything is filled in: the cards and the timeline all come from the app's backend." alt="LeanZero Management inside Jira on our test site while the IP allowlist was Active: the plan Tap to pay is open with its forecast cards and timeline bars filled in, and the product name and logo show in the blue bar" width="800" height="556"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Now the limits, because this test is smaller than it sounds. Our browser came from the one address on the list and we had no second network. So this shows the allowlist didn't break the app. It doesn't show the allowlist turning anyone away. Every time we read it in those 3 minutes 22 seconds, the data behind the admin screen (Atlassian's admin API) reported the allowlist's Jira target as "applying", while the screen itself said Active. We couldn't read the app's backend logs that day, so I don't know whether any of the 19 calls went on to Jira, as the app or as the user. At least one of them reads the app's own stored copy. And it was one app, on one page, on Jira only. So take it as one data point. Still, an active allowlist with no Forge addresses in it didn't stop a Forge app from loading, and Atlassian's changelog says it shouldn't.&lt;/p&gt;

&lt;p&gt;One small thing we noticed on the way. After we deleted the allowlist, the same admin data showed its Jira target as "removing" for more than 40 minutes while the screen already said "No IP allowlist created". So give a change a little time before you decide it didn't work.&lt;/p&gt;

&lt;h2&gt;
  
  
  Forge IP ranges: read them from ip-ranges.atlassian.com, not from a vendor page
&lt;/h2&gt;

&lt;p&gt;You don't need Forge addresses for Atlassian's IP allowlist any more. You may still need them for the opposite direction, when a Forge app calls into something behind your own firewall.&lt;/p&gt;

&lt;p&gt;Atlassian publishes its addresses as a file at &lt;a href="https://ip-ranges.atlassian.com/" rel="noopener noreferrer"&gt;ip-ranges.atlassian.com&lt;/a&gt;. The copy I read was created on 2 November 2026 and holds 175 entries. Of those, 95 are tagged for Forge and 85 of them are outgoing ranges, 29 in the older IPv4 format and 56 in IPv6. This command prints the 85:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;curl -s https://ip-ranges.atlassian.com/ &lt;span class="o"&gt;|&lt;/span&gt; jq -r &lt;span class="s1"&gt;'.items[] | select((.product|index("forge")) and (.direction|index("egress"))) | .cidr'&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Wait before anyone pastes that list into a firewall. Not one of those ranges belongs to Forge alone, and every Forge app shares them. Atlassian's note from when it first published them: "Allowing connections from this IP address range will permit connections from any Forge app." Its support page calls this traffic "untrusted and user-configurable".&lt;/p&gt;

&lt;p&gt;And the addresses move. The 8 single addresses from September 2023, which are still printed in the ACCESS-1442 description, are all absent from the file today. A list copied into a help page goes stale, so read the file. Our earlier piece on &lt;a href="https://dev.to/blog/atlassian-cloud-ip-ranges-2027"&gt;Atlassian cloud IP ranges for 2027&lt;/a&gt; walks through the newest block and how to keep a firewall list in step with the file.&lt;/p&gt;

&lt;h2&gt;
  
  
  What a Forge Remote backend still needs
&lt;/h2&gt;

&lt;p&gt;With Forge Remote, a vendor runs part of a Forge app on servers the vendor hosts. Atlassian's &lt;a href="https://developer.atlassian.com/platform/forge/remote/essentials/" rel="noopener noreferrer"&gt;Forge Remote essentials&lt;/a&gt; page, last updated on 29 October 2026, covers one direction: when Forge calls the vendor's backend, it comes from the outgoing ranges in the file above.&lt;/p&gt;

&lt;p&gt;Nobody has answered for the other direction yet, as far as I can find. On 31 August 2025 a customer commented on ACCESS-1442 that the fix "works only on Forge plateforms but not for Forge Remote". I found no Atlassian page that says how a remote backend's calls into Jira are treated by the allowlist, and we didn't test it. If your app has a remote part and fails only on sites with an allowlist, ask the vendor, and expect that they may need to ask Atlassian.&lt;/p&gt;

&lt;h2&gt;
  
  
  If you build Forge apps: say this on your support page
&lt;/h2&gt;

&lt;p&gt;Your customers' admins are reading 2022 threads. A short page that says "nothing to add to the Atlassian IP allowlist, ask your network team to allow &lt;code&gt;*.atlassian-dev.net&lt;/code&gt;" saves them a support ticket. AppLiger's page does it in one sentence and links the draw.io thread.&lt;/p&gt;

&lt;p&gt;We don't have that page for our own three apps yet either. I checked our repositories on 17 November 2026 and found no page explaining IP allowlists to customers, so that's a job for us too.&lt;/p&gt;

&lt;p&gt;Has a Forge app failed for you on a site with an allowlist since 2024, and it wasn't the network? I'd really like to see the error text. Tell me on the Atlassian Community or at &lt;a href="mailto:gabriela@leanzero.net"&gt;gabriela@leanzero.net&lt;/a&gt;.&lt;/p&gt;




&lt;p&gt;Originally published on &lt;a href="https://leanzero.net/blog/forge-app-not-loading-ip-allowlist?utm_source=devto&amp;amp;utm_medium=referral&amp;amp;utm_campaign=crosspost" rel="noopener noreferrer"&gt;leanzero.net&lt;/a&gt;. More Atlassian, Forge and local-AI write-ups at &lt;a href="https://leanzero.net/blog?utm_source=devto&amp;amp;utm_medium=referral&amp;amp;utm_campaign=crosspost" rel="noopener noreferrer"&gt;leanzero.net/blog&lt;/a&gt;, and if you're planning a migration or a Forge app, that's what we do: &lt;a href="https://leanzero.net/services?utm_source=devto&amp;amp;utm_medium=referral&amp;amp;utm_campaign=crosspost" rel="noopener noreferrer"&gt;leanzero.net/services&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>forge</category>
      <category>jira</category>
      <category>atlassian</category>
      <category>security</category>
    </item>
    <item>
      <title>Forge Custom UI blank page after deploy: Vite asset paths</title>
      <dc:creator>Mihai Perdum</dc:creator>
      <pubDate>Tue, 17 Nov 2026 05:59:43 +0000</pubDate>
      <link>https://dev.to/mihai_leanzero/forge-custom-ui-blank-page-after-deploy-vite-asset-paths-49ia</link>
      <guid>https://dev.to/mihai_leanzero/forge-custom-ui-blank-page-after-deploy-vite-asset-paths-49ia</guid>
      <description>&lt;p&gt;A Forge Custom UI app built with Vite can render under &lt;code&gt;forge tunnel&lt;/code&gt; and then show a blank page after &lt;code&gt;forge deploy&lt;/code&gt;. The cause is Vite's default build, which writes absolute asset paths such as &lt;code&gt;/assets/index-xxx.js&lt;/code&gt; into &lt;code&gt;index.html&lt;/code&gt;. We reproduced it on our Jira test site on 17 November 2026, and both assets returned HTTP 422 with the body &lt;code&gt;Invalid URL&lt;/code&gt;. Adding &lt;code&gt;base: './'&lt;/code&gt; to &lt;code&gt;vite.config.js&lt;/code&gt; fixed the deployed panel.&lt;/p&gt;

&lt;p&gt;If you're new to these names: Forge is Atlassian's platform for apps that run on Atlassian's cloud, and Custom UI is the Forge option where your own HTML and JavaScript run inside an iframe. Vite is the front-end build tool that turns your source into the files Forge serves. &lt;code&gt;forge tunnel&lt;/code&gt; serves the app from your own machine while you develop, and &lt;code&gt;forge deploy&lt;/code&gt; uploads it to Atlassian.&lt;/p&gt;

&lt;p&gt;People keep running into this one. On 24 July 2025 a developer posted on the Atlassian developer community that their &lt;a href="https://community.developer.atlassian.com/t/issue-panel-is-not-working-on-dev-mode-without-forge-tunnel/94075" rel="noopener noreferrer"&gt;issue panel was not working without forge tunnel&lt;/a&gt;. "Everything works perfectly when I run it locally using forge tunnel," they wrote. "However, after building the app and deploying it with forge deploy, the app does not appear on the issue panel." Their screenshot shows a panel with a title and an empty body, the same picture we got. The next day an Atlassian staff member asked them to hard-refresh the page and read the browser console. About two hours later a second staff member pointed at the &lt;code&gt;index.html&lt;/code&gt; in the build output, because the assets in its head "should be using relative paths".&lt;/p&gt;

&lt;p&gt;So we built a small panel with the current Vite React template (Vite 8.3.8) and ran it three ways. Run A was deployed with the default config. Run B was the same build under the tunnel, and run C was deployed again with the one-line change. This page has the console lines from each run so you can match them against yours, and one image path the setting didn't fix for us.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Note&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Prerequisites&lt;/strong&gt; — A Jira or Confluence Cloud site where you can install apps (we used wolfaenpak.atlassian.net, our test site). A Forge Custom UI app you can deploy, which means you're its developer or a contributor on it. We ran Forge CLI 14.1.0 on Node.js 24.15.0 with Vite 8.3.8, React 19.3.1 and @⁠forge/bridge 7.3.0, in Chrome for Testing 149. When you're done you'll have a deployed panel that renders, and a check you can run before each deploy.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;[[steps]]&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Confirm the symptom in the browser&lt;/strong&gt; — two failed asset requests on the &lt;code&gt;cdn.prod.atlassian-dev.net&lt;/code&gt; host (Step 1).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Check index.html for absolute paths&lt;/strong&gt; — a leading slash in the head is the cause (Step 2).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Set base: './' in the Vite config&lt;/strong&gt; — rebuild, and the paths turn relative (Step 3).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Fix root-absolute strings in your JavaScript&lt;/strong&gt; — the setting leaves a &lt;code&gt;/logo.png&lt;/code&gt; typed as a string alone (Step 4).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Deploy and check the panel&lt;/strong&gt; — the assets load from inside your app's folder (Step 5).&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Why a Forge Custom UI app works with forge tunnel and is not working without the tunnel
&lt;/h2&gt;

&lt;p&gt;&lt;code&gt;forge tunnel&lt;/code&gt; and &lt;code&gt;forge deploy&lt;/code&gt; serve your files from different places.&lt;/p&gt;

&lt;p&gt;When you run &lt;code&gt;forge tunnel&lt;/code&gt;, the Forge CLI serves the folder named in your manifest's &lt;code&gt;resources&lt;/code&gt; entry from your own machine. In our run the panel's iframe pointed at &lt;code&gt;http://localhost:8000/&lt;/code&gt;, and &lt;code&gt;curl http://localhost:8000/assets/index-U0oGil3V.js&lt;/code&gt; returned 200. Your build folder is the root of that little server, so a path that starts with a slash finds its file.&lt;/p&gt;

&lt;p&gt;After &lt;code&gt;forge deploy&lt;/code&gt;, the same folder lives on Atlassian's content delivery network, several folders deep. The iframe URL we saw looked like this (ids replaced):&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F265sbkf6whhmkpivevy1.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F265sbkf6whhmkpivevy1.png" title="Illustration, generated locally with ERNIE-Image. After forge deploy the same folder lives on Atlassian's content delivery network, several folders deep. The ladder was always going to fall short." alt="Two boxy robots on a cobalt blue background. One stands on flat ground dropping a parcel straight into a low open crate; the other stands on top of a wobbly stack of five crates with a wooden ladder leaning against it, far from a glowing parcel on a pole to the right." width="800" height="448"&gt;&lt;/a&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;https://&amp;lt;app-host&amp;gt;.cdn.prod.atlassian-dev.net/&amp;lt;app id&amp;gt;/&amp;lt;environment id&amp;gt;/&amp;lt;per-deploy id&amp;gt;/panel/_ctx_&amp;lt;blob&amp;gt;/
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;code&gt;panel&lt;/code&gt; is the resource key from our manifest. The first id matched the app id in &lt;code&gt;manifest.yml&lt;/code&gt;. The second matched the development environment in &lt;code&gt;forge environments list&lt;/code&gt;. The third changed between our two deploys, so it's probably a per-deploy id (Atlassian's docs don't name it). That means &lt;code&gt;/assets/index-U0oGil3V.js&lt;/code&gt; asks for a file at the top of the host, outside your app, and &lt;code&gt;./assets/index-U0oGil3V.js&lt;/code&gt; asks for one next to &lt;code&gt;index.html&lt;/code&gt;. Atlassian's Custom UI page says the same in its &lt;a href="https://developer.atlassian.com/platform/forge/extend-ui-with-custom-options/#accessing-static-assets" rel="noopener noreferrer"&gt;Accessing static assets&lt;/a&gt; section: "instead of including an image at "/assets/image.png", you should use "./assets/image.png"".&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Ftorp46zxmneot61gtb9k.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Ftorp46zxmneot61gtb9k.png" title="Run B, the default build served by forge tunnel. Compare the first row with the deployed panel in Step 5: under the tunnel even /logo.png loads." alt="The Vite base demo panel rendered on work item LZPT-186 under forge tunnel, with /logo.png, ./logo.png and import logo all marked loaded" width="800" height="270"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Here is what runs A, B and C did. Between A and B we changed how the app was served and left the build alone.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Run&lt;/th&gt;
&lt;th&gt;Vite config&lt;/th&gt;
&lt;th&gt;Served by&lt;/th&gt;
&lt;th&gt;Panel&lt;/th&gt;
&lt;th&gt;Asset requests&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;A&lt;/td&gt;
&lt;td&gt;default&lt;/td&gt;
&lt;td&gt;&lt;code&gt;forge deploy&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;title and DEV lozenge, empty body&lt;/td&gt;
&lt;td&gt;2 of 2 returned 422&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;B&lt;/td&gt;
&lt;td&gt;default&lt;/td&gt;
&lt;td&gt;&lt;code&gt;forge tunnel&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;fully rendered&lt;/td&gt;
&lt;td&gt;4 of 4 returned 200&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;C&lt;/td&gt;
&lt;td&gt;&lt;code&gt;base: './'&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;&lt;code&gt;forge deploy&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;rendered&lt;/td&gt;
&lt;td&gt;JS and CSS returned 200&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Nothing warned us on the way to run A. &lt;code&gt;forge deploy&lt;/code&gt; ran its lint and printed &lt;code&gt;No issues found.&lt;/code&gt; followed by &lt;code&gt;✔ Deployed&lt;/code&gt;. I think that's a big part of why this question keeps coming back on the forum.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 1. Confirm the symptom: 422 or 403 on the Custom UI static assets
&lt;/h2&gt;

&lt;p&gt;Start by making sure this is your problem. The console tells you in a minute.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;In your browser, open the page that holds your app (for us, a work item with the panel on it). The panel shows its title and an empty body.&lt;/li&gt;
&lt;li&gt;Open the developer tools and select the &lt;strong&gt;Console&lt;/strong&gt; tab, then reload the page. Failed requests are listed in red.&lt;/li&gt;
&lt;li&gt;Look for requests to a host ending in &lt;code&gt;cdn.prod.atlassian-dev.net&lt;/code&gt; whose path starts right at &lt;code&gt;/assets/&lt;/code&gt; (or &lt;code&gt;/static/&lt;/code&gt;), with no ids in between.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;You should see something like this, one line per script or stylesheet in your &lt;code&gt;index.html&lt;/code&gt;:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Failed to load resource: the server responded with a status of 422 ()   https://&amp;lt;app-host&amp;gt;.cdn.prod.atlassian-dev.net/assets/index-nqMpL4T3.css
Failed to load resource: the server responded with a status of 422 ()   https://&amp;lt;app-host&amp;gt;.cdn.prod.atlassian-dev.net/assets/index-U0oGil3V.js
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;In the &lt;strong&gt;Network&lt;/strong&gt; tab, each of those responses is 11 bytes long and says &lt;code&gt;Invalid URL&lt;/code&gt;. Our iframe's own document loaded. What failed were the two files it asked for by absolute path.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fiyhpxsw60uvcjwtkhykm.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fiyhpxsw60uvcjwtkhykm.png" title="Run A on our test site, Vite 8.3.8 default build after forge deploy. Look under the panel title: there's no error and no spinner, the body is empty." alt="The Vite base demo panel on a Jira work item, showing its title and a DEV lozenge with nothing underneath, above Jira's Agent sessions and Activity sections" width="800" height="270"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Your status code may differ. Atlassian's troubleshooting list files this cause under "403 forbidden error", and a &lt;a href="https://community.developer.atlassian.com/t/60655" rel="noopener noreferrer"&gt;2022 thread&lt;/a&gt; pasted &lt;code&gt;net::ERR_ABORTED 403&lt;/code&gt; for it. We got 422 in Chromium. If the URL in your console starts at &lt;code&gt;/assets/&lt;/code&gt; right after the host, carry on to Step 2 whatever the number is.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 2. Check index.html for absolute paths before you deploy
&lt;/h2&gt;

&lt;p&gt;Now look at what your bundler wrote. You can do this on your machine, before any deploy.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;In a terminal, go to your Custom UI folder (ours is &lt;code&gt;static/panel&lt;/code&gt;).&lt;/li&gt;
&lt;li&gt;Run &lt;code&gt;npm run build&lt;/code&gt;. Vite writes the &lt;code&gt;dist&lt;/code&gt; folder.&lt;/li&gt;
&lt;li&gt;Print the built entry file with &lt;code&gt;cat dist/index.html&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Read the &lt;code&gt;src&lt;/code&gt; and &lt;code&gt;href&lt;/code&gt; values in the head.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;With the default Vite config, we got this:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight html"&gt;&lt;code&gt;&lt;span class="nt"&gt;&amp;lt;link&lt;/span&gt; &lt;span class="na"&gt;rel&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"icon"&lt;/span&gt; &lt;span class="na"&gt;type&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"image/svg+xml"&lt;/span&gt; &lt;span class="na"&gt;href&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"/favicon.svg"&lt;/span&gt; &lt;span class="nt"&gt;/&amp;gt;&lt;/span&gt;
&lt;span class="nt"&gt;&amp;lt;script&lt;/span&gt; &lt;span class="na"&gt;type&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"module"&lt;/span&gt; &lt;span class="na"&gt;crossorigin&lt;/span&gt; &lt;span class="na"&gt;src&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"/assets/index-U0oGil3V.js"&lt;/span&gt;&lt;span class="nt"&gt;&amp;gt;&amp;lt;/script&amp;gt;&lt;/span&gt;
&lt;span class="nt"&gt;&amp;lt;link&lt;/span&gt; &lt;span class="na"&gt;rel&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"stylesheet"&lt;/span&gt; &lt;span class="na"&gt;crossorigin&lt;/span&gt; &lt;span class="na"&gt;href&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"/assets/index-nqMpL4T3.css"&lt;/span&gt;&lt;span class="nt"&gt;&amp;gt;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;All three paths start with a slash. Vite is doing what it's told: its &lt;code&gt;base&lt;/code&gt; option &lt;a href="https://vite.dev/config/shared-options.html#base" rel="noopener noreferrer"&gt;defaults to &lt;code&gt;/&lt;/code&gt;&lt;/a&gt;, which is right for a site served from the top of its own domain and wrong for a Forge resource.&lt;/p&gt;

&lt;p&gt;This one-liner prints any root-absolute path in the built file and prints nothing when the file is clean:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;grep -nE &lt;span class="s1"&gt;'(src|href)="/'&lt;/span&gt; dist/index.html
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;On our default build it printed the three lines from the head:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;5:    &amp;lt;link rel="icon" type="image/svg+xml" href="/favicon.svg" /&amp;gt;
8:    &amp;lt;script type="module" crossorigin src="/assets/index-U0oGil3V.js"&amp;gt;&amp;lt;/script&amp;gt;
9:    &amp;lt;link rel="stylesheet" crossorigin href="/assets/index-nqMpL4T3.css"&amp;gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  Step 3. The fix for a Forge Custom UI app built with Vite: base: './'
&lt;/h2&gt;

&lt;p&gt;Vite's docs describe &lt;code&gt;./&lt;/code&gt; as the value "for embedded deployment", and a Forge iframe is exactly that.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Open &lt;code&gt;vite.config.js&lt;/code&gt; (or &lt;code&gt;vite.config.ts&lt;/code&gt;) in your Custom UI folder and add &lt;code&gt;base: './',&lt;/code&gt; inside &lt;code&gt;defineConfig&lt;/code&gt;:
&lt;/li&gt;
&lt;/ol&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight javascript"&gt;&lt;code&gt;&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="n"&gt;react&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="s1"&gt;'@vitejs/plugin-react'&lt;/span&gt;
&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="n"&gt;defineConfig&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="s1"&gt;'vite'&lt;/span&gt;

&lt;span class="k"&gt;export&lt;/span&gt; &lt;span class="k"&gt;default&lt;/span&gt; &lt;span class="nf"&gt;defineConfig&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="n"&gt;base&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s1"&gt;'./'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="n"&gt;plugins&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="nf"&gt;react&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;ol&gt;
&lt;li&gt;Run &lt;code&gt;npm run build&lt;/code&gt; again. Vite rewrites &lt;code&gt;dist/index.html&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Run &lt;code&gt;cat dist/index.html&lt;/code&gt; and read the head once more.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;You should see relative paths now:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight html"&gt;&lt;code&gt;&lt;span class="nt"&gt;&amp;lt;link&lt;/span&gt; &lt;span class="na"&gt;rel&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"icon"&lt;/span&gt; &lt;span class="na"&gt;type&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"image/svg+xml"&lt;/span&gt; &lt;span class="na"&gt;href&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"./favicon.svg"&lt;/span&gt; &lt;span class="nt"&gt;/&amp;gt;&lt;/span&gt;
&lt;span class="nt"&gt;&amp;lt;script&lt;/span&gt; &lt;span class="na"&gt;type&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"module"&lt;/span&gt; &lt;span class="na"&gt;crossorigin&lt;/span&gt; &lt;span class="na"&gt;src&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"./assets/index-BibfWtNU.js"&lt;/span&gt;&lt;span class="nt"&gt;&amp;gt;&amp;lt;/script&amp;gt;&lt;/span&gt;
&lt;span class="nt"&gt;&amp;lt;link&lt;/span&gt; &lt;span class="na"&gt;rel&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"stylesheet"&lt;/span&gt; &lt;span class="na"&gt;crossorigin&lt;/span&gt; &lt;span class="na"&gt;href&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"./assets/index-nqMpL4T3.css"&lt;/span&gt;&lt;span class="nt"&gt;&amp;gt;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Our JavaScript file got a new hash (&lt;code&gt;U0oGil3V&lt;/code&gt; became &lt;code&gt;BibfWtNU&lt;/code&gt;) and the CSS file kept its name. Vite's &lt;a href="https://vite.dev/guide/build.html" rel="noopener noreferrer"&gt;build guide&lt;/a&gt; explains that a relative base makes "all generated URLs to be relative to each file", so images you &lt;code&gt;import&lt;/code&gt; in your code are covered too.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 4. Fix the paths you typed in your JavaScript (base doesn't touch /logo.png)
&lt;/h2&gt;

&lt;p&gt;I didn't expect this next result. Vite's &lt;code&gt;base&lt;/code&gt; setting rewrites the URLs Vite processes during the build, and its build guide lists them: "JS-imported asset URLs, CSS url() references, and asset references in your .html files". A path you type as a string in your JavaScript, or in JSX (the HTML-like markup inside a React component), stays as you wrote it.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F9ve1dedg1g8trczsi44d.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F9ve1dedg1g8trczsi44d.png" title="Illustration, generated locally with ERNIE-Image. Vite's base setting rewrites only the URLs Vite generates, so a path you typed by hand stays exactly as you wrote it. The roller never touches the sign." alt="On an emerald green background, a factory robot runs a paint roller over a row of boxes on a conveyor, stamping each with a fresh blank yellow label, while a second robot beside the machine holds up two hand-painted wooden signs that the roller passes straight over; a bare light bulb glows above the first robot." width="800" height="448"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;We put the same image into the panel with each kind of reference, to see which ones survive a deploy:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Reference in the component&lt;/th&gt;
&lt;th&gt;Under &lt;code&gt;forge tunnel&lt;/code&gt;
&lt;/th&gt;
&lt;th&gt;Deployed with &lt;code&gt;base: './'&lt;/code&gt;
&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;code&gt;&amp;lt;img src="/logo.png"&amp;gt;&lt;/code&gt; (file in &lt;code&gt;public/&lt;/code&gt;)&lt;/td&gt;
&lt;td&gt;loaded&lt;/td&gt;
&lt;td&gt;failed, 422 &lt;code&gt;Invalid URL&lt;/code&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;code&gt;&amp;lt;img src="./logo.png"&amp;gt;&lt;/code&gt; (same file)&lt;/td&gt;
&lt;td&gt;loaded&lt;/td&gt;
&lt;td&gt;loaded&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;import logo from './assets/hero.png'&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;loaded&lt;/td&gt;
&lt;td&gt;loaded&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Vite's &lt;a href="https://vite.dev/guide/assets.html" rel="noopener noreferrer"&gt;asset guide&lt;/a&gt; tells you to reference files in &lt;code&gt;public/&lt;/code&gt; "using root absolute path". Written as a string in our JSX, that was the form that failed once deployed.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;In your editor, search the JavaScript files in your &lt;code&gt;src&lt;/code&gt; folder for &lt;code&gt;src="/&lt;/code&gt; and &lt;code&gt;href="/&lt;/code&gt;. Each hit is a path that will leave your app's folder once deployed.&lt;/li&gt;
&lt;li&gt;Change each one to start with &lt;code&gt;./&lt;/code&gt;, or import the file and use the imported value. After the next build, the file loads from your app's folder.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Vite also documents &lt;code&gt;import.meta.env.BASE_URL&lt;/code&gt; for building such a URL at runtime. We didn't run that variant.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 5. Deploy and check the panel
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;In the app's root folder, run &lt;code&gt;forge deploy -e development&lt;/code&gt;. The CLI prints &lt;code&gt;✔ Deployed&lt;/code&gt;. We didn't need &lt;code&gt;forge install --upgrade&lt;/code&gt; for this change.&lt;/li&gt;
&lt;li&gt;In the browser, reload the page with your app, with the developer tools still open. The panel renders.&lt;/li&gt;
&lt;li&gt;In the &lt;strong&gt;Network&lt;/strong&gt; tab, select one of the asset requests and read its URL.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;You should see status 200, and a URL that keeps the long app path in front of &lt;code&gt;assets/&lt;/code&gt;:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;200  https://&amp;lt;app-host&amp;gt;.cdn.prod.atlassian-dev.net/&amp;lt;app id&amp;gt;/&amp;lt;environment id&amp;gt;/&amp;lt;per-deploy id&amp;gt;/panel/_ctx_&amp;lt;blob&amp;gt;/assets/index-BibfWtNU.js
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fwvje6h5fs7h636eta6ez.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fwvje6h5fs7h636eta6ez.png" title="Run C, the same app deployed with base './'. The panel renders, and the first row shows the /logo.png typed as a string still failing while the other two load." alt="The Vite base demo panel rendered on work item LZPT-186, with three image rows: /logo.png marked FAILED with a broken image icon, ./logo.png and import logo both marked loaded" width="800" height="297"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;If the panel has content and no request in the console goes to &lt;code&gt;/assets/&lt;/code&gt; directly under the host, you're done.&lt;/p&gt;

&lt;p&gt;The tunnel still serves the fixed build, by the way. We ran &lt;code&gt;forge tunnel&lt;/code&gt; again afterwards, and &lt;code&gt;curl http://localhost:8000/&lt;/code&gt; returned the relative-path &lt;code&gt;index.html&lt;/code&gt; with status 200, as did both asset files. That was a curl check; the panel wasn't reopened in the browser for it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Create React App and rsbuild: the same relative-path fix when a Forge app fails in production
&lt;/h2&gt;

&lt;p&gt;Vite isn't special here. Any bundler that assumes it owns the root of a domain produces the same empty panel. Our runs covered Vite. What follows comes from each tool's documentation and from public threads.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Create React App.&lt;/strong&gt; Atlassian's own &lt;a href="https://developer.atlassian.com/platform/forge/build-a-custom-ui-app-in-jira/" rel="noopener noreferrer"&gt;Build a Custom UI app in Jira&lt;/a&gt; tutorial uses create-react-app. Atlassian's troubleshooting list says to set &lt;code&gt;"homepage": "./"&lt;/code&gt; in &lt;code&gt;package.json&lt;/code&gt;. The Create React App &lt;a href="https://create-react-app.dev/docs/deployment/" rel="noopener noreferrer"&gt;deployment page&lt;/a&gt; writes it as &lt;code&gt;"homepage": "."&lt;/code&gt; and says this makes "all the asset paths … relative to index.html". The thread &lt;a href="https://community.developer.atlassian.com/t/my-forge-app-only-loads-when-im-tunneling-the-app-from-my-local-pc/47401" rel="noopener noreferrer"&gt;"My Forge App only Loads when I'm Tunneling the app from my local pc"&lt;/a&gt; had 2,710 views when we read it on 17 November 2026. In it, a second developer replied in April 2021 that adding &lt;code&gt;"homepage": "."&lt;/code&gt; fixed the same symptom for them. (The original poster's own cause turned out to be a react-router setting, so read past the accepted answer.)&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;rsbuild.&lt;/strong&gt; In the thread &lt;a href="https://community.developer.atlassian.com/t/91065" rel="noopener noreferrer"&gt;"Forge app fails in production"&lt;/a&gt;, a developer who had moved from craco to rsbuild wrote in October 2025 that the paths in &lt;code&gt;index.html&lt;/code&gt; had to be relative, and added &lt;code&gt;output: { assetPrefix: './' }&lt;/code&gt;. They said it then worked in production, and that the app still didn't work through the tunnel from the build folder (only through a port). The &lt;a href="https://rsbuild.rs/config/output/asset-prefix" rel="noopener noreferrer"&gt;rsbuild docs&lt;/a&gt; call a relative &lt;code&gt;assetPrefix&lt;/code&gt; "not recommended" and offer &lt;code&gt;'auto'&lt;/code&gt;, which generates relative paths based on file location.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;A stray base tag.&lt;/strong&gt; In January 2026 another developer with a Vite Custom UI &lt;a href="https://community.developer.atlassian.com/t/75076/5" rel="noopener noreferrer"&gt;reported&lt;/a&gt; the message &lt;code&gt;was blocked because of a disallowed MIME type ("")&lt;/code&gt; on &lt;code&gt;/assets/index-&amp;lt;hash&amp;gt;.js&lt;/code&gt;. Their fix was &lt;code&gt;base: './'&lt;/code&gt; plus removing a &lt;code&gt;&amp;lt;base href="/"&amp;gt;&lt;/code&gt; tag from &lt;code&gt;index.html&lt;/code&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  forge tunnel with the Vite dev server: tunnel.port, and two things we hit
&lt;/h2&gt;

&lt;p&gt;Run B used the built &lt;code&gt;dist&lt;/code&gt; folder, which means a rebuild after each change. You can point the tunnel at Vite's dev server instead. Atlassian's &lt;a href="https://developer.atlassian.com/platform/forge/tunneling/" rel="noopener noreferrer"&gt;tunneling page&lt;/a&gt; documents a &lt;code&gt;tunnel&lt;/code&gt; block on the resource (the manifest's Resources reference page doesn't list it):&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight yaml"&gt;&lt;code&gt;&lt;span class="na"&gt;resources&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
  &lt;span class="p"&gt;-&lt;/span&gt; &lt;span class="na"&gt;key&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;panel&lt;/span&gt;
    &lt;span class="na"&gt;path&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;static/panel/dist&lt;/span&gt;
    &lt;span class="na"&gt;tunnel&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
      &lt;span class="na"&gt;port&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;5173&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;On Forge CLI 14.1.0 the tunnel picked this block up without a redeploy in our run. Atlassian's page says to deploy after a manifest change, so run &lt;code&gt;forge deploy&lt;/code&gt; if yours doesn't.&lt;/p&gt;

&lt;p&gt;With &lt;code&gt;vite --port 5173 --strictPort&lt;/code&gt; running next to &lt;code&gt;forge tunnel&lt;/code&gt;, our panel rendered from the dev server and the console showed &lt;code&gt;[vite] connected.&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;Styling broke first. Our panel came up unstyled, and the console said why: &lt;code&gt;Applying inline style violates the following Content Security Policy directive 'style-src 'self' …&lt;/code&gt;. Vite's dev client injects CSS as inline styles, and Forge's content security policy for Custom UI (the browser rule that says which scripts and styles a page may run) blocked them. The deployed build wasn't affected, because there the CSS is a separate file. Atlassian's &lt;a href="https://developer.atlassian.com/platform/forge/add-content-security-and-egress-controls/" rel="noopener noreferrer"&gt;content security page&lt;/a&gt; documents a &lt;code&gt;permissions.content.styles&lt;/code&gt; entry with &lt;code&gt;unsafe-inline&lt;/code&gt; to allow inline CSS. We haven't tried it on this error, and that's where I'd look next.&lt;/p&gt;

&lt;p&gt;Chrome was the other problem. In headless Chrome 149 the tunnel iframe didn't load at all until we granted the &lt;code&gt;local-network-access&lt;/code&gt; permission. Until then, Jira's page logged &lt;code&gt;The target origin provided ('http://localhost:8000') does not match the recipient window's origin ('null')&lt;/code&gt;. Chrome &lt;a href="https://developer.chrome.com/blog/local-network-access" rel="noopener noreferrer"&gt;announced&lt;/a&gt; a permission prompt for requests from public pages to local addresses, launching in Chrome 142. So if your tunnel shows an empty frame in a recent Chrome, look for a blocked local network permission on the Jira tab.&lt;/p&gt;

&lt;h2&gt;
  
  
  If it didn't work
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;What you see&lt;/th&gt;
&lt;th&gt;Where&lt;/th&gt;
&lt;th&gt;What it means&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;code&gt;Failed to load resource: the server responded with a status of 422 ()&lt;/code&gt; on &lt;code&gt;…cdn.prod.atlassian-dev.net/assets/…&lt;/code&gt;
&lt;/td&gt;
&lt;td&gt;Console, deployed app&lt;/td&gt;
&lt;td&gt;A root-absolute path in &lt;code&gt;index.html&lt;/code&gt;. Steps 2 and 3.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;The same 422 on one image or font after the fix&lt;/td&gt;
&lt;td&gt;Console, deployed app&lt;/td&gt;
&lt;td&gt;A path typed as a string in your JavaScript. Step 4.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;code&gt;net::ERR_ABORTED 403&lt;/code&gt; on &lt;code&gt;…/static/css/main.&amp;lt;hash&amp;gt;.css&lt;/code&gt;
&lt;/td&gt;
&lt;td&gt;Console, deployed app&lt;/td&gt;
&lt;td&gt;The same cause, as reported in a 2022 thread. Check your built &lt;code&gt;index.html&lt;/code&gt; (Step 2).&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;was blocked because of a disallowed MIME type ("")&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Console, deployed app&lt;/td&gt;
&lt;td&gt;Reported in January 2026 by a developer who removed a &lt;code&gt;&amp;lt;base href="/"&amp;gt;&lt;/code&gt; tag from &lt;code&gt;index.html&lt;/code&gt; and also set &lt;code&gt;base: './'&lt;/code&gt;.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;Applying inline style violates the following Content Security Policy directive&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Console, tunnel with dev server&lt;/td&gt;
&lt;td&gt;Forge's content security policy blocks the dev server's inline CSS. The deployed build is fine.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;does not match the recipient window's origin ('null')&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Console of the Jira page, tunnel&lt;/td&gt;
&lt;td&gt;The browser blocked the iframe to localhost. Check the local network permission.&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;If your console shows none of these, start where Atlassian staff started in the 2025 thread: hard-refresh the page to rule out the cache, then read the console again.&lt;/p&gt;

&lt;h2&gt;
  
  
  What you have now, and what we left out
&lt;/h2&gt;

&lt;p&gt;[[takeaways]]&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Your Custom UI build writes relative paths into &lt;code&gt;index.html&lt;/code&gt;, and the deployed panel renders.&lt;/li&gt;
&lt;li&gt;You have a &lt;code&gt;grep&lt;/code&gt; check to run on &lt;code&gt;dist/index.html&lt;/code&gt; before each &lt;code&gt;forge deploy&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Not covered by that check: a root-absolute string in your JavaScript, which lives outside &lt;code&gt;index.html&lt;/code&gt; (Step 4).&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;By default &lt;code&gt;grep&lt;/code&gt; exits 0 when it finds a path and 1 when the file is clean, which is the wrong way round for a pipeline. If you &lt;a href="https://leanzero.net/tutorials/cognirunner-forge-app-ci-cd-bitbucket-pipelines?utm_source=devto&amp;amp;utm_medium=referral&amp;amp;utm_campaign=crosspost" rel="noopener noreferrer"&gt;deploy your Forge app through CI/CD&lt;/a&gt;, wrap it like this so a bad build stops the job:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nb"&gt;test&lt;/span&gt; -f dist/index.html &lt;span class="o"&gt;||&lt;/span&gt; &lt;span class="nb"&gt;exit&lt;/span&gt; 1
&lt;span class="k"&gt;if&lt;/span&gt; grep -nE &lt;span class="s1"&gt;'(src|href)="/'&lt;/span&gt; dist/index.html&lt;span class="o"&gt;;&lt;/span&gt; &lt;span class="k"&gt;then&lt;/span&gt; &lt;span class="nb"&gt;exit&lt;/span&gt; 1&lt;span class="o"&gt;;&lt;/span&gt; &lt;span class="k"&gt;fi&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;To confirm it's wired the right way, save the two lines as &lt;code&gt;check-paths.sh&lt;/code&gt; in your Custom UI folder and run &lt;code&gt;bash check-paths.sh; echo $?&lt;/code&gt; on both builds (pasted straight into a terminal, the bare &lt;code&gt;exit 1&lt;/code&gt; would close it). On our default build it printed the three lines and exited 1, and on the fixed build it printed nothing and exited 0.&lt;/p&gt;

&lt;p&gt;Our measurements come from one setup: Forge CLI 14.1.0, Vite 8.3.8 with the React template, a &lt;code&gt;jira:issuePanel&lt;/code&gt;, and Chromium. Firefox and Forge CLI 15.1.0 (it refused our Node.js version) are outside it.&lt;/p&gt;

&lt;p&gt;If you're building more with Custom UI, two of our other tutorials pick up from here: &lt;a href="https://leanzero.net/tutorials/forge-object-store-upload-download-files?utm_source=devto&amp;amp;utm_medium=referral&amp;amp;utm_campaign=crosspost" rel="noopener noreferrer"&gt;uploading and downloading files with the Forge Object Store&lt;/a&gt; and &lt;a href="https://leanzero.net/tutorials/dark-mode-done-right-in-forge-custom-ui?utm_source=devto&amp;amp;utm_medium=referral&amp;amp;utm_campaign=crosspost" rel="noopener noreferrer"&gt;dark mode in Forge Custom UI&lt;/a&gt;. Would you like a test to catch the empty panel before a person does? We wrote up how we run &lt;a href="https://leanzero.net/tutorials/forge-app-live-ui-e2e-testing?utm_source=devto&amp;amp;utm_medium=referral&amp;amp;utm_campaign=crosspost" rel="noopener noreferrer"&gt;end-to-end UI tests against a deployed Forge app with Playwright&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Did you get a status code other than 422 or 403 for this? I'd like to know which browser and which bundler you were on.&lt;/p&gt;




&lt;p&gt;Originally published on &lt;a href="https://leanzero.net/tutorials/forge-custom-ui-vite-blank-after-deploy?utm_source=devto&amp;amp;utm_medium=referral&amp;amp;utm_campaign=crosspost" rel="noopener noreferrer"&gt;leanzero.net&lt;/a&gt;. More Atlassian, Forge and local-AI write-ups at &lt;a href="https://leanzero.net/blog?utm_source=devto&amp;amp;utm_medium=referral&amp;amp;utm_campaign=crosspost" rel="noopener noreferrer"&gt;leanzero.net/blog&lt;/a&gt;, and if you're planning a migration or a Forge app, that's what we do: &lt;a href="https://leanzero.net/services?utm_source=devto&amp;amp;utm_medium=referral&amp;amp;utm_campaign=crosspost" rel="noopener noreferrer"&gt;leanzero.net/services&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>forge</category>
      <category>jira</category>
      <category>vite</category>
      <category>atlassian</category>
    </item>
    <item>
      <title>Atlassian AI Training Opt Out: What Each Plan Can Switch Off</title>
      <dc:creator>Mihai Perdum</dc:creator>
      <pubDate>Mon, 16 Nov 2026 11:59:03 +0000</pubDate>
      <link>https://dev.to/mihai_leanzero/atlassian-ai-training-opt-out-what-each-plan-can-switch-off-a5f</link>
      <guid>https://dev.to/mihai_leanzero/atlassian-ai-training-opt-out-what-each-plan-can-switch-off-a5f</guid>
      <description>&lt;p&gt;If your Atlassian organization is on Free or Standard and nobody has changed one particular admin setting since 17 August 2026, Atlassian has been allowed to use your Jira and Confluence content to improve its apps for everyone. It's on by default. On Premium and Enterprise the same content starts switched off, but every plan below Enterprise still contributes metadata, which is numbers and patterns Atlassian derives from your content, and you can't stop it.&lt;/p&gt;

&lt;p&gt;The Atlassian AI training opt out is one setting per organization, called &lt;strong&gt;Data contribution&lt;/strong&gt;, under &lt;strong&gt;Security&lt;/strong&gt; in Atlassian Administration. Every plan can switch in-app data (the content your people write) on or off there. Metadata has a switch only on Enterprise.&lt;/p&gt;

&lt;p&gt;A lot of admins are finding this out late. On 21 April someone posted "&lt;a href="https://community.atlassian.com/forums/Jira-questions/Atlassian-Enables-Default-Customer-Data-Collection-to-Train-AI/qaa-p/3224658" rel="noopener noreferrer"&gt;Atlassian Enables Default Customer Data Collection to Train AI&lt;/a&gt;" on the Community. It had 3,863 views when I checked on 16 November, and most of what ranks for it was written before the change started.&lt;/p&gt;

&lt;p&gt;So on 16 November we changed the setting on our own test org, which is on Premium, and switched it back. It took a radio button plus a separate &lt;strong&gt;Save&lt;/strong&gt;, with no confirmation dialog, and our audit log stored both changes with the old and new value. I didn't expect this bit: whether you'll have that audit row at all depends on your subscriptions.&lt;/p&gt;

&lt;h2&gt;
  
  
  Five things we found on our own org
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;The page path is &lt;code&gt;/o/&amp;lt;your org&amp;gt;/data-contribution&lt;/code&gt;, and the sidebar item still carries a &lt;strong&gt;New&lt;/strong&gt; tag.&lt;/li&gt;
&lt;li&gt;On a Premium org there is no metadata switch at all. The page only says "Metadata is always contributed".&lt;/li&gt;
&lt;li&gt;Picking On or Off changes nothing until you click &lt;strong&gt;Save&lt;/strong&gt;, and there's no "are you sure" dialog.&lt;/li&gt;
&lt;li&gt;Our org audit log wrote "Updated in-app data contribution from Off to On" in the same minute we saved. Atlassian's audit log page says organizations without Atlassian Guard (Atlassian's paid security add-on) or an Enterprise plan don't store org-level events at all.&lt;/li&gt;
&lt;li&gt;The guided tour on the page says it plainly: keeping the setting Off and adding spaces one by one lets you "contribute selectively while keeping your organization opted out".&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  What Atlassian AI training data covers: metadata vs in-app data
&lt;/h2&gt;

&lt;p&gt;Atlassian splits your data into two kinds, and the whole opt-out question hangs on which one you mean.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;In-app data&lt;/strong&gt; is what your people type. Atlassian's page on &lt;a href="https://support.atlassian.com/security-and-access-policies/docs/what-types-of-data-does-my-organization-contribute/" rel="noopener noreferrer"&gt;what types of data your organization contributes&lt;/a&gt; lists the titles and content of Confluence pages and the titles, descriptions and comments of Jira work items (Atlassian's current name for issues). Custom status and workflow names count as well. Atlassian's page on &lt;a href="https://www.atlassian.com/trust/ai/data-contribution/how-atlassian-protects-contributed-data" rel="noopener noreferrer"&gt;how it protects contributed data&lt;/a&gt; gives a work item called "Fix login error on iOS after the latest mobile update" as its example.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Metadata&lt;/strong&gt; comes in two kinds. Content attributes are statistics and fields derived from your content. Atlassian's examples are a readability score for a Confluence page, how similar two pages are, a classification like "sales work item", story points, and the SLA (service level agreement) on a Jira Service Management request. Common patterns are things Atlassian finds across many customers in search queries, prompts to Rovo Chat (the chat in Rovo, Atlassian's AI assistant) and configuration, like a work type called "Laptop repair ticket". Atlassian says it drops anything low in frequency that "may be unique to your organization".&lt;/p&gt;

&lt;p&gt;What does Atlassian use metadata for? The same page lists four uses, among them training its search model and root cause analysis suggestions. Its &lt;a href="https://www.atlassian.com/trust/ai/data-contribution/faqs" rel="noopener noreferrer"&gt;data contribution FAQ&lt;/a&gt; adds that data from one app can improve features across the whole portfolio, and that Rovo Chat conversations and search queries fall under the setting too.&lt;/p&gt;

&lt;p&gt;For your data protection lead, the contract side is in Atlassian's &lt;a href="https://www.atlassian.com/legal/data-processing-addendum" rel="noopener noreferrer"&gt;Data Processing Addendum&lt;/a&gt;, effective 17 August 2026. It says Atlassian "must de-identify and aggregate Customer Data and may use such De-identified and Aggregated Data to improve the Cloud Products", in line with these settings.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fshd3xr5b44ag3fsgixom.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fshd3xr5b44ag3fsgixom.png" title="Our Data contribution page on 16 November 2026, on a Premium org. Notice there's no switch for metadata at all, only the sentence saying it is always contributed." alt="Atlassian Administration Data contribution page on our test org: in-app data contribution set to Off, the line In-app data refers to content created by users within Atlassian apps. Metadata is always contributed, and an empty Include in-app data table with Select data to include" width="800" height="514"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Atlassian data contribution settings by plan: what you can switch off
&lt;/h2&gt;

&lt;p&gt;Here's Atlassian's &lt;a href="https://support.atlassian.com/security-and-access-policies/docs/data-contribution-settings/" rel="noopener noreferrer"&gt;Data contribution settings&lt;/a&gt; page as it read on 16 November 2026, put into one table.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Highest active plan&lt;/th&gt;
&lt;th&gt;Metadata&lt;/th&gt;
&lt;th&gt;Can you change it?&lt;/th&gt;
&lt;th&gt;In-app data default&lt;/th&gt;
&lt;th&gt;Can you change it?&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Free&lt;/td&gt;
&lt;td&gt;Always contributed&lt;/td&gt;
&lt;td&gt;No&lt;/td&gt;
&lt;td&gt;On&lt;/td&gt;
&lt;td&gt;Yes, to Off&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Standard&lt;/td&gt;
&lt;td&gt;Always contributed&lt;/td&gt;
&lt;td&gt;No&lt;/td&gt;
&lt;td&gt;On&lt;/td&gt;
&lt;td&gt;Yes, to Off&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Premium&lt;/td&gt;
&lt;td&gt;Always contributed&lt;/td&gt;
&lt;td&gt;No&lt;/td&gt;
&lt;td&gt;Off&lt;/td&gt;
&lt;td&gt;Yes, to On&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Enterprise&lt;/td&gt;
&lt;td&gt;On&lt;/td&gt;
&lt;td&gt;Yes, to Off&lt;/td&gt;
&lt;td&gt;Off&lt;/td&gt;
&lt;td&gt;Yes, to On&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;What counts is the highest plan in your whole organization, and Atlassian says that includes trials. Its own examples help here. Confluence Free plus Jira Standard means in-app data is On. Confluence Standard plus a Jira Premium trial means it's Off. Confluence Free plus Jira Enterprise gives you in-app Off and metadata On, with the metadata switch available. So one Enterprise app is enough to get the metadata switch for the whole organization.&lt;/p&gt;

&lt;p&gt;On Enterprise that switch also "controls metadata contributions from applicable Teamwork Graph connectors too". Teamwork Graph connectors are the ones that bring content from other tools into Atlassian's apps, and Atlassian only uses a connector's data if that connector has a setting on this page.&lt;/p&gt;

&lt;p&gt;The FAQ says you can see your plans under &lt;strong&gt;Apps &amp;gt; Atlassian apps&lt;/strong&gt;. Our &lt;strong&gt;Billing and subscriptions&lt;/strong&gt; page shows a Premium subscription, a Free one and Atlassian Guard, and no Enterprise, which matches what the Data contribution page showed us. Atlassian also warns that "Some Atlassian customers, including those with specific compliance requirements, may see different defaults", so read your own screen before you write anything down.&lt;/p&gt;

&lt;h2&gt;
  
  
  Jira AI training opt out: switch off in-app data, step by step
&lt;/h2&gt;

&lt;p&gt;Before you start: Atlassian lists the role for this as &lt;strong&gt;Organization admin&lt;/strong&gt;, on Atlassian Cloud, any plan. Atlassian Government Cloud doesn't have this setting. If your company has more than one organization, repeat this in each one. When you're done, the page shows in-app data &lt;strong&gt;Off&lt;/strong&gt;, and you have a screenshot of it with the date noted.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Go to &lt;a href="https://admin.atlassian.com" rel="noopener noreferrer"&gt;admin.atlassian.com&lt;/a&gt; and pick your organization in the switcher at the top left. Its name shows above the sidebar.&lt;/li&gt;
&lt;li&gt;In the sidebar, select &lt;strong&gt;Security&lt;/strong&gt;, then &lt;strong&gt;Data contribution&lt;/strong&gt;. The page is headed &lt;strong&gt;Data contribution&lt;/strong&gt;, and a three-step tour pops up over it. Step through it or close it.&lt;/li&gt;
&lt;li&gt;Find &lt;strong&gt;Contribute in-app data to improve Atlassian apps for everyone:&lt;/strong&gt; and read the line under it. If it says "Metadata is always contributed", your highest plan is below Enterprise. Atlassian's page says Enterprise orgs get a metadata setting too (we couldn't check that, because our org is Premium).&lt;/li&gt;
&lt;li&gt;If &lt;strong&gt;Off&lt;/strong&gt; is already selected, nothing needs saving. Go to step 7. Otherwise select &lt;strong&gt;Off&lt;/strong&gt;. The table below changes to &lt;strong&gt;Include in-app data&lt;/strong&gt; with &lt;strong&gt;No data included&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;Select &lt;strong&gt;Save&lt;/strong&gt; at the top right. The button only appears after you change the radio button, and without this click nothing is stored.&lt;/li&gt;
&lt;li&gt;Reload the page. &lt;strong&gt;Off&lt;/strong&gt; stays selected. Good.&lt;/li&gt;
&lt;li&gt;Take a screenshot of the page and write down the date you took it. If you changed the setting and your org has Atlassian Guard or an Enterprise plan, also open &lt;strong&gt;Insights &amp;gt; Audit log&lt;/strong&gt; and look for the row "Updated in-app data contribution from On to Off".&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;When we tested the other direction (Off to On), the table swapped to &lt;strong&gt;Exclude in-app data&lt;/strong&gt;, with &lt;strong&gt;Select data to exclude&lt;/strong&gt;, and the blue &lt;strong&gt;Save&lt;/strong&gt; button appeared. We also left the page once without saving, and the setting was still Off when we came back.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fzjwmjvuqk1qqmtvm0v22.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fzjwmjvuqk1qqmtvm0v22.png" title="The page right after we picked On, before Save. Notice the Save button at the top right and the table that now says Exclude instead of Include." alt="The same Data contribution page after selecting On but before saving: a blue Save button at the top right and the table below renamed to Exclude in-app data, No data excluded, Select data to exclude" width="800" height="523"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Those include and exclude tables are a bit of a middle path, and the tour explains them well: "Keep it off to contribute only from the spaces, apps, and connectors you include. Turn it on to contribute more broadly and then exclude specific spaces, apps, or connectors." &lt;a href="https://support.atlassian.com/security-and-access-policies/docs/include-or-exclude-in-app-data/" rel="noopener noreferrer"&gt;Atlassian's include or exclude page&lt;/a&gt; adds that platform apps like Rovo and Goals can't be picked one by one. They follow the organization setting, and so does content that isn't inside a space, such as site-wide Confluence configuration. And these tables only handle in-app data, so you can't exclude one space's metadata.&lt;/p&gt;

&lt;h2&gt;
  
  
  One organization at a time: trials, downgrades and the 30-day window
&lt;/h2&gt;

&lt;p&gt;Atlassian's FAQ is plain about it: settings "are determined independently for each Atlassian cloud organization". If your company has a second organization, say one for testing or one that came with an acquisition, it has its own setting and its own defaults.&lt;/p&gt;

&lt;p&gt;Billing changes can move things under you too, so I'd put these on the calendar of whoever owns your Atlassian billing. When you add a new app, Atlassian starts using its data 30 days later, following your existing settings. A new space in an existing app is used from the day you create it. When a trial ends and your highest plan changes, you get 30 days to review before the new settings apply.&lt;/p&gt;

&lt;p&gt;A downgrade doesn't reset your choices to the new plan's defaults, Atlassian says, with one exception. If you leave Enterprise, metadata contribution is turned back on, and you get a notice and 30 days to review. If an upgrade brings new settings, Atlassian says it will tell you.&lt;/p&gt;

&lt;p&gt;Trials are what I'd watch, I think. They're easy to miss. Atlassian's pages don't mention Enterprise trials by name, so this is my reading of the two rules together, and we haven't tested it: trials count toward your highest plan, so an Enterprise trial should give you the metadata switch, and leaving Enterprise turns metadata back on.&lt;/p&gt;

&lt;h2&gt;
  
  
  Atlassian AI data collection after you opt out: 30 and 90 days
&lt;/h2&gt;

&lt;p&gt;Atlassian's page spells out what happens when you opt out, or delete an app or a site. It removes the in-app data within 30 days from the datasets it uses to improve apps for all customers, and the content attributes within 90 days. It will "retrain any models previously trained on that data". It stops collecting new data from that app, and it stops looking for recurring patterns in data you contributed before.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fyi47kf0sr6wcbk3esrll.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fyi47kf0sr6wcbk3esrll.png" title="Illustration, generated locally with ERNIE-Image. After you opt out, Atlassian removes your in-app data from the datasets it uses to improve apps for all customers within 30 days and the content attributes within 90 days, and it will retrain any model previously trained on that data. One robot padlocks a drawer while another empties the next one, and the two clocks stand in for the 30 and the 90 days." alt="Cartoon robots in a blue workshop clearing out green filing cabinets: one drops cards into a violet bin, one on a step ladder padlocks a drawer, and a small robot sits at a desk next to a brain-headed robot stitching a zigzag pattern, under two wall clocks." width="800" height="448"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;But the same page says that data "de-identified and aggregated at a customer level such that it is no longer associated with individual customers (including common patterns), may be retained for up to seven years". So patterns already extracted before your opt-out can probably stay. I couldn't find a page that says how long a retrain takes.&lt;/p&gt;

&lt;p&gt;In &lt;a href="https://community.atlassian.com/forums/Confluence-questions/Data-Contribution-for-AI/qaa-p/3222867" rel="noopener noreferrer"&gt;one April thread&lt;/a&gt; a member read Atlassian's page as saying that models trained during the 30 to 90 days after an opt-out would not be removed. Atlassian's page said then, and still says, that it will "retrain any models previously trained on that data", though it gives no timeline for the retrain. I'd quote Atlassian's page in your own documents. Note that the FAQ says "metadata within 90 days" where the support pages say "content attributes".&lt;/p&gt;

&lt;h2&gt;
  
  
  How to evidence the setting for an audit
&lt;/h2&gt;

&lt;p&gt;I wanted to see this one with our own eyes. None of Atlassian's pages I read says the change is logged, and the audit log's &lt;a href="https://support.atlassian.com/security-and-access-policies/docs/audit-log-activities-database/" rel="noopener noreferrer"&gt;activities database&lt;/a&gt; doesn't list it.&lt;/p&gt;

&lt;p&gt;On our org it is logged. It's quick, too. We saved On at 11:31 and Off at 11:32 (Bucharest time), and the audit log showed both rows, each with the person's name and e-mail, the city, the IP address, and this text:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fgxoaziwy9lhwz8hphbso.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fgxoaziwy9lhwz8hphbso.png" title="Our audit log on 16 November 2026, with the person's details cropped out. Notice that each row states the old and the new value." alt="Two audit log rows from our test org on 16 November 2026: 11:32 Updated in-app data contribution from On to Off, and 11:31 Updated in-app data contribution from Off to On. The location and actor columns are cropped out" width="800" height="170"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Our org has Atlassian Guard Premium, though, and Atlassian's &lt;a href="https://support.atlassian.com/security-and-access-policies/docs/view-audit-log-activities/" rel="noopener noreferrer"&gt;audit log page&lt;/a&gt; says Insights are only available with Atlassian Guard (Standard or Premium) or at least one Enterprise plan: "Without these subscriptions, organization-level logs will not store or display any events." So on a Free, Standard or Premium org without Guard, I don't expect you'll have this row. Your evidence there is the screenshot from step 7, with its date.&lt;/p&gt;

&lt;p&gt;If you do have Guard, export the row with &lt;strong&gt;Export log&lt;/strong&gt; at the top of the audit log page. The banner on our page says new entries can be viewed for 12 months. And don't mix this up with the audit log's own &lt;strong&gt;In-app data settings&lt;/strong&gt;: that one decides whether page titles show up in the audit log and has nothing to do with contribution.&lt;/p&gt;

&lt;h2&gt;
  
  
  Atlassian Rovo training data: the no-training promise covers third-party models only
&lt;/h2&gt;

&lt;p&gt;You may have read Atlassian's older promise that Rovo data isn't used for training, and wondered how both can be true. The old knowledge base article now redirects to &lt;a href="https://support.atlassian.com/rovo/kb/How-Rovo-customer-data-is-handled/" rel="noopener noreferrer"&gt;How Rovo customer data is handled&lt;/a&gt;, and it splits the two cleanly.&lt;/p&gt;

&lt;p&gt;The no-training promise is about third-party model providers. Atlassian says customer data "is never shared with third-party AI providers to train, fine-tune, or improve their AI models". Its FAQ names the providers and says they work under zero data retention agreements. Data contribution is about Atlassian itself. The same article says Atlassian "may use metadata to fine-tune open-source models that operate strictly within Atlassian's infrastructure", subject to these settings.&lt;/p&gt;

&lt;p&gt;The answer did change, though. A Bitbucket thread from January 2026 quotes the trust page as saying "No, Rovo does not use your inputs or outputs to train Atlassian apps and services." That line is gone from the &lt;a href="https://www.atlassian.com/trust/ai" rel="noopener noreferrer"&gt;AI Trust Center&lt;/a&gt; today.&lt;/p&gt;

&lt;p&gt;And turning Rovo off doesn't change any of this. The FAQ says the AI setting and the data contribution setting "are independent of each other". If you've already followed our guide to &lt;a href="https://dev.to/blog/disable-rovo-jira-confluence"&gt;disabling Rovo in Jira and Confluence&lt;/a&gt;, you still need to visit the Data contribution page.&lt;/p&gt;

&lt;h2&gt;
  
  
  Who is left out: Loom, Bitbucket, Data Center and regulated orgs
&lt;/h2&gt;

&lt;p&gt;According to &lt;a href="https://support.atlassian.com/security-and-access-policies/docs/data-contribution-settings-availability/" rel="noopener noreferrer"&gt;Atlassian's availability page&lt;/a&gt;, the settings cover Jira, Confluence and Jira Service Management, plus platform apps such as Rovo and Goals. Atlassian says it doesn't use data from apps that don't have a setting yet, such as Loom or Bitbucket, and the FAQ adds Trello. It also doesn't use Marketplace apps, even Atlassian's own like Jira Service Management Forms. The FAQ says Data Center products aren't part of this change.&lt;/p&gt;

&lt;p&gt;Some organizations are excluded completely: those with customer-managed keys or bring-your-own-key encryption (you hold the encryption key), Atlassian Government Cloud, Atlassian Isolated Cloud, organizations set up for HIPAA (the US health data law), and "certain government and financial services customers". For those, the FAQ says contribution is off "and you won't have the option to turn it on". I couldn't find a definition of which financial services customers that means.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F9oylw7ykqtnpoedezyif.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F9oylw7ykqtnpoedezyif.png" title="Illustration, generated locally with ERNIE-Image. Organizations with customer-managed or bring-your-own-key encryption, Atlassian Government Cloud, Atlassian Isolated Cloud, setups for HIPAA and certain government and financial services customers are excluded outright: contribution is off and there is no option to turn it on. The doorman waves everyone off, including the robot wearing a bank as a hat." alt="A white robot doorman with a red cross on its chest stands with both hands up behind a velvet rope in front of an arched violet door, while robots on both sides hold a golden key, a shield with a star, a server in a glass box, a first-aid kit and a tiny columned bank building on its head." width="800" height="448"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;If one of these applies to you, it keeps metadata out without Enterprise. For the health case, &lt;a href="https://support.atlassian.com/organization-administration/docs/the-hipaa-implementation-guide/" rel="noopener noreferrer"&gt;Atlassian's HIPAA implementation guide&lt;/a&gt; says business associate agreements are available on paid plans from Standard up, not on Free or trial plans. I couldn't confirm that signing one is what gets an org excluded. In one Community thread an Atlassian reply says the excluded orgs are those "that have notified us", and a Free-tier org in that thread was excluded anyway.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I'd do, plan by plan
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Free or Standard.&lt;/strong&gt; Your in-app data is going in today unless someone switched it off. If your Confluence holds HR or legal material, switch it Off and save, then take the screenshot from step 7. If one space is fine to share, add it under &lt;strong&gt;Include&lt;/strong&gt;. Keep the rest out. Remember that whatever you include helps Atlassian's apps for every customer.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Premium.&lt;/strong&gt; Your in-app data started Off. Check it's still Off. Then write down that metadata can't be stopped on your plan, and give that sentence to your security or data protection lead. If they can't accept it, the in-product route is an Enterprise plan on one app.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Enterprise, or a single Enterprise app.&lt;/strong&gt; You have the metadata switch. If your lead's line is "nothing derived from our content leaves us", switch metadata Off. If you're comfortable with de-identified statistics improving search for you and everyone else, leave it On. Record the choice either way. Metadata comes back on if that Enterprise subscription ends.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Several organizations.&lt;/strong&gt; List them all. Check each one, including any test organization.&lt;/p&gt;

&lt;p&gt;If you're also setting Rovo limits on the same admin pages, our walkthrough on &lt;a href="https://dev.to/tutorials/rovo-usage-limit-extra-usage"&gt;setting the Rovo usage limit and extra usage&lt;/a&gt; covers that part.&lt;/p&gt;

&lt;p&gt;Which way did your organization go on this, and did your auditors ask for proof? I'd love to hear how other admins are documenting it.&lt;/p&gt;




&lt;p&gt;Originally published on &lt;a href="https://leanzero.net/blog/atlassian-ai-training-opt-out?utm_source=devto&amp;amp;utm_medium=referral&amp;amp;utm_campaign=crosspost" rel="noopener noreferrer"&gt;leanzero.net&lt;/a&gt;. More Atlassian, Forge and local-AI write-ups at &lt;a href="https://leanzero.net/blog?utm_source=devto&amp;amp;utm_medium=referral&amp;amp;utm_campaign=crosspost" rel="noopener noreferrer"&gt;leanzero.net/blog&lt;/a&gt;, and if you're planning a migration or a Forge app, that's what we do: &lt;a href="https://leanzero.net/services?utm_source=devto&amp;amp;utm_medium=referral&amp;amp;utm_campaign=crosspost" rel="noopener noreferrer"&gt;leanzero.net/services&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>jira</category>
      <category>atlassian</category>
      <category>ai</category>
      <category>privacy</category>
    </item>
    <item>
      <title>Jira Dependency Lag: Working Days Between Tasks</title>
      <dc:creator>Mihai Perdum</dc:creator>
      <pubDate>Mon, 16 Nov 2026 09:04:21 +0000</pubDate>
      <link>https://dev.to/mihai_leanzero/jira-dependency-lag-working-days-between-tasks-ajj</link>
      <guid>https://dev.to/mihai_leanzero/jira-dependency-lag-working-days-between-tasks-ajj</guid>
      <description>&lt;p&gt;A Jira dependency lag doesn't exist in Jira itself: the issue link has no field for a wait. In LeanZero Management, our Gantt and planning app for Jira Cloud, you set the lag on the link. It counts working days, and the timeline keeps to it while you plan. I think that's what people want from a lag: a wait you re-enter by hand every time the blocker slips is just another date to forget. On our demo plan, linking ATLAS-150 to ATLAS-146 with a lag of 2 moved ATLAS-146 from Nov 12 to Tuesday Dec 15, 2026. A drag that tried to start it later was refused. Apply, the button that writes your draft to Jira, wrote the link and then the dates in about 17 seconds, and the lag itself stayed in the app.&lt;/p&gt;

&lt;p&gt;Lag is the waiting time between one task finishing and the next one starting. Think of a sign-off that takes two days, or concrete that has to cure. People ask Atlassian for it. &lt;a href="https://jira.atlassian.com/browse/JRACLOUD-88033" rel="noopener noreferrer"&gt;JRACLOUD-88033&lt;/a&gt;, a request filed against Jira Plans when it was still called Portfolio, asks for more kinds of scheduling dependency, including a way to "set the delay such as number of days before the start of another Epic/Story". It had 56 votes and 33 watchers when we read it on 16 November 2026, and it was still Gathering Interest.&lt;/p&gt;

&lt;p&gt;We make the app, so I'm not neutral. The first section below is what Jira does without it, read from Atlassian's own pages. There's a 91-second video of this walk, published on 3 October 2026. We ran the steps again on 16 November on version 6.19.0. Our pair, ATLAS-150 and ATLAS-146, is not the video's, because they sit a few rows apart, and Step 4's refused drag isn't in the video.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://www.youtube.com/watch?v=tRudIEzbhdk" rel="noopener noreferrer"&gt;https://www.youtube.com/watch?v=tRudIEzbhdk&lt;/a&gt;&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Note&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Before you start&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Jira Cloud with &lt;a href="https://marketplace.atlassian.com/apps/736826281/leanzero-management" rel="noopener noreferrer"&gt;LeanZero Management&lt;/a&gt; installed. It's free on the Marketplace today. We ran this on 6.19.0, released 6 November 2026.&lt;/li&gt;
&lt;li&gt;A plan in the app with two work items that have start and due dates. A plan is the app's view of one or more Jira projects, a board or a JQL query, with every work item's schedule worked out from its dates and links.&lt;/li&gt;
&lt;li&gt;Jira's Link Issues permission on both work items, because the app creates a real Jira link. To write the dates you also need Browse Projects and Edit Issues, and Schedule Issues if your plan uses Jira's own Due date field. The app asks Jira about each of these before it writes.&lt;/li&gt;
&lt;li&gt;A desktop browser. Ours was 1,675 by 1,250 px.&lt;/li&gt;
&lt;li&gt;When you're done, one work item will wait two working days after another, Jira will hold the link and the new dates, and you'll know where the lag itself is kept.&lt;/li&gt;
&lt;/ul&gt;
&lt;/blockquote&gt;

&lt;p&gt;[[steps]]&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Open the plan on the Timeline and show the links&lt;/strong&gt;: every connector is drawn.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Drag from the first bar's end dot onto the second bar&lt;/strong&gt;: a staged link appears.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Click the link and press + twice&lt;/strong&gt;: Lag (working days) reads 2.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Drag the second work item later&lt;/strong&gt;: the app refuses and says why.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Click Apply 2 changes&lt;/strong&gt;: the review lists the dates and Lag 2 working days.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Click Apply 2 changes again&lt;/strong&gt;: the link goes to Jira first, then the dates.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Check Jira and the link menu&lt;/strong&gt;: the link is there and the lag is still 2.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  What a Jira dependency can't say: wait two days
&lt;/h2&gt;

&lt;p&gt;A dependency in Jira is an issue link, usually of the type Blocks: "this work item blocks that one". We read Jira Cloud's REST API description (the published contract for the web interface that programs use to read and change Jira). An issue link has five properties (id, inwardIssue, outwardIssue, self and type), and the request that creates one takes four of the same kind. There's no field where a delay could go, so no app can store a lag in the link itself. I'd like Jira to have that field. It doesn't.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F57x0xlnazzemkrmxrdf1.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F57x0xlnazzemkrmxrdf1.png" title="Illustration, generated locally with ERNIE-Image. A dependency in Jira is an issue link whose record carries five fields, and not one of them can hold a delay. The robots turned it over twice." alt="Three robots around one enormous solid chrome chain link that joins two platforms: the red robot jams a brass hourglass against the seamless metal and it slips, the green robot leans on a wrench with a magnifying glass, a small purple robot peers up at the link. Flat cobalt blue background." width="800" height="448"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Jira's project timeline draws these links. Atlassian's page &lt;a href="https://support.atlassian.com/jira-software-cloud/docs/manage-dependencies-between-epics-on-the-timeline/" rel="noopener noreferrer"&gt;What are dependencies on the timeline?&lt;/a&gt; says the timeline "can only show work items with the Blocks work item link type and link work items from a single space". We searched that page and three other Atlassian pages on timeline and plan dependencies for the words lag and lead time. Neither word appears on any of the four.&lt;/p&gt;

&lt;p&gt;Finish-to-start is the common kind of dependency: the second task can start only when the first one has finished. The Data Center ticket &lt;a href="https://jira.atlassian.com/browse/JSWSERVER-24935" rel="noopener noreferrer"&gt;JSWSERVER-24935&lt;/a&gt;, "To support time lag between dependencies", has asked for a lag on it since April 2021. It has 12 votes.&lt;/p&gt;

&lt;h3&gt;
  
  
  Jira Plans shows lead time but can't set a lag
&lt;/h3&gt;

&lt;p&gt;Jira Plans is the planning tool in Jira's Premium and Enterprise plans. Its dependency page, &lt;a href="https://support.atlassian.com/jira-software-cloud/docs/what-are-dependencies-in-advanced-roadmaps" rel="noopener noreferrer"&gt;What are dependencies in your plan?&lt;/a&gt;, says every link type you show is treated as Blocks, "meaning that the first work item must end before the second one can begin". A dependency turns red when the first work item puts the second at risk.&lt;/p&gt;

&lt;p&gt;The knowledge-base article &lt;a href="https://support.atlassian.com/advanced-roadmaps-for-jira/kb/calculate-lead-time-in-jira-advanced-roadmaps-understanding-dependencies/" rel="noopener noreferrer"&gt;Calculate lead time in Jira Advanced Roadmaps&lt;/a&gt; defines lead time in Plans as "the time between the end time of the first issue and the start time of the second issue", a gap you can see between two dates you typed. Nothing in Plans holds that gap when the first work item slips.&lt;/p&gt;

&lt;p&gt;Plans has no working-day calendar with weekends and holidays yet. &lt;a href="https://jira.atlassian.com/browse/JRACLOUD-88154" rel="noopener noreferrer"&gt;JRACLOUD-88154&lt;/a&gt;, "Include working days and hours on advanced roadmaps", asks for one and had 341 votes on 16 November 2026, up from 331 when we wrote about it in August. And &lt;a href="https://jira.atlassian.com/browse/JRACLOUD-88193" rel="noopener noreferrer"&gt;JRACLOUD-88193&lt;/a&gt;, which asks Plans to shift blocked work when a blocker's end date changes, had 119. I don't think a lag setting makes much sense in Plans before those two land, because a wait only means something if the waiting work moves.&lt;/p&gt;

&lt;p&gt;Outside Jira the words mean something else. Microsoft Project's page &lt;a href="https://support.microsoft.com/en-us/project/add-lead-or-lag-time-to-a-task" rel="noopener noreferrer"&gt;Add lead or lag time to a task&lt;/a&gt; says "When you add lag time, you delay the start time of the successor task", and lead time is an overlap. This tutorial uses them that way.&lt;/p&gt;

&lt;h2&gt;
  
  
  Lag counts working days, not calendar days, on the Jira timeline
&lt;/h2&gt;

&lt;p&gt;LeanZero Management counts a lag in working days: the days your plan treats as workdays, Monday to Friday unless you change it, minus the plan's holidays. Lag 0 means the next working day after the blocker's due date. A lag of N adds N more working days on top.&lt;/p&gt;

&lt;p&gt;Our run shows it across a weekend. ATLAS-150 is due on Thursday 10 December 2026:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Lag on the link&lt;/th&gt;
&lt;th&gt;ATLAS-146 starts&lt;/th&gt;
&lt;th&gt;Why&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;0&lt;/td&gt;
&lt;td&gt;Fri Dec 11&lt;/td&gt;
&lt;td&gt;the next working day&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;1&lt;/td&gt;
&lt;td&gt;Mon Dec 14&lt;/td&gt;
&lt;td&gt;Saturday and Sunday are skipped&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;2&lt;/td&gt;
&lt;td&gt;Tue Dec 15&lt;/td&gt;
&lt;td&gt;one more working day&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;A lag of 2 calendar days would have put the start on Sunday 13 December. I prefer working days. A two-day sign-off doesn't happen over a weekend. We also ran the app's scheduling function directly with a holiday on Friday 12 June 2026 and a blocker due Wednesday 10 June. Lag 2 gave Tuesday 16 June instead of Monday 15 June, so a holiday pushes the start one more day.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 1: Open the plan on the Timeline and show the links
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;In Jira's top bar, open &lt;strong&gt;Apps&lt;/strong&gt; and select &lt;strong&gt;LeanZero Management&lt;/strong&gt;. The Plans page opens.&lt;/li&gt;
&lt;li&gt;In &lt;strong&gt;Find a plan or project key&lt;/strong&gt;, type the plan's name or its Jira project key. We typed ATLAS.&lt;/li&gt;
&lt;li&gt;Select the plan. We opened ATLAS Portfolio Plan, which has 2,349 open work items. It opens on its summary cards.&lt;/li&gt;
&lt;li&gt;Select the &lt;strong&gt;Timeline&lt;/strong&gt; tab, then &lt;strong&gt;Everything&lt;/strong&gt; and &lt;strong&gt;Week&lt;/strong&gt; in the Timeline toolbar. Everything shows one row per work item, and Week makes each day wide enough to drop a link on.&lt;/li&gt;
&lt;li&gt;Open the &lt;strong&gt;⋯&lt;/strong&gt; menu at the right end of the Timeline toolbar.&lt;/li&gt;
&lt;li&gt;Select &lt;strong&gt;Show all connectors&lt;/strong&gt;, which is off by default. Lines now run from each bar to the work items it blocks.&lt;/li&gt;
&lt;li&gt;Scroll until both work items are on screen. Ours were four rows apart.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;You should see both bars and their connector lines. The plan header should read &lt;strong&gt;Saved&lt;/strong&gt; with no Apply button. I always check that first. If an Apply button is already there, the plan holds changes Jira doesn't have yet. Your Apply would write those too, so find out whose they are first.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 2: Draw a finish-to-start dependency between two Jira work items
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Hover over the bar of the work item that must finish first. A small dot appears just past the right end of the bar. We hovered ATLAS-150.&lt;/li&gt;
&lt;li&gt;Press on that dot and drag onto the work item that must wait. Drop on the green dot at the left end of its bar. We dropped on ATLAS-146.&lt;/li&gt;
&lt;li&gt;Release. I aim for the dot, not the bar; it's small, so zoom in if you need to. A dashed connector joins the two bars, and the second bar moves to the next working day after the first one ends. ATLAS-146 went from Nov 12 → Nov 23 to Dec 11 → Dec 22, 2026.&lt;/li&gt;
&lt;li&gt;Look at the plan header. It now shows &lt;strong&gt;Save (2)&lt;/strong&gt; and &lt;strong&gt;Apply 2 changes&lt;/strong&gt;: the new link is one change, and ATLAS-146's dates are the other. Only Apply writes to Jira.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F1nqt20m61r7nr750ro6f.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F1nqt20m61r7nr750ro6f.png" title="Right after the link was drawn. Notice the dashed connector from ATLAS-150 down to ATLAS-146 and the orange draft frame on ATLAS-146, which now finishes Dec 22, 2026. Production install on our demo site, 16 November 2026, version 6.19.0." alt="LeanZero Management timeline after drawing a link: a dashed staged connector from ATLAS-150 to ATLAS-146, and ATLAS-146 now finishing Dec 22, 2026" width="800" height="284"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;A dashed line means the link is staged. Staged means it's in your own draft of the plan and nowhere else: Jira hasn't been told. Nobody else sees it.&lt;/p&gt;

&lt;p&gt;The bar kept its length. ATLAS-146 was 8 working days long before the link. It still is.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 3: Set the lag in working days with + in the link menu
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Click the connector line itself, between the two bars. A small menu opens. Ours read "ATLAS-150 blocks ATLAS-146", with an orange &lt;strong&gt;staged&lt;/strong&gt; tag, then &lt;strong&gt;Lag (working days)&lt;/strong&gt; with − 0 +, and a red &lt;strong&gt;Remove link&lt;/strong&gt; button.&lt;/li&gt;
&lt;li&gt;Click &lt;strong&gt;+&lt;/strong&gt; once. The value goes to 1 and ATLAS-146 moves to Dec 14 → Dec 23.&lt;/li&gt;
&lt;li&gt;Click &lt;strong&gt;+&lt;/strong&gt; again. The value goes to 2 and ATLAS-146 moves to Dec 15 → Dec 24, 2026.&lt;/li&gt;
&lt;li&gt;Press Escape to close the menu.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;You should see the second bar sitting two working days further right than in Step 2. I keep lags small. Two or three days is a real wait; twenty is usually a missing task. The &lt;strong&gt;−&lt;/strong&gt; button stops at 0. There's no negative lag, which would be a lead (the second task starting before the first one finishes). The app's code refuses one with "Lead (negative lag) is not supported yet".&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F3craos11kzxokxpvssz3.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F3craos11kzxokxpvssz3.png" title="The link menu after two clicks on +. Notice the orange staged tag: this link exists only in our draft until Apply. Production install on our demo site, 16 November 2026, version 6.19.0." alt="LeanZero Management link menu reading ATLAS-150 blocks ATLAS-146, staged, Lag (working days) with minus, 2 and plus buttons, and Remove link" width="800" height="350"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;When the lag is saved depends on the link. Ours was staged, so the lag travels with it and is saved when Apply creates the link. On a link that is already in Jira, the app's manual says the lag "is saved to the plan as soon as you set it and everyone who opens the plan sees it". Undo doesn't take that back; you set the old value in the same menu. The dates a lag moves are staged in both cases.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 4: Drag the successor later: what the timeline refuses and why
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Drag the second bar to the right. We dragged ATLAS-146 five calendar days later.&lt;/li&gt;
&lt;li&gt;Release. You should see the bar go back to Dec 15 → Dec 24, and this warning at the top right (with your own keys and date):
&lt;/li&gt;
&lt;/ol&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;ATLAS-146 must start 2 working days after ATLAS-150 finishes — on Dec 15, 2026. Cannot move after: a linked task starts on that day, not later. To start it later, change the link's lag or move ATLAS-150.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The rule is strict. The app's code calls it "'on', never 'on or after'": a linked work item is pinned to the day its links set. So a lag here is an exact start, where Microsoft Project treats it as the &lt;a href="https://support.microsoft.com/en-us/project/link-tasks-in-a-project" rel="noopener noreferrer"&gt;earliest one&lt;/a&gt;. We tested only the later drag; the code refuses an earlier one too. If you want ATLAS-146 to start a week later, raise the lag to 7 or move ATLAS-150. I think that's the right call. A bar that drifts away from its link without saying why is exactly how a plan stops matching the work.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fe2wqtec8gmfrueckc6ys.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fe2wqtec8gmfrueckc6ys.png" title="Illustration, generated locally with ERNIE-Image. A linked work item sits on the day its links set, and the app refuses a drag that would move it off that day. Two robots tried anyway, one each way." alt="Two robots hauling a red block left and a green block right on a long workbench, both pinned at a fixed distance by one rigid bolted steel bar, while a third robot measures the bar with a tape; three red refusal discs float above. Flat sunflower yellow background." width="800" height="448"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fph41trqoosfm4bzq5q61.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fph41trqoosfm4bzq5q61.png" title="The refusal from Step 4, still on screen when we opened the review in Step 5. Notice the message names the date, Dec 15, 2026, and tells you to change the lag or move ATLAS-150. Production install on our demo site, 16 November 2026, version 6.19.0." alt="LeanZero Management Review changes dialog with ATLAS-146 start and due dates struck through and replaced, a New dependencies row ATLAS-150 blocks ATLAS-146 with Lag 2 working days, and next to it the warning that ATLAS-146 must start 2 working days after ATLAS-150 finishes" width="799" height="361"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 5: Read the lag in the Apply review
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;In the plan header, click &lt;strong&gt;Apply 2 changes&lt;/strong&gt;. A dialog called &lt;strong&gt;Review changes&lt;/strong&gt; opens and says "2 changes will be written to Jira".&lt;/li&gt;
&lt;li&gt;Read &lt;strong&gt;What this does to your commitments&lt;/strong&gt;. A commitment is a date the plan promised someone, such as a release. Ours said "No commitment moves."&lt;/li&gt;
&lt;li&gt;Read &lt;strong&gt;Date changes&lt;/strong&gt;. Ours had one row: ATLAS-146, with Start Nov 12, 2026 struck through and Dec 15, 2026 next to it, and Due Nov 23, 2026 struck through and Dec 24, 2026 next to it.&lt;/li&gt;
&lt;li&gt;Read &lt;strong&gt;New dependencies&lt;/strong&gt;. Ours had one row: "ATLAS-150 blocks ATLAS-146" with an orange &lt;strong&gt;Lag 2 working days&lt;/strong&gt; label.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;I read the New dependencies section first. It lists every staged link with its lag in one place. Each row has a tick box, so you can leave a change out. I wouldn't skip this screen. A link with no lag reads "No lag". A changed lag reads as before and after, for example "Lag 2 → 3 working days". The buttons at the bottom are &lt;strong&gt;Discard all&lt;/strong&gt;, &lt;strong&gt;Review with AI&lt;/strong&gt;, &lt;strong&gt;Cancel&lt;/strong&gt; and &lt;strong&gt;Apply 2 changes&lt;/strong&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 6: Apply: the Jira issue link is written first, then the dates
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Click &lt;strong&gt;Apply 2 changes&lt;/strong&gt; at the bottom of the review. A progress dialog runs through "Checking your staged links against Jira", "Saving your reviewed draft", "Checking for conflicts with other saved drafts" and "Writing to Jira".&lt;/li&gt;
&lt;li&gt;Wait for &lt;strong&gt;Applied&lt;/strong&gt;. Ours read "2 of 2 changes written to Jira" with four ticked steps, Starting, Writing, Verifying and Complete, about 17 seconds after the click.&lt;/li&gt;
&lt;li&gt;Click &lt;strong&gt;Done&lt;/strong&gt;. The plan refreshes and the header goes back to &lt;strong&gt;Saved&lt;/strong&gt;.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;I think the order is the most useful thing in this tutorial. The new dates were worked out from the link, so the app writes the links first and starts on the dates once they are all in Jira. If a link fails, no date is written. Jira's own history of ATLAS-146 shows the order. At 04:23:36 (our time, UTC+2) the app added "This work item is blocked by ATLAS-150". Six seconds later it changed the start date from 12 November to 15 December and the due date from 23 November to 24 December. I trust Jira's history more than any dialog, ours included. Check it once.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fhvwwlp45ddopt85mpf6h.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fhvwwlp45ddopt85mpf6h.png" title="The end of the Apply. Notice the Verifying step: the app reads the work items back from Jira before it calls the Apply complete. Production install on our demo site, 16 November 2026, version 6.19.0." alt="LeanZero Management Applied dialog: 2 of 2 changes written to Jira, with Starting, Writing, Verifying and Complete all ticked and a Done button" width="800" height="400"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 7: Check what Jira and the plan hold now
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Open ATLAS-146 in Jira. Under linked work items it says it is blocked by ATLAS-150, and its start and due dates are Dec 15 and Dec 24, 2026.&lt;/li&gt;
&lt;li&gt;Back on the Timeline, click the connector again. The menu reads "ATLAS-150 blocks ATLAS-146" and &lt;strong&gt;Lag (working days)&lt;/strong&gt; 2, without the staged tag.&lt;/li&gt;
&lt;li&gt;Optional: read the work item's history over the Jira REST API to see the order of the writes. Set &lt;code&gt;JIRA_SITE&lt;/code&gt; (your site's address), &lt;code&gt;JIRA_EMAIL&lt;/code&gt; and &lt;code&gt;JIRA_API_TOKEN&lt;/code&gt; (an Atlassian API token) first, and change the key and the date to yours. We ran it against our demo site after the Apply:
&lt;/li&gt;
&lt;/ol&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;curl -s -u &lt;span class="s2"&gt;"$JIRA_EMAIL:$JIRA_API_TOKEN"&lt;/span&gt; &lt;span class="s2"&gt;"$JIRA_SITE/rest/api/3/issue/ATLAS-146/changelog?maxResults=100"&lt;/span&gt; \
  &lt;span class="o"&gt;|&lt;/span&gt; jq -r &lt;span class="s1"&gt;'.values[] | select(.created | startswith("2026-11-16T04:23:3") or startswith("2026-11-16T04:23:4"))
    | "\(.created)  \(.items | map("\(.field): \(.fromString // "-") -&amp;gt; \(.toString // "-")") | join("; "))"'&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;





&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;2026-11-16T04:23:36.001+0200  Link: - -&amp;gt; This work item is blocked by ATLAS-150
2026-11-16T04:23:42.683+0200  Start date: 12/Nov/26 -&amp;gt; 15/Dec/26; duedate: 2026-11-23 00:00:00.0 -&amp;gt; 2026-12-24 00:00:00.0
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;You should see two lines: the link first, the dates a few seconds later. I do both checks the first time. Only the second one tells you the lag survived Apply. Jira now has the link and the dates, and the app has the 2.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fpnvg2dv909va9y42z18r.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fpnvg2dv909va9y42z18r.png" title="The same link menu after Apply. Notice the staged tag is gone and the lag still reads 2: Jira holds the link, the app holds the lag. Production install on our demo site, 16 November 2026, version 6.19.0." alt="LeanZero Management link menu after Apply: ATLAS-150 blocks ATLAS-146, Lag (working days) 2, Remove link, with no staged tag" width="800" height="228"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Where the lag lives, and what deletes it
&lt;/h2&gt;

&lt;p&gt;We keep the lag in the app's own storage on Atlassian's platform, one map per plan, keyed by the Jira link's id. It isn't an issue property and it never reaches Jira; the code puts it as "Lag is app-private (Jira links carry none)". The Apply review shows the lag so you can check it, but what Apply writes is the link and the dates the lag produced.&lt;/p&gt;

&lt;p&gt;If you remove the link with &lt;strong&gt;Remove link&lt;/strong&gt; in the app, the removal is staged like any other change. When you Apply, Jira goes first: the app clears the lag only after Jira confirms the link is gone.&lt;/p&gt;

&lt;p&gt;With two blockers, the app works out each link's date with its own lag and then takes the later one. &lt;a href="https://dev.to/blog/leanzero-management-jira-dependency-moves-dates"&gt;The blog post on how a Jira dependency moves dates&lt;/a&gt; walks through a worked case where a lag of 5 on the earlier blocker decides the start.&lt;/p&gt;

&lt;h2&gt;
  
  
  How the app stores and computes a lag (for Forge developers)
&lt;/h2&gt;

&lt;p&gt;If you build on Forge, Atlassian's platform for apps that run inside Jira, this is the part I'd have wanted to read first.&lt;/p&gt;

&lt;p&gt;LeanZero Management keeps one key per plan, &lt;code&gt;p:{planId}:deps&lt;/code&gt;, in Forge's key-value storage: a map from the Jira link id to a whole number of working days. It sits apart from the app's per-plan copy of Jira data. That copy is rebuilt every time the app re-reads Jira (a re-index or the hourly refresh), and a rebuild would wipe any lag kept on its rows. When a plan loads, each work item gets its incoming links' lags copied onto it as &lt;code&gt;predecessorLags&lt;/code&gt;, so the scheduler never looks the map up while it runs.&lt;/p&gt;

&lt;p&gt;Our first version, on 5 July 2026, keyed the map by the pair of work-item keys, so a link deleted and drawn again got its old lag back. I'd call that a bug. The code comment that now prunes old lags says one would "silently reapply if the link is recreated". The releases of 30 September and 1 October 2026 moved plans to link ids; an old plan is migrated at its next rebuild, and a pair whose link is gone is dropped.&lt;/p&gt;

&lt;p&gt;Creating a link with a lag is two calls in a fixed order: the app creates the link in Jira, reads back the new link's id (Jira's 201 answer has no body), then saves the lag against that id. If the second call fails, the link stays staged with a warning, so you can't end up thinking a lag is saved when it isn't.&lt;/p&gt;

&lt;p&gt;Here's the rule: a successor's earliest start is the latest, over its blockers, of the next working day after the blocker's due date plus that link's lag. The browser computes it for the timeline you see, and the server computes it again to check what you save. A code comment admits the browser's date helper counts one day short, so the browser passes &lt;code&gt;lag + 1&lt;/code&gt;, and a parity test suite holds the two to the same answer. I like that the off-by-one is written down next to the fix. I'd copy this whole pattern for any data Jira has no field for.&lt;/p&gt;

&lt;p&gt;Plan protection uses the same rule. When someone moves a work item's start in Jira to before its blocker allows, the app puts the old start back if the old one keeps the rule, otherwise leaves the date, and either way leaves a comment on the work item saying why. The July commit that added lags made protection lag-aware too, or it would undo a start that's correct because of a lag.&lt;/p&gt;

&lt;h2&gt;
  
  
  Undo the lag before Apply, and put things back after it
&lt;/h2&gt;

&lt;p&gt;Before Apply, nothing is in Jira. I use that a lot: I try a lag, look at it and often throw it away. I'd be careful how. Pressing &lt;strong&gt;−&lt;/strong&gt; back to 0 only takes the lag off: ATLAS-146 goes back to Dec 11 and the link stays staged. &lt;strong&gt;Remove link&lt;/strong&gt; (confirm with &lt;strong&gt;Remove&lt;/strong&gt;) takes the link out of your draft, but the dates it moved can stay changed. &lt;strong&gt;Discard all&lt;/strong&gt; in the review clears both, along with any other unapplied edit. When the plan header reads &lt;strong&gt;Saved&lt;/strong&gt; with no Apply button, nothing is left.&lt;/p&gt;

&lt;p&gt;After Apply, the link and the dates are in Jira. In the app, click &lt;strong&gt;Remove link&lt;/strong&gt; and confirm with &lt;strong&gt;Remove&lt;/strong&gt;, then set the old dates and apply again. We put our demo site back over the Jira REST API with a script instead, because we needed an exact before-and-after record. We set the lag to 0 through the app, deleted the link in Jira, wrote the old dates back and refreshed the plan.&lt;/p&gt;

&lt;p&gt;Our first restore didn't stick. We deleted the link at 04:23:54 and wrote the old dates at 04:23:55. At 04:23:57 the app wrote Dec 15 and Dec 24 back and left a comment on ATLAS-146 headed "Date change reverted". That was plan protection. The plan hadn't re-read Jira since we deleted the link, so it still saw ATLAS-150 as a blocker and put the start back. We refreshed the plan and restored again. Then everything matched: no link, ATLAS-146 back on Nov 12 → Nov 23, and none of the 2,359 schedules we compared had changed after a reload. We deleted the protection comment afterwards.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fj9azo2t50wmlu1u3verr.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fj9azo2t50wmlu1u3verr.png" title="Illustration, generated locally with ERNIE-Image. Our first restore put the old dates back, and two seconds later plan protection stamped the new ones over them, because the plan still saw the deleted link. The robot with the stamp was only following the rules." alt="A blue robot on a stool slides two blank tiles back into a big blank wall-calendar grid under a red circular undo arrow, while a second robot on a taller ladder re-presses the same two tiles with a rubber stamp; a hands-only wall clock ticks one step ahead and an open toolbox of gears sits on the bench. Flat emerald green background." width="800" height="448"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;If you undo an Apply in Jira directly, delete the link first. Then select &lt;strong&gt;Refresh from Jira now&lt;/strong&gt; in the &lt;strong&gt;⋯&lt;/strong&gt; menu at the right end of the plan header (you need edit rights on the plan), wait until the plan stops saying Refreshing from Jira, and only then write the old dates. I'd rather remove the link in the app. Apply then deletes the link before it writes the dates, so protection has nothing stale to act on.&lt;/p&gt;

&lt;h2&gt;
  
  
  If it didn't work
&lt;/h2&gt;

&lt;p&gt;You hover the bar and see no dot. The dot only appears for a work item you can change on a bar wider than a few pixels, and never on a parent such as an epic. Zoom to Week or Day so the bar is wider.&lt;/p&gt;

&lt;p&gt;You release and no link appears. You let go over the bar instead of the green dot at its left end, or the timeline scrolled under the pointer. Dragging near the edge of the chart scrolls it. We missed twice that way before keeping both bars in the middle of the screen.&lt;/p&gt;

&lt;p&gt;"The link ATLAS-150 → ATLAS-146 is in Jira, but its lag of 2 working days could not be saved yet — it shows 0." (with your own keys). Jira took the link and the app couldn't store the lag. The message's own advice: Apply again, or set it in the link's menu.&lt;/p&gt;

&lt;p&gt;"Someone changed the lag ATLAS-150 → ATLAS-146 to 3 working days since you opened it. Nothing was saved." (with your own keys and number). Another planner set the same link's lag first. Reopen the menu and decide which value stands. When two people each stage the same new link with different lags, Apply asks "Two lags for one link" and offers Keep mine or Take theirs.&lt;/p&gt;

&lt;p&gt;An Apply that stops with "Apply stopped" and "No dates were written — they wait for these links". A link failed, so no date was written. Fix what the dialog names, usually a missing Link Issues permission on one of the two work items, and Apply again.&lt;/p&gt;

&lt;h2&gt;
  
  
  What it doesn't do
&lt;/h2&gt;

&lt;p&gt;It models finish-to-start only. There's no start-to-start, finish-to-finish or start-to-finish link, and no lead time. I'd like lead time too. It isn't there yet. A negative lag is refused, and the scheduling engine treats one as 0.&lt;/p&gt;

&lt;p&gt;There's no calendar-days lag. Every lag counts the plan's working days and holidays.&lt;/p&gt;

&lt;p&gt;We didn't test a very large lag live, and we didn't test a link between two plans; a code comment says such a link counts as lag 0.&lt;/p&gt;

&lt;p&gt;You can't see a lag outside the app: Jira's timeline, Plans, filters and exports show the link and the dates, and nothing that explains them. If someone deletes the link in Jira, the next refresh drops the lag with it, and a link drawn again gets a new id and starts with no lag. I'd rather the lag were in Jira. It can't be. I'd put the reason for any lag over a day or two in a comment on the work item.&lt;/p&gt;

&lt;h2&gt;
  
  
  What you have now
&lt;/h2&gt;

&lt;p&gt;[[takeaways]]&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;A finish-to-start dependency between two Jira work items, drawn on the timeline and written to Jira as a Blocks link.&lt;/li&gt;
&lt;li&gt;A lag of 2 working days on that link, counted across the weekend: Friday Dec 11 became Tuesday Dec 15.&lt;/li&gt;
&lt;li&gt;A refused drag, and a message that names Dec 15, 2026 and says what to change instead.&lt;/li&gt;
&lt;li&gt;A review that listed the link with Lag 2 working days, and an Apply that wrote the link before the dates in about 17 seconds.&lt;/li&gt;
&lt;li&gt;Not covered here: two blockers with different lags, holidays on a live plan, and links between plans.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The 2 stays in LeanZero Management, keyed to that one link. The &lt;a href="https://dev.to/tutorials/jira-gantt-dependencies-leanzero-management"&gt;Jira Gantt dependencies tutorial&lt;/a&gt; shows what happens when the blocker slips, the &lt;a href="https://dev.to/tutorials/jira-gantt-chart-critical-path-leanzero-management"&gt;critical path tutorial&lt;/a&gt; shows which links set your plan's finish, the &lt;a href="https://dev.to/blog/jira-timeline-vs-plans-leanzero-management"&gt;comparison of Jira's timeline and Plans&lt;/a&gt; covers what each does when a date moves, and the &lt;a href="https://dev.to/portfolio/leanzero-management#lag"&gt;product page&lt;/a&gt; has the manual's section on lag.&lt;/p&gt;

&lt;p&gt;My advice: put a lag only on a wait that really exists, like an approval or a delivery, and write down why. A lag nobody can explain looks the same on the timeline as a real one, and six months later nobody will remember which is which.&lt;/p&gt;




&lt;p&gt;Originally published on &lt;a href="https://leanzero.net/tutorials/jira-dependency-lag-leanzero-management?utm_source=devto&amp;amp;utm_medium=referral&amp;amp;utm_campaign=crosspost" rel="noopener noreferrer"&gt;leanzero.net&lt;/a&gt;. More Atlassian, Forge and local-AI write-ups at &lt;a href="https://leanzero.net/blog?utm_source=devto&amp;amp;utm_medium=referral&amp;amp;utm_campaign=crosspost" rel="noopener noreferrer"&gt;leanzero.net/blog&lt;/a&gt;, and if you're planning a migration or a Forge app, that's what we do: &lt;a href="https://leanzero.net/services?utm_source=devto&amp;amp;utm_medium=referral&amp;amp;utm_campaign=crosspost" rel="noopener noreferrer"&gt;leanzero.net/services&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>jira</category>
      <category>forge</category>
      <category>atlassian</category>
      <category>projectmanagement</category>
    </item>
    <item>
      <title>Jira field schemes replaced field configuration schemes</title>
      <dc:creator>Mihai Perdum</dc:creator>
      <pubDate>Mon, 16 Nov 2026 06:00:00 +0000</pubDate>
      <link>https://dev.to/mihai_leanzero/jira-field-schemes-replaced-field-configuration-schemes-3dhd</link>
      <guid>https://dev.to/mihai_leanzero/jira-field-schemes-replaced-field-configuration-schemes-3dhd</guid>
      <description>&lt;p&gt;On 20 October 2026, Carol Low from Atlassian answered a question under the Community's &lt;a href="https://community.atlassian.com/forums/Jira-Cloud-Admins-articles/FAQ-amp-Reference-Guide-Transitioning-to-the-New-Field-Schemes/ba-p/3197911" rel="noopener noreferrer"&gt;field schemes FAQ&lt;/a&gt;, a post that had 56,420 views when I checked on 15 November. Sites on continuous release tracks already had field schemes, she wrote, and sites on bundled tracks were scheduled to get them on 10 November. (A release track is the setting that decides when Atlassian's changes reach your site.) So if you run Jira Cloud, your field configurations and field configuration schemes have most likely been converted by now, automatically, in your site's maintenance window.&lt;/p&gt;

&lt;p&gt;We looked at what that conversion left behind on our own test site on 15 November. The new Field schemes page listed 43 field schemes for 59 company-managed spaces, and 24 of them weren't linked to any space. Meanwhile the old field configuration API still answered with HTTP 200, with numbers that no longer match the new model: 740 items in our default configuration against 471 fields in the default field scheme. Writes through the old API came back 404.&lt;/p&gt;

&lt;p&gt;If you look after a Jira site with somewhere between 50 and 2,000 people on it, the part to worry about is the scripts and reports nobody has touched in a year. Scripts that only read won't fail. They'll read stale numbers and carry on.&lt;/p&gt;

&lt;p&gt;A &lt;strong&gt;space&lt;/strong&gt; is Jira's current name for a project, and the REST API still says project. A &lt;strong&gt;work type&lt;/strong&gt; is what older screens called an issue type. Our test site is wolfaenpak.atlassian.net, which is on a Jira plan with a sandbox (Premium or Enterprise) and which we keep for exactly this kind of thing, and the numbers below come from that site after the real migration.&lt;/p&gt;

&lt;h2&gt;
  
  
  What we found on 15 November 2026
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;We had 43 field schemes after the migration. 19 were linked to spaces, one of them only to a space in the trash. The other 24 were linked to none (I'll call those orphans), and all 24 were schemes for service spaces, meaning Jira Service Management spaces, that no longer exist.&lt;/li&gt;
&lt;li&gt;42 of our 59 live company-managed spaces share the Default Field Scheme. The other 17 each have a scheme of their own, and 12 of those were made by our own test-data script through the new API.&lt;/li&gt;
&lt;li&gt;The old read endpoints still answer with HTTP 200, but the numbers don't match the new model: 740 items against 471 fields for the default, 165 against 157 for a service space, 170 against 180 for a test space.&lt;/li&gt;
&lt;li&gt;Asking the old API "which scheme does this space use" gave back an empty list for all 70 spaces, company-managed and team-managed.&lt;/li&gt;
&lt;li&gt;An old write returned 404 "The field configuration was not found." on an id that the old read still answers for. Through the new API, the same change worked once we left one setting out of Atlassian's example.&lt;/li&gt;
&lt;li&gt;Jira refused to delete the default scheme and a scheme in use, and it deleted an orphaned scheme in one call.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  What Jira field schemes replaced: field configurations and field configuration schemes
&lt;/h2&gt;

&lt;p&gt;Until this year, a Jira admin needed two objects to decide which fields a space shows. A &lt;strong&gt;field configuration&lt;/strong&gt; listed the fields and marked each one hidden, optional or required. A &lt;strong&gt;field configuration scheme&lt;/strong&gt; then mapped work types in a space to field configurations, so a Bug could use one configuration and a Story another.&lt;/p&gt;

&lt;p&gt;A &lt;strong&gt;field scheme&lt;/strong&gt; replaces both. Atlassian's &lt;a href="https://support.atlassian.com/jira-cloud-administration/docs/what-are-field-schemes/" rel="noopener noreferrer"&gt;What are field schemes?&lt;/a&gt; page puts it like this: "Field schemes allow you to control which fields appear on your work items and how those fields behave across different spaces." Each space uses exactly one field scheme, and one scheme can serve many spaces, says the page on &lt;a href="https://support.atlassian.com/jira-cloud-administration/docs/associate-a-space-with-a-field-scheme/" rel="noopener noreferrer"&gt;associating a space with a field scheme&lt;/a&gt;. If a field isn't in a space's scheme, it doesn't show up in that space.&lt;/p&gt;

&lt;p&gt;Two older pieces keep their jobs, and it helps to keep them apart in your head. &lt;strong&gt;Field contexts&lt;/strong&gt; now only set the content of a field, meaning default values and the options in a dropdown, and they no longer hide a field from a space. Atlassian's general availability post says each field now gets a global context that can't be deleted. &lt;strong&gt;Screens&lt;/strong&gt;, screen schemes and layouts "remain the final gatekeepers for what users actually see", in the words of that same post.&lt;/p&gt;

&lt;p&gt;So a field has to be in the space's field scheme and on the screen before anyone sees it, and its context decides what it's filled with.&lt;/p&gt;

&lt;p&gt;Per-work-type differences moved inside the scheme. On a field's row you open &lt;strong&gt;More actions&lt;/strong&gt; and pick &lt;strong&gt;Change field behavior by work type&lt;/strong&gt;. A side panel then lets you set &lt;strong&gt;Available on&lt;/strong&gt; and &lt;strong&gt;Required on&lt;/strong&gt; per work type, and replace the field description for one work type, as described in &lt;a href="https://support.atlassian.com/jira-cloud-administration/docs/change-the-way-fields-behave-for-different-work-types/" rel="noopener noreferrer"&gt;Change the way fields behave for different work types&lt;/a&gt;. Below is one of our service-space schemes; look at the two columns on the right.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fw1jy5e0phabfuilnva97.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fw1jy5e0phabfuilnva97.png" title="One migrated field scheme on our test site, 15 November 2026. Notice Available on and Required on per field, and the button at the top right saying how many spaces share it." alt="A field scheme page in Jira Cloud: Jira Service Management Field Configuration Scheme for Project JT, 1 space uses this scheme, 157 fields, with columns Name, Field type, Description, Available on and Required on, most rows reading All work types and No work types" width="799" height="383"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;A new custom field is not added to any field scheme by itself. Atlassian's &lt;a href="https://support.atlassian.com/jira-cloud-administration/docs/create-or-edit-a-field-scheme/" rel="noopener noreferrer"&gt;Create or edit a field scheme&lt;/a&gt; page says you must add it to the relevant schemes before it appears in your spaces. If someone on your team creates a field and tells you "it's not showing", start there.&lt;/p&gt;

&lt;p&gt;Where do you find it? In Jira, select &lt;strong&gt;Settings&lt;/strong&gt;, then &lt;strong&gt;Work items&lt;/strong&gt;, then &lt;strong&gt;Field schemes&lt;/strong&gt; in the sidebar. When we opened the old admin addresses, &lt;code&gt;/secure/admin/ViewFieldLayouts.jspa&lt;/code&gt; and &lt;code&gt;/secure/admin/ViewFieldLayoutSchemes.jspa&lt;/code&gt;, they redirected straight to the Field schemes page, so old bookmarks won't show you the old screens any more.&lt;/p&gt;

&lt;h2&gt;
  
  
  When the field schemes migration reached your site
&lt;/h2&gt;

&lt;p&gt;Atlassian announced general availability on 10 June 2026 in &lt;a href="https://community.atlassian.com/forums/Jira-Cloud-Admins-articles/Announcing-General-Availability-of-Field-Schemes/ba-p/3246894" rel="noopener noreferrer"&gt;Announcing General Availability of Field Schemes&lt;/a&gt;. Continuous release track sites were converted over the following weeks. Bundled release track sites were expected in September, and Carol Low's comment above put them on 10 November. The &lt;a href="https://www.atlassian.com/roadmap/cloud?search=field%20schemes" rel="noopener noreferrer"&gt;Cloud roadmap&lt;/a&gt; lists "Field schemes - GA" as released, 2026 Q3, for Jira and Jira Service Management.&lt;/p&gt;

&lt;p&gt;You didn't get to pick the hour. In a June comment on the FAQ, Atlassian staff wrote that the conversion "runs automatically, in the maintenance window of your site", and that moving the site to bundled release tracks was the one way to control the timing. In her 20 October comment, Carol Low added that a site still on the old screens was most likely on a bundled track.&lt;/p&gt;

&lt;h2&gt;
  
  
  What the field schemes migration created on our Jira Cloud site
&lt;/h2&gt;

&lt;p&gt;The migration's logic is described in the original announcement, &lt;a href="https://community.atlassian.com/forums/Jira-Cloud-Admins-articles/Say-goodbye-to-field-configuration-schemes-and-hello-to-the-future-of-Jira/ba-p/3160315" rel="noopener noreferrer"&gt;Say goodbye to field configuration schemes and hello to the future of Jira&lt;/a&gt; (49,198 views and 48 comments on 15 November). It reads your field configurations, which spaces use them, the fields in those spaces and the work types they apply to, and then your field contexts. Then it creates field schemes so that the fields people see today stay visible, with this warning: "you may have more schemes than you began with fewer spaces associated with each scheme."&lt;/p&gt;

&lt;p&gt;It also tidies up. Fields that aren't used in the linked spaces lose their association. A field counts as used if it holds a value on a work item, sits on a screen, is required, is used in a workflow, or is used in a form. A field that used to be limited to some work types by its context gets the same limit inside the scheme, so it doesn't suddenly appear.&lt;/p&gt;

&lt;p&gt;Here's our site afterwards. We read all 43 schemes through the new API and matched each one to its spaces.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fkl0omlg4glgqru5gqnlc.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fkl0omlg4glgqru5gqnlc.png" title="Our Field schemes page on 15 November 2026, before we deleted one orphan. Notice the 0 spaces rows: schemes left behind by service spaces that were deleted." alt="The Jira Cloud Field schemes list: 43 field schemes, the Default Field Scheme marked Default on 49 spaces with 471 fields, several Showcase field schemes on 1 space each, and Jira Service Management schemes for spaces showing 0 spaces with 170 and 79 fields" width="800" height="467"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;What&lt;/th&gt;
&lt;th&gt;Count on our site&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Field schemes in the new list&lt;/td&gt;
&lt;td&gt;43&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Field configuration schemes still in the old list&lt;/td&gt;
&lt;td&gt;32&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Live company-managed spaces&lt;/td&gt;
&lt;td&gt;59&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Field schemes linked to at least one space&lt;/td&gt;
&lt;td&gt;19&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Field schemes linked to no space&lt;/td&gt;
&lt;td&gt;24&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;After we deleted one orphan (see the cleanup)&lt;/td&gt;
&lt;td&gt;42 schemes, 23 with no space&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Live spaces on the Default Field Scheme&lt;/td&gt;
&lt;td&gt;42 (49 counting spaces in the trash)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Team-managed spaces&lt;/td&gt;
&lt;td&gt;11, listed under no field scheme&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;The 24 orphans are all named "Jira Service Management Field Configuration Scheme for Space" plus a space key, and the spaces behind them are gone. On our site each service space had its own scheme, and deleting the space left the scheme behind. They hold between 69 and 233 fields each. They don't break anything, but they pad the list to 43 rows when 19 are in use.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Futt69mny7szw82opitzt.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Futt69mny7szw82opitzt.png" title="Illustration, generated locally with ERNIE-Image. Deleting a service space left its field configuration scheme behind: 24 orphans still on our site, each holding between 69 and 233 fields, padding the list to 43 rows when 19 are in use. Nothing is broken, the shelf is just full." alt="A cartoon robot on a wooden stepladder holding a feather duster in front of a tall metal shelf stacked with dusty cobwebbed cardboard boxes whose top row is fading away as translucent dashed outlines, while only one short row of glowing yellow boxes is cabled to a small green machine, and a smaller robot shrugs at a separate dusty heap beside a box painted with a yellow star." width="800" height="448"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Spaces in the trash still count. The Default Field Scheme says 49 spaces, and 7 of those 49 are spaces we had deleted that are still in the trash. If you count your spaces from the project list and your schemes from this page, the numbers won't agree while those spaces sit in the trash.&lt;/p&gt;

&lt;p&gt;Team-managed spaces don't appear under any scheme. Their fields are managed inside each space. A public bug, &lt;a href="https://jira.atlassian.com/browse/JRACLOUD-99816" rel="noopener noreferrer"&gt;JRACLOUD-99816&lt;/a&gt;, shows they have a project-level field scheme behind the scenes, but it isn't one you'll see on this page.&lt;/p&gt;

&lt;p&gt;Our numbers are small. We had 32 old schemes and ended up with 43, mostly because of our own test spaces. Your count depends on how you used field contexts. Carol Low wrote in September that if you mostly use global contexts, the migration "shouldn't result in individual schemes", but if you lean on space-specific contexts you can end up with many more. One admin &lt;a href="https://community.atlassian.com/forums/Jira-Cloud-Admins-articles/Announcing-General-Availability-of-Field-Schemes/ba-p/3246894" rel="noopener noreferrer"&gt;wrote in June&lt;/a&gt; that they had 10 field configuration schemes in production. Once the change reached their sandbox, they counted 343 field schemes. So before you plan anything, open the page and read your own count.&lt;/p&gt;

&lt;h2&gt;
  
  
  The 700-field limit now counts per field scheme
&lt;/h2&gt;

&lt;p&gt;Jira Cloud has enforced a limit of 700 fields per space since March 2026, according to &lt;a href="https://support.atlassian.com/jira-cloud-administration/docs/data-limits-and-guardrails/" rel="noopener noreferrer"&gt;Data limits and guardrails in Jira Cloud&lt;/a&gt;. That page still describes the fields as the ones "included in field configuration schemes associated with the space". Atlassian's release note on &lt;a href="https://jirareleases.atlassian.com/announcements/a-simpler-way-to-manage-fields-across-jira" rel="noopener noreferrer"&gt;jirareleases.atlassian.com&lt;/a&gt; says "A limit of 700 fields applies per scheme". Carol Low wrote on 20 October that "Removing a field from a scheme reduces the count, and you don't have to trash it."&lt;/p&gt;

&lt;p&gt;So if you're close to 700, you remove fields from the field scheme. Our default scheme has 471 fields, comfortably under. Removing a field from a scheme doesn't delete its data, says Atlassian's &lt;a href="https://support.atlassian.com/jira-cloud-administration/docs/optimize-your-custom-fields/" rel="noopener noreferrer"&gt;Optimize fields per space&lt;/a&gt; page, but its values aren't accessible until the field is added back.&lt;/p&gt;

&lt;p&gt;The 150-work-type limit you may have seen quoted per scheme now sits on the space, through its work type scheme, according to the same guardrails page.&lt;/p&gt;

&lt;h2&gt;
  
  
  Which scripts break on the old Jira field configuration scheme API
&lt;/h2&gt;

&lt;p&gt;Atlassian's REST reference marks all 15 old operations under &lt;code&gt;/rest/api/3/fieldconfiguration&lt;/code&gt; and &lt;code&gt;/rest/api/3/fieldconfigurationscheme&lt;/code&gt; as deprecated, with "use Field schemes" as the instruction. None of them has a removal date. The &lt;a href="https://community.atlassian.com/forums/Jira-Cloud-Admins-articles/From-Field-Configurations-to-Field-Schemes-Migration-Guide-for-API-Users/ba-p/3245633" rel="noopener noreferrer"&gt;Migration Guide for API Users&lt;/a&gt;, written by Atlassian staff, covers writes. It says nothing about reads, and reads are where we found problems that don't show up as errors.&lt;/p&gt;

&lt;h3&gt;
  
  
  The old reads still answer, with different numbers
&lt;/h3&gt;

&lt;p&gt;We asked both APIs about the same three spaces.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fe9ljab476scjhfm5izqj.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fe9ljab476scjhfm5izqj.png" title="Plotted from our own API reads on 15 November 2026. Notice the default: 740 items in the old list against 471 fields in the scheme people actually use." alt="Bar chart from our test site, 15 November 2026: the old API lists 740, 165 and 170 field configuration items for the default, the JT service space and the TPP test space; their field schemes hold 471, 157 and 180 fields" width="800" height="448"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;For the default, the old API listed 740 items, none hidden, and the Default Field Scheme has 471 fields. 118 of those 740 are field ids that the site's own field list no longer returns. Of the old list's fields that still exist, 152 aren't in the new scheme, which fits the documented tidy-up of unused fields, so I don't read them as a bug. But a report built on the old endpoint now counts fields your users can't see. Required fields matched in all three pairs.&lt;/p&gt;

&lt;p&gt;And the old list of schemes is incomplete. Twelve schemes made on 10 September by our own test-data script, through the new API, aren't in the old list at all. A script that inventories field configuration schemes the old way misses those 12.&lt;/p&gt;

&lt;p&gt;And the old lookup of which scheme a space uses, &lt;code&gt;GET /rest/api/3/fieldconfigurationscheme/project&lt;/code&gt;, returned &lt;code&gt;{"total":0,"values":[]}&lt;/code&gt; for all 70 spaces. That's HTTP 200 with an empty list. We checked it wasn't our query: the same family's mapping call for scheme 10005 still returned its row. None of Atlassian's pages we read documents this behaviour of the old reads, so treat it as what we measured on one site.&lt;/p&gt;

&lt;h3&gt;
  
  
  "The field configuration was not found." on a write
&lt;/h3&gt;

&lt;p&gt;Writes are documented. The migration guide's words are "Embrace the 404: Once a project migrates to the new architecture, legacy update APIs will return a 404 Not Found." On our site it came back on an id that the old API still reads without trouble:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fwm5ljnn1pf8xuwmsbtgk.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fwm5ljnn1pf8xuwmsbtgk.png" title="Our calls on 15 November 2026, re-typeset from our call logs. Notice the first two lines: the same id reads fine and refuses the write with not found." alt="Our API calls against our test site on 15 November 2026, re-typeset from our probe logs: GET on field configuration 10014 returns HTTP 200 with 170 items, PUT on the same id returns HTTP 404 The field configuration was not found, the old project lookup returns total 0, and PUT on the new field schemes parameters endpoint returns HTTP 200 success true" width="799" height="247"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;If a script logs that message, nobody deleted your configuration. Your site has moved to field schemes, and the script needs the new endpoint.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fblpvx6yiwnbdfshmwc2k.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fblpvx6yiwnbdfshmwc2k.png" title="Illustration, generated locally with ERNIE-Image. A write that answers The field configuration was not found does not mean somebody deleted it: the site has moved to field schemes and the script is still calling the old endpoint. The custodian never touched anything." alt="A cartoon robot courier holding a blank envelope scratches its head in front of an old round doorway boarded shut and covered in cobwebs, while a robot custodian shrugs beside it holding a broom and an empty dustpan, and a taller robot gestures warmly from a new open archway with a green carpet runner and a signpost showing an arrow." width="800" height="448"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  The new endpoint, and one trap in the example payload
&lt;/h3&gt;

&lt;p&gt;The replacement lives under &lt;code&gt;/rest/api/3/config/fieldschemes&lt;/code&gt;, 15 operations in the &lt;a href="https://developer.atlassian.com/cloud/jira/platform/swagger-v3.v3.json" rel="noopener noreferrer"&gt;Jira Cloud REST API spec&lt;/a&gt;. They need the Administer Jira permission. All 15 are still flagged experimental, and the group's description still says beta and opt-in, even though the feature is generally available.&lt;/p&gt;

&lt;p&gt;To change a field's description in one scheme we called &lt;code&gt;PUT /rest/api/3/config/fieldschemes/fields/parameters&lt;/code&gt;. Our first try copied the spec's example, which includes a &lt;code&gt;rendererType&lt;/code&gt;. On the system field labels it failed with HTTP 400 and "Field labels cannot have renderer type changed", although we sent the value it already had. Sending only the description worked. This is the body we sent:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight json"&gt;&lt;code&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="nl"&gt;"labels"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="nl"&gt;"parameters"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="nl"&gt;"description"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"lz-probe-20261115 new-api write"&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nl"&gt;"schemeIds"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="mi"&gt;2&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The call returned HTTP 200 with &lt;code&gt;"success": true&lt;/code&gt;, the description changed in scheme 2 only, and the default scheme kept its empty description. We put the old description back with the same call. Note that the endpoint reports results per field and per scheme, so a script should read &lt;code&gt;success&lt;/code&gt; in the body as well as the status code.&lt;/p&gt;

&lt;h2&gt;
  
  
  What to tell app vendors and script owners
&lt;/h2&gt;

&lt;p&gt;Atlassian's own line is that "scripts relying on legacy field configuration APIs will need to be updated", while automation rules keep working. I'd hand your script owners this list:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Search your scripts for &lt;code&gt;fieldconfiguration&lt;/code&gt; and &lt;code&gt;fieldconfigurationscheme&lt;/code&gt;. A hit that only reads is the risky one, because it won't error.&lt;/li&gt;
&lt;li&gt;Change project lookups to &lt;code&gt;GET /rest/api/3/config/fieldschemes/projects?projectId=...&lt;/code&gt;. Atlassian's spec calls this "a temporary API" for the transition, and like the rest of the new group it's flagged experimental, so keep an eye on it.&lt;/li&gt;
&lt;li&gt;Treat a 404 from an old write as "this site has moved" and switch the call over.&lt;/li&gt;
&lt;li&gt;Leave &lt;code&gt;rendererType&lt;/code&gt; out of parameter updates unless you mean to change it.&lt;/li&gt;
&lt;li&gt;Ask each app vendor whether they've moved off the old field configuration API.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;On vendors, I found one notice. Adaptavist's &lt;a href="https://docs.adaptavist.com/sr4jc/latest/features/scripted-fields/create-and-modify-scripted-fields" rel="noopener noreferrer"&gt;ScriptRunner for Jira Cloud scripted fields page&lt;/a&gt; says new custom fields are no longer linked to all schemes automatically, and that field configurations are merging into field schemes. I couldn't find a notice from Appfire or other vendors, so it's worth asking them directly.&lt;/p&gt;

&lt;p&gt;If you're also creating spaces by script, Atlassian's &lt;a href="https://community.developer.atlassian.com/t/rfc-121-transition-project-create-apis-to-the-new-field-scheme-model/97660" rel="noopener noreferrer"&gt;RFC-121&lt;/a&gt; says the field configuration settings in the create-project call will be deprecated too.&lt;/p&gt;

&lt;h2&gt;
  
  
  Field schemes cleanup: orphaned schemes, the shared default and sprawl
&lt;/h2&gt;

&lt;p&gt;We ran this cleanup on our site in the order below, and you'll need to be a Jira admin for it. We deleted through the REST API with an API token. On Premium and Enterprise, the Site optimizer can also delete an unassociated scheme from the screen; we didn't test the page's own Actions menu for a delete option.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;In &lt;strong&gt;Settings &amp;gt; Work items &amp;gt; Field schemes&lt;/strong&gt;, read the &lt;strong&gt;Spaces&lt;/strong&gt; column. A row with 0 spaces is an orphan candidate; check its name and description first, because a scheme someone built and hasn't linked yet also shows 0. Ours had 24, all named after deleted service spaces.&lt;/li&gt;
&lt;li&gt;Remember the trash. A deleted space that's still in the trash keeps its scheme linked, so that scheme won't show 0 spaces while the space sits there.&lt;/li&gt;
&lt;li&gt;Find the orphan's id with &lt;code&gt;GET /rest/api/3/config/fieldschemes&lt;/code&gt; (each entry has &lt;code&gt;id&lt;/code&gt;, &lt;code&gt;name&lt;/code&gt; and a link to its spaces), then delete it with &lt;code&gt;DELETE /rest/api/3/config/fieldschemes/{id}&lt;/code&gt;. Ours returned HTTP 200 and &lt;code&gt;{"id":"640","deleted":true}&lt;/code&gt;, and the list dropped from 43 to 42.&lt;/li&gt;
&lt;li&gt;Expect two refusals. A scheme a space uses returns HTTP 409 "Scheme is in use and cannot be deleted". The Default Field Scheme returns HTTP 400 "System schemes cannot be deleted".&lt;/li&gt;
&lt;li&gt;Open the Default Field Scheme and check its field count against 700. Most of your spaces probably share it, so a field you add there counts for each of them.&lt;/li&gt;
&lt;li&gt;Add any custom field created since the migration to the schemes that need it, because Jira won't do it for you.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;When you're done, the Field schemes page shows no 0-space rows you can't explain, and the default scheme's field count is under 700.&lt;/p&gt;

&lt;p&gt;When should you merge schemes? If two schemes hold the same fields and only differ by a few required fields, you can now express that inside one scheme with &lt;strong&gt;Required on&lt;/strong&gt;. Atlassian's FAQ says a large number of schemes won't slow your site down, while too many fields in one scheme can. So I'd consolidate for the people maintaining it, and trim fields for the limit.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I'd do this week
&lt;/h2&gt;

&lt;p&gt;Open your Field schemes page and write down your total schemes, the schemes with 0 spaces, and the fields in the default. Then send the five-point list above to the people who maintain your scripts and apps, before a monthly report quietly goes wrong. Do the scripts first, and leave the cleanup for a calm afternoon.&lt;/p&gt;

&lt;p&gt;There's one thing I couldn't confirm: which Jira plans field schemes apply to. None of the Atlassian pages I read states a plan, and the only plan-limited piece I found is the Site optimizer (Premium and Enterprise), so check your own site before you promise anything to your team. If you're moving from Data Center, Atlassian says the migration assistant converts field configurations when the target site already has field schemes, and our note on the &lt;a href="https://leanzero.net/blog/jcma-couldnt-export-custom-field-config-scheme?utm_source=devto&amp;amp;utm_medium=referral&amp;amp;utm_campaign=crosspost" rel="noopener noreferrer"&gt;Jira Cloud Migration Assistant export error for custom field config schemes&lt;/a&gt; covers one place that goes wrong. For the admin time all this takes, our piece on &lt;a href="https://leanzero.net/blog/how-many-jira-administrators?utm_source=devto&amp;amp;utm_medium=referral&amp;amp;utm_campaign=crosspost" rel="noopener noreferrer"&gt;how many Jira administrators you need&lt;/a&gt; has the numbers, and the &lt;a href="https://leanzero.net/tutorials/jira-formula-fields-calculated-field-cloud?utm_source=devto&amp;amp;utm_medium=referral&amp;amp;utm_campaign=crosspost" rel="noopener noreferrer"&gt;formula fields tutorial&lt;/a&gt; covers the limits of formula fields themselves.&lt;/p&gt;

&lt;p&gt;If you've been through this on a bigger site, I'd love to hear your scheme count before and after, and whether any of your apps tripped over the old API.&lt;/p&gt;




&lt;p&gt;Originally published on &lt;a href="https://leanzero.net/blog/jira-field-schemes?utm_source=devto&amp;amp;utm_medium=referral&amp;amp;utm_campaign=crosspost" rel="noopener noreferrer"&gt;leanzero.net&lt;/a&gt;. More Atlassian, Forge and local-AI write-ups at &lt;a href="https://leanzero.net/blog?utm_source=devto&amp;amp;utm_medium=referral&amp;amp;utm_campaign=crosspost" rel="noopener noreferrer"&gt;leanzero.net/blog&lt;/a&gt;, and if you're planning a migration or a Forge app, that's what we do: &lt;a href="https://leanzero.net/services?utm_source=devto&amp;amp;utm_medium=referral&amp;amp;utm_campaign=crosspost" rel="noopener noreferrer"&gt;leanzero.net/services&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>jira</category>
      <category>atlassian</category>
    </item>
    <item>
      <title>Jira Sandbox to Production: What the Deploy Beta Checks</title>
      <dc:creator>Mihai Perdum</dc:creator>
      <pubDate>Sun, 15 Nov 2026 05:59:21 +0000</pubDate>
      <link>https://dev.to/mihai_leanzero/jira-sandbox-to-production-what-the-deploy-beta-checks-2ea6</link>
      <guid>https://dev.to/mihai_leanzero/jira-sandbox-to-production-what-the-deploy-beta-checks-2ea6</guid>
      <description>&lt;p&gt;On 6 July 2026 Atlassian's product manager for sandboxes posted on the Community that Jira and Jira Service Management admins could deploy configuration changes from a sandbox to production, as an open beta. By 14 November that post had 8,965 views. Atlassian's docs say it deploys workflows, fields, screens, schemes, boards, filters and automation rules to production without an app, for org admins on Premium or Enterprise. It's one-way, though: the review screen says deployed changes "can't be reversed".&lt;/p&gt;

&lt;p&gt;We tried it on 14 November on our own organization, and we stopped at the review screen, before the deploy button. We picked 4 changes, the tool counted 110 items to deploy, and 12 of them showed errors. The one warning we read named a field called Story Points that exists on both of our sites, and the fix the screen suggests is a full copy of production into the sandbox, which overwrites everything in it.&lt;/p&gt;

&lt;p&gt;A sandbox, if you haven't opened one yet, is a separate Jira site linked to your production site, for testing changes before your users see them. Ours is Premium, with production on wolfaenpak.atlassian.net and the sandbox on leanzero-demo.atlassian.net. Below are the steps with our real screens and timings, then Atlassian's own list of what moves and what doesn't. If you'd rather copy whole projects between two Cloud sites, that's a different job, covered in &lt;a href="https://leanzero.net/tutorials/merge-two-jira-cloud-instances?utm_source=devto&amp;amp;utm_medium=referral&amp;amp;utm_campaign=crosspost" rel="noopener noreferrer"&gt;merge two Jira Cloud instances&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  What we found when we tried it on 14 November 2026
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;The first scan of our sandbox, which had never been copied from production, took about 13 minutes and listed 764 differences.&lt;/li&gt;
&lt;li&gt;Selecting 4 items selected 16, and validation then counted 110, most of them fields that our project's field scheme depends on.&lt;/li&gt;
&lt;li&gt;12 of the 110 showed errors, our project among them, so the part we cared about couldn't go.&lt;/li&gt;
&lt;li&gt;We didn't start the deployment. Production had 0 new fields, statuses, workflows, filters or projects afterwards, and the moved-or-not table below is Atlassian's documentation.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Before you start: role, plan and a fresh copy
&lt;/h2&gt;

&lt;blockquote&gt;
&lt;p&gt;Note&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Prerequisites&lt;/strong&gt; — you need all of this before step 1.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;&lt;strong&gt;Role:&lt;/strong&gt; organization admin. Site admins can't deploy, and a public suggestion to change that, &lt;a href="https://jira.atlassian.com/browse/CLOUD-13068" rel="noopener noreferrer"&gt;CLOUD-13068&lt;/a&gt;, is open.&lt;br&gt;
&lt;strong&gt;Plan:&lt;/strong&gt; Jira or Jira Service Management on Premium or Enterprise. Premium includes 1 sandbox per app and Enterprise up to 5 (&lt;a href="https://support.atlassian.com/organization-administration/docs/understand-billing-for-sandboxes/" rel="noopener noreferrer"&gt;Understand billing for sandboxes&lt;/a&gt;).&lt;br&gt;
&lt;strong&gt;Cloud only,&lt;/strong&gt; and not Atlassian Government Cloud, where deployment isn't available (&lt;a href="https://support.atlassian.com/organization-administration/docs/deploy-configuration-changes-from-a-sandbox/" rel="noopener noreferrer"&gt;Deploy configuration changes from a sandbox&lt;/a&gt;).&lt;br&gt;
&lt;strong&gt;Company-managed projects only.&lt;/strong&gt; Team-managed projects aren't supported (&lt;a href="https://support.atlassian.com/organization-administration/docs/data-deployed-from-sandboxes/" rel="noopener noreferrer"&gt;Data deployed from sandboxes&lt;/a&gt;).&lt;br&gt;
&lt;strong&gt;A recent full copy of production in the sandbox.&lt;/strong&gt; Without one the scan still runs, as ours did, but Atlassian says deployments only work accurately after it. Step 1 checks this.&lt;/p&gt;

&lt;p&gt;When you're done you'll have a validated deployment, and you'll know which items will reach production and which ones need fixing first.&lt;/p&gt;
&lt;h2&gt;
  
  
  The procedure at a glance
&lt;/h2&gt;

&lt;p&gt;[[steps]]&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Check the sandbox's last copy&lt;/strong&gt; — compare &lt;strong&gt;Last data copy&lt;/strong&gt; with the cut-off dates and refresh if it's older.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Make your changes in the sandbox&lt;/strong&gt; — in a company-managed project, with names you can search for.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Create a deployment&lt;/strong&gt; — pick your production site and let the scan run.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Find your changes&lt;/strong&gt; — search the scan and rescan if something is missing.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Select and check dependencies&lt;/strong&gt; — tick your items and look at what the tool adds.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Review and read every error&lt;/strong&gt; — open the side panel of each item with an error.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Start the deployment and read the report&lt;/strong&gt; — then confirm one item in production.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;You should see the same seven stages in the admin screens, in this order.&lt;/p&gt;
&lt;h2&gt;
  
  
  Step 1: Check the Jira sandbox's last refresh (its copy of production data)
&lt;/h2&gt;

&lt;p&gt;Atlassian says deployments only work accurately after a recent full copy. Without one, items made separately on each site look new: in our never-copied sandbox 752 of the 764 differences were Added, and Story Points was flagged as a same-name duplicate. It still scanned, so the copy isn't required to start, only to get a clean result.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;In &lt;a href="https://admin.atlassian.com" rel="noopener noreferrer"&gt;admin.atlassian.com&lt;/a&gt;, select &lt;strong&gt;Apps&lt;/strong&gt;, then &lt;strong&gt;Sandboxes&lt;/strong&gt;. The page lists your sandboxes with a &lt;strong&gt;Last data copy&lt;/strong&gt; column.&lt;/li&gt;
&lt;li&gt;Read &lt;strong&gt;Last data copy&lt;/strong&gt; on your Jira sandbox's row. Ours said &lt;strong&gt;Never copied&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;Compare it with the cut-off dates on the banner of a new deployment (step 3 shows where). Ours asked for a copy "on or after February 7, 2026 for deploying Jira configurations (excluding automations), or May 17, 2026 for deploying Jira Service Management configurations and any automation rules." Atlassian's &lt;a href="https://support.atlassian.com/organization-administration/docs/recommended-workflow-for-deployments/" rel="noopener noreferrer"&gt;recommended workflow page&lt;/a&gt; says May 7 for the second date. If your copy is dated between 7 and 17 May 2026, the docs accept it but the screen doesn't, so make a new one.&lt;/li&gt;
&lt;li&gt;Optional: to refresh, select &lt;strong&gt;More actions (…)&lt;/strong&gt; on the row, then &lt;strong&gt;Copy production data&lt;/strong&gt;. The copy options open.&lt;/li&gt;
&lt;li&gt;Optional: choose &lt;strong&gt;All projects&lt;/strong&gt;, then &lt;strong&gt;Copy data with attachments&lt;/strong&gt; or &lt;strong&gt;Copy data without attachments&lt;/strong&gt;. A summary of the data to copy appears.&lt;/li&gt;
&lt;li&gt;Optional: review the summary and select &lt;strong&gt;Copy data&lt;/strong&gt;. The copy starts.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;You should see a &lt;strong&gt;Last data copy&lt;/strong&gt; date after the cut-off. Ours didn't have one. A copy replaces everything in the sandbox, and a full copy into one Jira-family sandbox also overwrites your Jira Service Management and Product Discovery sandboxes, if you have them (&lt;a href="https://support.atlassian.com/organization-administration/docs/jira-family-and-sandboxes/" rel="noopener noreferrer"&gt;How do sandboxes work for the Jira family of apps?&lt;/a&gt;). So refresh first, then build.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fnfcj7gm39s4nxw8vpps3.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fnfcj7gm39s4nxw8vpps3.png" title="The banner at the top of a new deployment, 14 November 2026. Notice the two dates, and that automation rules follow the later one." alt="Deployment page banner: Deployments only work accurately if you've copied production data into your sandbox using Copy All Projects on or after February 7, 2026 for Jira configurations, or May 17, 2026 for Jira Service Management configurations and automation rules" width="799" height="235"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;We skipped the copy on purpose. Our sandbox holds the demo data for our own apps, and a copy would have wiped it. That choice probably explains what happened in step 6, so with a fresh sandbox you should get further than we did.&lt;/p&gt;
&lt;h2&gt;
  
  
  Step 2: Make your changes in the sandbox
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Open your sandbox site and make the configuration changes you want to ship, in a company-managed project.&lt;/li&gt;
&lt;li&gt;Give them names you can search for later. We started every name with SBX, a prefix we made up, so we could find each item, and later delete it, by name.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Our test was a company-managed project called SBX Deploy Test. It got its own workflow with a new status, SBX Review, and a validator that makes a field required before review. We added a dropdown field, a screen, a filter shared with the project, a project role and an automation rule that comments on new work items.&lt;/p&gt;
&lt;h2&gt;
  
  
  Step 3: Create a Jira sandbox deployment and choose production
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;On the &lt;strong&gt;Sandboxes&lt;/strong&gt; page, select &lt;strong&gt;More actions (…)&lt;/strong&gt; on your Jira sandbox's row. The menu shows &lt;strong&gt;Create a deployment&lt;/strong&gt; with a &lt;strong&gt;Beta&lt;/strong&gt; label.&lt;/li&gt;
&lt;li&gt;Select &lt;strong&gt;Create a deployment&lt;/strong&gt;. A deployment page opens, named after the date and time. Ours was "November 14, 2026_11:21:37_Jira_Deployment".&lt;/li&gt;
&lt;li&gt;Under &lt;strong&gt;Destination&lt;/strong&gt;, select &lt;strong&gt;Select destination&lt;/strong&gt; and pick your production site.&lt;/li&gt;
&lt;li&gt;Select &lt;strong&gt;Confirm&lt;/strong&gt;. A progress bar appears under &lt;strong&gt;Scanning your data&lt;/strong&gt;.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;You can leave the page while it scans. &lt;strong&gt;View deployment log&lt;/strong&gt; in the same menu shows the status "scanning data". Our first scan, run before step 2, took about 13 minutes and listed 764 differences, 752 added and 12 modified. With a sandbox that has never been copied, nearly everything looks new.&lt;/p&gt;
&lt;h2&gt;
  
  
  Step 4: Find your changes in the scan
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;In &lt;strong&gt;Search entity name&lt;/strong&gt;, type a word from your changes. We typed SBX.&lt;/li&gt;
&lt;li&gt;Read the groups. Each one is an item type with a count (Atlassian calls each configuration item an entity, and a board shows up as Rapid View). A green plus means added and a pencil means modified.&lt;/li&gt;
&lt;li&gt;If a change is missing, select &lt;strong&gt;Scan again&lt;/strong&gt;, then &lt;strong&gt;Begin scan&lt;/strong&gt; in the dialog. A rescan clears your selection.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Our changes came after the first scan, so we rescanned. It took 5.4 minutes, the total rose from 764 to 785, and the search found 19 SBX items, all of them Added. The automation rule was there too.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F1rlu2mmtgwd1dd2cslf6.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F1rlu2mmtgwd1dd2cslf6.png" title="The rescan, filtered to our test items. Notice the Automation Rule Config group at the top, and that every item carries the green Added mark." alt="The deployment scan filtered by SBX: 19 results, all Added, grouped as Automation Rule Config, Field, Filter, Issue Status, Project, Project Role, Rapid View, Screen, Screen Scheme and Work Type Scheme" width="800" height="442"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h2&gt;
  
  
  Step 5: Select your changes and check the dependencies
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Tick the items you want to deploy. We ticked 4: the project, the filter, the project role and the automation rule.&lt;/li&gt;
&lt;li&gt;Select the &lt;strong&gt;Selected&lt;/strong&gt; tab. Ours showed 16, because the tool ticks what those 4 depend on.&lt;/li&gt;
&lt;li&gt;Optional: select an item's name to open its side panel. &lt;strong&gt;Dependencies&lt;/strong&gt; lists what it needs and &lt;strong&gt;Used by&lt;/strong&gt; lists what needs it.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;So the selection grows fast, from 4 to 16 in our case. You should see your own items plus the ones they need. The help page puts it simply: "we automatically select any configuration dependencies".&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fezkh29qavn4coaujnlo1.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fezkh29qavn4coaujnlo1.png" title="Illustration, generated locally with ERNIE-Image. Jira selects a project's configuration dependencies automatically, and a field scheme depends on every field in it. One cube on a trolley, two cheerful robots, and a second trolley already overflowing." alt="Two cartoon robots beside a single cobalt cube on a hand trolley; cables run from that one cube to dozens of red, yellow and green cubes, a second trolley overflows with yellow cubes, and a clipboard shows a tree of circles." width="800" height="448"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h2&gt;
  
  
  Step 6: Review the deployment and read every error
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Select &lt;strong&gt;Review Deployment&lt;/strong&gt;. A progress bar shows &lt;strong&gt;Validating entities&lt;/strong&gt;. Ours took about 2.5 minutes.&lt;/li&gt;
&lt;li&gt;Read the summary at the top. Ours said "12 errors found", with &lt;strong&gt;All 110&lt;/strong&gt;, &lt;strong&gt;Ready for deployment 98&lt;/strong&gt; and &lt;strong&gt;Contains errors 12&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;Select &lt;strong&gt;Contains errors&lt;/strong&gt;. Each item with a problem carries a red &lt;strong&gt;Contain errors&lt;/strong&gt; badge.&lt;/li&gt;
&lt;li&gt;Select an item's name. The side panel's &lt;strong&gt;Overview&lt;/strong&gt; tab explains the error.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The jump from 16 to 110 happens here. Validation followed the chain one level further. Our project uses the default field scheme, whose panel lists 74 dependencies, and the review counted 72 fields, so most of the jump is likely that scheme.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fq226gmngvpwy4phjnt2y.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fq226gmngvpwy4phjnt2y.png" title="The review screen, 14 November 2026. Notice the sentence above the red box, and the Field group: 72 fields came along with one project." alt="Review changes to be deployed: once deployed, the changes in the destination can't be reversed; 12 errors found; All 110, Ready for deployment 98, Contains errors 12" width="800" height="346"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;The 12 items with errors were our automation rule, the field Story Points, the default field configuration, the default field layout scheme, the default field scheme, the default priority scheme, our project (106 dependencies), its board, the Story work type, the project's work type scheme, our workflow and our workflow scheme. We opened the panel for Story Points. It showed a red "Error in dependent entities" box and a yellow warning:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Another Field with the same name was created on the destination after the sandbox was last refreshed. Deploying this entity may create a duplicate on the destination, which you can manually clean up post the deployment.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fkqbil4v2hqt35k8xwvha.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fkqbil4v2hqt35k8xwvha.png" title="The side panel for Story Points. Notice the two boxes: red for an error in its dependencies, yellow for the name clash with production." alt="Story Points side panel: Error in dependent entities, and Another entity with the same name exists on destination, with the advice to perform a copy all spaces operation into the sandbox from production" width="800" height="530"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;To check a name clash yourself, look the field up by name on both sites with the REST API (use your own site and credentials):&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;curl -s -u you@example.com:&lt;span class="nv"&gt;$API_TOKEN&lt;/span&gt; &lt;span class="s2"&gt;"https://your-site.atlassian.net/rest/api/3/field/search?query=Story%20Points"&lt;/span&gt; &lt;span class="o"&gt;|&lt;/span&gt; jq -r &lt;span class="s1"&gt;'.values[] | "\(.id)  \(.name)"'&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;You should see each field's id and name. Run against our production site and then our sandbox on 14 November, it printed:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;== wolfaenpak
customfield_10054  Story Points
== leanzero-demo
customfield_10077  Story Points
customfield_10153  Story Points
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;So Story Points really is separate fields with one name on our sites, and our sandbox even has two of them, because it was never copied from production. We didn't open the other 11 panels, so we can't tell you which item holds the first error. A name clash like this one is probably the cause, and the panel's own advice is a full copy from production.&lt;/p&gt;

&lt;p&gt;The red box on the review screen offers &lt;strong&gt;Remove and revalidate&lt;/strong&gt;, which it says removes the 12 items and checks the rest again. When we selected it, we landed back on the selection screen with all 110 still selected. Removing them would have dropped the project and the rule we came to test, and still sent the other 71 fields. So we stopped. Then we deleted our test items from the sandbox.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 7: Start the deployment and download the report
&lt;/h2&gt;

&lt;p&gt;We didn't run this step, so here's Atlassian's procedure from &lt;a href="https://support.atlassian.com/organization-administration/docs/deploy-configuration-changes-from-a-sandbox/" rel="noopener noreferrer"&gt;Deploy configuration changes from a sandbox&lt;/a&gt;.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;On the review screen, once no errors are left, select &lt;strong&gt;Start Deployment&lt;/strong&gt;. The deployment runs.&lt;/li&gt;
&lt;li&gt;On the &lt;strong&gt;Sandboxes&lt;/strong&gt; page, select &lt;strong&gt;More actions (…)&lt;/strong&gt; on the sandbox row, then &lt;strong&gt;View deployment log&lt;/strong&gt;. Your deployment is listed with its status.&lt;/li&gt;
&lt;li&gt;Select &lt;strong&gt;More actions (…)&lt;/strong&gt; on your deployment, then &lt;strong&gt;View details&lt;/strong&gt;. The details page opens.&lt;/li&gt;
&lt;li&gt;Select &lt;strong&gt;Download report&lt;/strong&gt;. You get &lt;strong&gt;Summary.csv&lt;/strong&gt; and &lt;strong&gt;RequiresAttention.csv&lt;/strong&gt;.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Atlassian asks you to "go through" both files "to check if there are any failures that you might want to address". Then open one of the deployed items in production, a workflow or a field, to confirm it's there. The log page says its details stay available for 14 days.&lt;/p&gt;

&lt;h2&gt;
  
  
  What moves from a Jira sandbox to production, and what stays behind
&lt;/h2&gt;

&lt;p&gt;Atlassian's &lt;a href="https://support.atlassian.com/organization-administration/docs/data-deployed-from-sandboxes/" rel="noopener noreferrer"&gt;Data deployed from sandboxes&lt;/a&gt; page lists what deploys and gives a workaround for each gap. I've put the Jira part in one table. We stopped at review, so none of these rows is measured by us, and I'd treat them as Atlassian's promise until you've seen your own report.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Change in the sandbox&lt;/th&gt;
&lt;th&gt;Deploys?&lt;/th&gt;
&lt;th&gt;What Atlassian says to do&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;New custom field and its context, field scheme, screen, screen scheme, workflow, workflow scheme, status, priority, work type, work type scheme, project role, board, notification or permission scheme&lt;/td&gt;
&lt;td&gt;Yes&lt;/td&gt;
&lt;td&gt;A scheme's link to an existing project changes only if you also select the project&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;New company-managed project&lt;/td&gt;
&lt;td&gt;Yes, its configuration, no work items&lt;/td&gt;
&lt;td&gt;The beta announcement: "This does not include issue data"&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;New automation rule&lt;/td&gt;
&lt;td&gt;Yes, but connections don't&lt;/td&gt;
&lt;td&gt;"Manually reconfigure connections in automations in the destination"&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;New filter&lt;/td&gt;
&lt;td&gt;Yes, as private&lt;/td&gt;
&lt;td&gt;"Manually change the permissions of the filter in the destination"&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Removing a status from a workflow&lt;/td&gt;
&lt;td&gt;No&lt;/td&gt;
&lt;td&gt;Remove it in production by hand&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Removing a field option or a default value&lt;/td&gt;
&lt;td&gt;No&lt;/td&gt;
&lt;td&gt;Remove it in production by hand&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Changing a field's type&lt;/td&gt;
&lt;td&gt;No&lt;/td&gt;
&lt;td&gt;Change it in production by hand&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Renaming a project or changing its key&lt;/td&gt;
&lt;td&gt;No&lt;/td&gt;
&lt;td&gt;Change it in production by hand&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Work type icons and other media&lt;/td&gt;
&lt;td&gt;No&lt;/td&gt;
&lt;td&gt;Upload them in production&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Anything in a team-managed project&lt;/td&gt;
&lt;td&gt;No&lt;/td&gt;
&lt;td&gt;Not supported&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Locked or app-managed fields&lt;/td&gt;
&lt;td&gt;No&lt;/td&gt;
&lt;td&gt;"Make changes to these custom fields fields directly on production"&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Deletions don't travel either: "Your deployment won't include any entities deleted on the sandbox", says the &lt;a href="https://support.atlassian.com/organization-administration/docs/recommended-workflow-for-deployments/" rel="noopener noreferrer"&gt;recommended workflow page&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Marketplace app configuration isn't on Atlassian's list. One admin's &lt;a href="https://community.atlassian.com/forums/Jira-Cloud-Admins-articles/Sandbox-to-production-deployment-in-Jira-Cloud-a-first-field/ba-p/3272220" rel="noopener noreferrer"&gt;field report&lt;/a&gt; says "Some of the marketplace app-provided configuration arrived. Some did not arrive at all", with nothing in the result to say which. Atlassian's product manager answered that "marketplace apps config are still a gap". The same report found, deploying into a second sandbox, that a workflow arrived inactive, because the deployment doesn't assign it anywhere. And there's no lock while a deployment runs, according to the suggestion &lt;a href="https://jira.atlassian.com/browse/CLOUD-13008" rel="noopener noreferrer"&gt;CLOUD-13008&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;If you run Jira Service Management, note the open bug &lt;a href="https://jira.atlassian.com/browse/CLOUD-13024" rel="noopener noreferrer"&gt;CLOUD-13024&lt;/a&gt;: validation fails for changes to a newly created service space, with no known workaround (In Progress, 16 votes on 14 November). Atlassian's request for app configuration support is &lt;a href="https://jira.atlassian.com/browse/CLOUD-12989" rel="noopener noreferrer"&gt;CLOUD-12989&lt;/a&gt;, with 8 votes.&lt;/p&gt;

&lt;h2&gt;
  
  
  Is there a rollback after a Jira sandbox deployment?
&lt;/h2&gt;

&lt;p&gt;The review screen says the changes "can't be reversed", and none of the four help pages on deployment mentions a rollback, undo or revert (we searched each one on 14 November). The admin API behind the page does return fields called &lt;code&gt;canPerformRollback&lt;/code&gt; and &lt;code&gt;rollbackAllowedTill&lt;/code&gt;. On our deployment, read while it was still scanning, they were false and empty, and I wouldn't plan around them until Atlassian documents them.&lt;/p&gt;

&lt;p&gt;So treat every deployment as one-way. For Premium, Atlassian suggests you "test your deployment by making changes to a small subset of data before the main deployment or purchase an additional sandbox for testing".&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F5yb4oslqe3lhbsmk5m7s.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F5yb4oslqe3lhbsmk5m7s.png" title="Illustration, generated locally with ERNIE-Image. A Jira sandbox deployment cannot be undone, so Atlassian advises testing a small subset first or keeping a second sandbox as staging. The road carries one arrow, the way back is crossed out, and the wall has a robot waiting behind it." alt="A cartoon robot carries a crate along a road painted with one big arrow pointing right, into a fortress wall where a green robot waves; a looping arrow on the ground is crossed out with a red circle and slash, and two smaller robots wait in glass domes with crates." width="800" height="448"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  What a Jira sandbox costs at 50 and 200 users
&lt;/h2&gt;

&lt;p&gt;You get sandboxes and the deployment with Premium. Atlassian's &lt;a href="https://www.atlassian.com/software/jira/pricing" rel="noopener noreferrer"&gt;Jira pricing page&lt;/a&gt; showed these US dollar prices on 14 November 2026:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Users&lt;/th&gt;
&lt;th&gt;Standard&lt;/th&gt;
&lt;th&gt;Premium&lt;/th&gt;
&lt;th&gt;Difference&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;50, monthly, per user&lt;/td&gt;
&lt;td&gt;$9.70&lt;/td&gt;
&lt;td&gt;$19.60&lt;/td&gt;
&lt;td&gt;$495 a month&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;200, monthly, per user&lt;/td&gt;
&lt;td&gt;$8.95&lt;/td&gt;
&lt;td&gt;$17.13&lt;/td&gt;
&lt;td&gt;$1,636 a month&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;50, annual (26-50 tier)&lt;/td&gt;
&lt;td&gt;$4,850&lt;/td&gt;
&lt;td&gt;$9,800&lt;/td&gt;
&lt;td&gt;$4,950 a year&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;200, annual (101-200 tier)&lt;/td&gt;
&lt;td&gt;$18,000&lt;/td&gt;
&lt;td&gt;$34,500&lt;/td&gt;
&lt;td&gt;$16,500 a year&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Premium buys more than sandboxes, so don't read the whole difference as the price of this feature. Our &lt;a href="https://leanzero.net/blog/jira-premium-vs-enterprise-pricing-200-500-seats?utm_source=devto&amp;amp;utm_medium=referral&amp;amp;utm_campaign=crosspost" rel="noopener noreferrer"&gt;Premium vs Enterprise pricing at 200-500 users&lt;/a&gt; goes through the rest. A second sandbox for testing is "$10,000 per sandbox, per app" on annual billing (&lt;a href="https://www.atlassian.com/platform/infrastructure/sandboxes" rel="noopener noreferrer"&gt;Atlassian Sandboxes&lt;/a&gt;).&lt;/p&gt;

&lt;p&gt;Configuration tools on the Marketplace are the other route. Appfire's Configuration Manager for Jira lists $1,585 a year at 50 users and $5,120 at 200 in Atlassian's Marketplace pricing data (read 14 November 2026). Salto's own pricing page says "Contact us", and its Marketplace listing shows "Free app".&lt;/p&gt;

&lt;h2&gt;
  
  
  If something doesn't work
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;"Another entity with the same name exists on destination"&lt;/strong&gt; means an item exists on both sites as two separate items with one name. The panel's advice is a full copy from production into the sandbox. If you deploy anyway, it warns that a duplicate "may" be created in production for you to clean up by hand.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Errors on items you didn't pick&lt;/strong&gt; can come from the dependency chain. In our run the one panel we opened, Story Points, showed "Error in dependent entities" and a same-name warning. Open each panel under &lt;strong&gt;Contains errors&lt;/strong&gt; to find the one with a cause of its own.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Your change isn't in the list&lt;/strong&gt; if you made it after the scan started. Select &lt;strong&gt;Scan again&lt;/strong&gt;, then &lt;strong&gt;Begin scan&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;A new filter is private in production.&lt;/strong&gt; That's documented behaviour, so share it again by hand.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;An automation rule uses a connection&lt;/strong&gt; (Slack, Teams, a web request). Connections don't deploy, so reconfigure them in production. Atlassian doesn't document whether deployed rules arrive enabled.&lt;/p&gt;

&lt;h2&gt;
  
  
  When to use the deploy beta now, and when to wait
&lt;/h2&gt;

&lt;p&gt;If your sandbox has a full copy from after the cut-off and your changes live in company-managed projects with no app configuration, I'd use it now. It saves you replaying workflow and field changes by hand, and the review step shows you every dependency before anything moves. Plan the time, though. Our two scans and the validation took about 21 minutes of waiting.&lt;/p&gt;

&lt;p&gt;If your sandbox is old, or you've been building in it for weeks while production moved on, expect the same name clashes we hit. Refresh first, then build, then deploy. And I'd start with one workflow the first time you try it, because a project pulls in its whole field scheme and we saw how fast that grows. If your workflows lean on Marketplace apps, a manual checklist or a configuration tool is still the safer route. On Standard there's no sandbox at all, so a checklist or a tool is the only route. It's a beta, and the &lt;a href="https://www.atlassian.com/roadmap/cloud?search=sandbox" rel="noopener noreferrer"&gt;cloud roadmap&lt;/a&gt; shows no general availability date.&lt;/p&gt;

&lt;h2&gt;
  
  
  What you have now
&lt;/h2&gt;

&lt;p&gt;[[takeaways]]&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;A way to check your sandbox's copy date against the cut-off before you build anything.&lt;/li&gt;
&lt;li&gt;The scan, select, review and deploy steps, with our real timing for each wait.&lt;/li&gt;
&lt;li&gt;A REST check that shows whether a field exists twice under one name.&lt;/li&gt;
&lt;li&gt;Atlassian's list of what deploys and what you'll still fix by hand. It doesn't cover Marketplace app configuration or an undo.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;You can check your sandbox's copy date, find your changes in a scan, follow the dependencies the tool adds and read validation errors in their side panels. You also have Atlassian's list of what moves and what you'll still fix by hand. If you've run a deployment on a freshly copied sandbox, I'd love to hear what your Summary.csv looked like, because that's the part we couldn't see this time :)&lt;/p&gt;




&lt;p&gt;Originally published on &lt;a href="https://leanzero.net/tutorials/jira-sandbox-to-production?utm_source=devto&amp;amp;utm_medium=referral&amp;amp;utm_campaign=crosspost" rel="noopener noreferrer"&gt;leanzero.net&lt;/a&gt;. More Atlassian, Forge and local-AI write-ups at &lt;a href="https://leanzero.net/blog?utm_source=devto&amp;amp;utm_medium=referral&amp;amp;utm_campaign=crosspost" rel="noopener noreferrer"&gt;leanzero.net/blog&lt;/a&gt;, and if you're planning a migration or a Forge app, that's what we do: &lt;a href="https://leanzero.net/services?utm_source=devto&amp;amp;utm_medium=referral&amp;amp;utm_campaign=crosspost" rel="noopener noreferrer"&gt;leanzero.net/services&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>jira</category>
      <category>atlassian</category>
    </item>
    <item>
      <title>Jira Timeline vs Plans: What Happens When a Date Moves</title>
      <dc:creator>Mihai Perdum</dc:creator>
      <pubDate>Sat, 14 Nov 2026 07:07:24 +0000</pubDate>
      <link>https://dev.to/mihai_leanzero/jira-timeline-vs-plans-what-happens-when-a-date-moves-jcj</link>
      <guid>https://dev.to/mihai_leanzero/jira-timeline-vs-plans-what-happens-when-a-date-moves-jcj</guid>
      <description>&lt;p&gt;Just after midnight on 14 November we dragged one work item a week later in a Jira plan on our test site, then read back the two work items waiting on it. Neither had moved. Four days earlier we'd done the same on the space Timeline (a space is what Jira used to call a project), Jira's built-in Gantt view, a bar chart of work over time, and got the same answer. In both places Jira drew a red line, said the dates overlap, and left the rest to us.&lt;/p&gt;

&lt;p&gt;So if you're asking "Jira Timeline vs Plans" because you want the dates of blocked work to follow a slip, neither does that when you edit a date by hand. Plans (Atlassian's advanced planning, the feature that used to be called Advanced Roadmaps) has one more tool, the auto-scheduler. It did re-date the whole chain in our test. It also overwrote dates we had set by hand, pulled the first work item 10 days earlier, and refused to run at all until the plan had a team. A Gantt app on top of Jira is the third route: in LeanZero Management, the one we sell, the blocked work moves with each drag, and you review the new dates before Jira gets them.&lt;/p&gt;

&lt;p&gt;Closing the gap the Atlassian way costs money. Plans comes with Jira Premium, which on 14 November 2026 cost $19.60 per user a month for the first 100 users, against $9.70 on Standard (&lt;a href="https://www.atlassian.com/software/jira/pricing" rel="noopener noreferrer"&gt;Jira pricing&lt;/a&gt;). Premium buys other features too, but that's what moving up from Standard costs. Atlassian's own feature request, &lt;a href="https://jira.atlassian.com/browse/JRACLOUD-88193" rel="noopener noreferrer"&gt;JRACLOUD-88193&lt;/a&gt;, "Advanced Roadmap - automatically shift blocked tasks when changing end date", has been open since July 2022 and had 119 votes when we read it.&lt;/p&gt;

&lt;p&gt;I run a company that sells a Gantt app for Jira, LeanZero Management, so I'm not neutral. For the Timeline and Plans we used our own test site and read the dates back from Jira after each step. If you only need dependency lines and a warning, the Timeline is probably enough and you need neither Premium nor an app.&lt;/p&gt;

&lt;h2&gt;
  
  
  Neither moved the blocked work on a manual edit: what we found
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;On the space Timeline, a drag of eight days on the blocker didn't move the blocked work item. Jira still held its old dates and last-updated time. The line turned red and a card said "Dates overlap".&lt;/li&gt;
&lt;li&gt;In Plans, a seven-day drag on the first of three linked work items moved only that one. Save changes wrote its 2 dates to Jira. B and C weren't touched. The plan showed "Dates overlap (5 days)" on the line and "blocks (-5d)" in the Dependencies view.&lt;/li&gt;
&lt;li&gt;Plans' auto-scheduler refused to start until the plan had a team ("Add a team to your plan to auto-schedule work items"), and by default it works on work items that have an estimate.&lt;/li&gt;
&lt;li&gt;Once it ran, the auto-scheduler put all 3 work items back to back with no overlap. It rewrote dates they already had, although the plan setting read "Only add values to empty fields", and it moved the first work item from 23 November back to 13 November.&lt;/li&gt;
&lt;li&gt;Nothing in Plans reached Jira until we pressed Save changes, and "Send update notifications" is ticked by default in that dialog.&lt;/li&gt;
&lt;li&gt;Neither the Timeline nor Plans shows a critical path. Atlassian's requests for one have 99 and 90 votes, and the second dates from 2014.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Jira Timeline vs Plans vs a Gantt app at a glance
&lt;/h2&gt;

&lt;p&gt;Here's how the three behaved when one date in a chain moved. We ran the Timeline and Plans on wolfaenpak, our Atlassian test site, with two and three linked work items, on 10 and 14 November 2026. The app column comes from a different run: a chain of eight work items on our demo site on 10 November. I'd read it as an example of the third route.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;&lt;/th&gt;
&lt;th&gt;Space Timeline&lt;/th&gt;
&lt;th&gt;Plans (Premium)&lt;/th&gt;
&lt;th&gt;Gantt app (LeanZero Management)&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Jira edition needed&lt;/td&gt;
&lt;td&gt;Every edition, Free included&lt;/td&gt;
&lt;td&gt;Premium or Enterprise&lt;/td&gt;
&lt;td&gt;Any edition, plus the app&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Blocked work after a manual date move&lt;/td&gt;
&lt;td&gt;Stays on its old dates&lt;/td&gt;
&lt;td&gt;Stays on its old dates&lt;/td&gt;
&lt;td&gt;Moves to the working day after its blocker&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;What warns you&lt;/td&gt;
&lt;td&gt;Red line, "Dates overlap" card&lt;/td&gt;
&lt;td&gt;Red line, "Dates overlap (5 days)", "blocks (-5d)"&lt;/td&gt;
&lt;td&gt;A strip saying how many work items moved, and why&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Re-dating the chain for you&lt;/td&gt;
&lt;td&gt;No. Atlassian's tip is to multi-select bars and drag them together&lt;/td&gt;
&lt;td&gt;Auto-scheduler: needs a team and estimates, previews, can rewrite set dates&lt;/td&gt;
&lt;td&gt;Every drag, on the plan's working calendar (Mon-Fri by default), with lag in working days&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;When Jira is written&lt;/td&gt;
&lt;td&gt;At once, on drop&lt;/td&gt;
&lt;td&gt;On Save changes&lt;/td&gt;
&lt;td&gt;On Apply, after a review of every date&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Links it reads&lt;/td&gt;
&lt;td&gt;Blocks, inside one space&lt;/td&gt;
&lt;td&gt;Links across spaces and teams&lt;/td&gt;
&lt;td&gt;Jira blocks links&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;What it doesn't do&lt;/td&gt;
&lt;td&gt;Cross-space dependencies, critical path&lt;/td&gt;
&lt;td&gt;Critical path. Skipping weekends in the auto-scheduler is an open request, not tested here&lt;/td&gt;
&lt;td&gt;Resource levelling; undo an Apply as one transaction&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;The Timeline limit comes straight from Atlassian's page: "The timeline can only show work items with the Blocks work item link type and link work items from a single space" (&lt;a href="https://support.atlassian.com/jira-software-cloud/docs/manage-dependencies-between-epics-on-the-timeline/" rel="noopener noreferrer"&gt;What are dependencies on the timeline?&lt;/a&gt;). Jira's pricing page says it too, in its own words. Dependencies inside one team or project are shown on the timeline, and dependencies across teams and projects belong in a plan.&lt;/p&gt;

&lt;h2&gt;
  
  
  What happens on the Jira Timeline when a date moves (no auto schedule)
&lt;/h2&gt;

&lt;p&gt;We kept the test small. Two work items, A and B, sat in one space. A blocks link ran from A to B, so B can't start until A is done. A ran 16 to 20 November and B started the next day.&lt;/p&gt;

&lt;p&gt;We dragged A to the right on the Timeline. It snapped to eight days later, 24 to 28 November, which put A's finish a week past B's start. B didn't move. We read B back through Jira's REST API (the interface scripts use to read and write Jira). Same dates, same last-updated time as before the drag. B's history held only the link we had created.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Flczt2vtv5dfw2eebn8fj.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Flczt2vtv5dfw2eebn8fj.png" title="The space Timeline after an eight-day drag on the blocker, 10 November 2026. Notice B still starts on Nov 21 while A is now due Nov 28, and Jira's reaction is the Dates overlap line." alt="Jira Timeline dependency card after a drag: A blocks B, A due Nov 28, B still starting Nov 21, with a Dates overlap warning" width="799" height="299"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Then the line between them turned red. Clicking it opened a small card that ends in "Dates overlap". Jira showed no message and asked nothing. When we put A back over the API, the line went grey again and the warning disappeared, so the red means overlap and nothing more. Editing A's due date through the API instead of dragging gave the same result.&lt;/p&gt;

&lt;p&gt;Atlassian's documentation only promises the warning. "In the event of overlapping dates, the dependency link turns red, signaling the potential for delay or risk." For moving linked work together, what I found is an Atlassian knowledge-base tip: select every bar with Ctrl or Cmd and a click, then drag them as one, "maintaining the same-day difference" (&lt;a href="https://support.atlassian.com/jira/kb/how-to-move-start-and-end-dates-of-issues-with-its-dependant-issues-in-the-project-timeline/" rel="noopener noreferrer"&gt;Atlassian KB&lt;/a&gt;). I'd use it for two or three bars. On a chain of eight you're doing the dependency maths in your head.&lt;/p&gt;

&lt;p&gt;Someone asked for the automatic version in 2023. &lt;a href="https://jira.atlassian.com/browse/JRACLOUD-91659" rel="noopener noreferrer"&gt;JRACLOUD-91659&lt;/a&gt;, "Move dependent issues when main issue is moved in timeline view", describes exactly our test ("dependent issues are not moved"). It was closed as "Not a bug".&lt;/p&gt;

&lt;h2&gt;
  
  
  Jira Plans auto schedule: what it moves and what you still accept
&lt;/h2&gt;

&lt;p&gt;For Plans we built the same thing with three work items, A blocks B blocks C, each five working days long, Monday to Friday, back to back from 16 November. We put them in a scratch plan on our Premium test site and gave each an estimate of five days, because by default the auto-scheduler works on estimated work.&lt;/p&gt;

&lt;h3&gt;
  
  
  A manual drag in Plans moves only what you drag
&lt;/h3&gt;

&lt;p&gt;We dragged A one week later, to 23 to 27 November. B and C stayed where they were, in the plan's timeline and in its list view. Up in the header: "Unsaved changes 1".&lt;/p&gt;

&lt;p&gt;Jira still had the old dates. A read from the API at that moment showed A on 16 to 20 November. Plans keeps your edits in the plan until you save them. Atlassian's page calls it "a sandbox environment meaning that any changes you make won't be committed back to your Jira work items until you choose to do so" (&lt;a href="https://support.atlassian.com/jira-software-cloud/docs/auto-schedule-issues-on-your-advanced-roadmaps-timeline/" rel="noopener noreferrer"&gt;Autoschedule work items on your plan&lt;/a&gt;).&lt;/p&gt;

&lt;p&gt;Unsaved changes listed one work item with 2 fields, old value and new value side by side. We pressed Save changes. In Jira, A now ran 23 to 27 November. B and C hadn't changed, down to their last-updated times.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fiu9fxlbewyolmqipdfeq.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fiu9fxlbewyolmqipdfeq.png" title="Plans after the save, 14 November 2026. Notice the count in the warning: Plans tells you the overlap is 5 days, which the space Timeline doesn't." alt="Plans dependency card: LZPP-5304 blocks LZPP-5305, with a red link icon and the warning Dates overlap (5 days)" width="800" height="232"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;I find Plans more precise about the problem than the Timeline. The card says "Dates overlap (5 days)", and the Dependencies tab, a view that lays the work items out as cards joined by arrows, labels each link with its gap.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F4acbouyrmn8sjpktosuf.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F4acbouyrmn8sjpktosuf.png" title="The Dependencies tab after the drag. Notice the two labels: -5d in red is the overlap, and +2d in grey is the weekend between B's Friday finish and C's Monday start." alt="Plans Dependencies view: A blocks B labelled blocks (-5d) in red, B blocks C labelled blocks (+2d) in grey, with each card's start and end dates" width="800" height="70"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;I like that view. You see the slip at a glance. Moving B and C is still your job, and the docs say so plainly: "To resolve this, change the start or end date associated with the dependency" (&lt;a href="https://support.atlassian.com/jira-software-cloud/docs/change-how-advanced-roadmaps-displays-dependencies/" rel="noopener noreferrer"&gt;Change how your plan timeline displays dependencies&lt;/a&gt;).&lt;/p&gt;

&lt;h3&gt;
  
  
  The auto-scheduler re-dated the chain, and more than we asked for
&lt;/h3&gt;

&lt;p&gt;The auto-scheduler is the Plans feature that works dates out for you. Atlassian says it "balances a range of different values from the dates assigned to a work item, work item estimates, a team's capacity and velocity, and any dependencies between work items" (&lt;a href="https://support.atlassian.com/jira-software-cloud/docs/how-does-the-auto-scheduler-in-advanced-roadmaps-work/" rel="noopener noreferrer"&gt;How does the auto-scheduler in my plan work?&lt;/a&gt;).&lt;/p&gt;

&lt;p&gt;Our first click on Auto-schedule did nothing but show a flag: "Add a team to your plan to auto-schedule work items". So we added a plan-only team (a team that exists in the plan and not in the rest of Jira) and assigned it to all three. Then we clicked again. This time a popup opened, and it read: "By default, the Auto-scheduler schedules all work items in your plan" and "Based on your current settings, the Auto-scheduler will only add data to empty fields in your plan."&lt;/p&gt;

&lt;p&gt;Our first preview stretched each bar to 56 days because of the team's capacity, which we had set to 5. We cancelled it. So we set the capacity to 40, and the bars went back to a week each. I think the number means hours per week in a plan estimated in days. We found no Atlassian page that says so, so check it on your own plan before you trust it.&lt;/p&gt;

&lt;p&gt;Our second try was much tidier. A on 13 to 19 November, B on 20 to 26 November, C on 27 November to 3 December. One after the other in link order, no overlap. I liked that part. A banner said "You'll still need to review and save all changes in your plan to Jira", and the dates appeared in the plan only after we pressed Accept changes.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F7q03l44njrjs3h8v7ykw.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F7q03l44njrjs3h8v7ykw.png" title="The review after the auto-scheduler, 14 November 2026. Notice A's due date going from Nov 27 back to Nov 19, and the ticked Send update notifications box." alt="Plans Unsaved changes dialog after the auto-scheduler: for LZPP-5306 and LZPP-5304 the team, due date and start date change, with Current (Jira) and New columns and Send update notifications ticked" width="800" height="311"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Two things in that result surprised me. All three work items already had dates, and the auto-scheduler rewrote them anyway, while the overwrite setting said "Only add values to empty fields" for everything. The settings page hints at why: its overwrite choice lists sprints, teams and releases, and dates aren't among them. Atlassian's docs agree, once you find the sentence: "By default, the auto-scheduler schedules all work items in your plan, regardless of whether you've set dates for them."&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fjoqfx39hogq24azbx7ne.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fjoqfx39hogq24azbx7ne.png" title="Illustration, generated locally with ERNIE-Image. The auto-scheduler re-dated work items that already had dates. The overwrite choice on its settings page lists sprints, teams and releases, and dates aren't on it. The sign said empty fields only, and the roller painted the dated ones anyway." alt="A violet robot in green overalls stands on a stepladder roller-painting yellow paint over a red circle on one of a row of clipped pages, while a worried blue robot holds up a page smeared with yellow and a green robot points at it; clipboard checklists of shapes with tick boxes hang on the wall." width="800" height="448"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;And A went backwards. We had moved it to start on 23 November and the auto-scheduler started it on 13 November. That was the date in UTC (coordinated universal time) when we ran it, while on our own clock it was already the 14th. An open request, &lt;a href="https://jira.atlassian.com/browse/JRACLOUD-88004" rel="noopener noreferrer"&gt;JRACLOUD-88004&lt;/a&gt; "Respect fixed start date when auto-scheduling" (81 votes), describes the same habit of "adjusting it to today's date". One run can't show which of the two it counts from. I wouldn't run it on a live plan without trying it on a copy first.&lt;/p&gt;

&lt;p&gt;Save changes then wrote all three: "3 changes were successfully saved in Jira." With the box ticked, Jira sends its usual update notifications for those work items (we didn't check who received them).&lt;/p&gt;

&lt;p&gt;If your teams don't work weekends, read &lt;a href="https://jira.atlassian.com/browse/JRACLOUD-88065" rel="noopener noreferrer"&gt;JRACLOUD-88065&lt;/a&gt;, "Option to exclude non-working days or weekend in Auto-schedule", before you plan around it. It had 267 votes on 14 November. Our one-week items can't show whether the auto-scheduler skips weekends.&lt;/p&gt;

&lt;h2&gt;
  
  
  Shift blocked tasks when changing the end date: what Atlassian's tracker says
&lt;/h2&gt;

&lt;p&gt;Put the two tests together and the pattern is simple. Jira treats a blocks link as information. It draws it, colours it red when the dates disagree, and leaves the decision with you. Plans adds a planner that can re-sequence everything, but as a batch you run on purpose. It has its own rules about teams and capacity, and a habit of starting from today.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F337nrdrza17d0q6ki82h.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F337nrdrza17d0q6ki82h.png" title="Illustration, generated locally with ERNIE-Image. On the Timeline a red blocks link is a warning for you to act on. In Plans the auto-scheduler is a lever you pull for the whole plan or the work items you select, and the results still wait for Save changes. Both robots look far too pleased about it." alt="Two robots in a bright workshop: a blue robot laughs with its arms spread wide beside a green notice board where two cards hang from a red chain under a red flag, while a violet robot in an apron pushes a big yellow lever that feeds a row of task cards into a re-ordering machine with a yellow funnel and a red alarm lamp." width="800" height="448"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Plenty of people want the third option (me included), where the blocked work follows the blocker the moment it slips. That's &lt;a href="https://jira.atlassian.com/browse/JRACLOUD-88193" rel="noopener noreferrer"&gt;JRACLOUD-88193&lt;/a&gt;, open since July 2022 with 119 votes and still marked Gathering Interest. Its sibling for working days in plans, &lt;a href="https://jira.atlassian.com/browse/JRACLOUD-88154" rel="noopener noreferrer"&gt;JRACLOUD-88154&lt;/a&gt;, has 341. A critical path, the longest chain of dependent work that sets the finish date, isn't in either product. Atlassian's tracker has requests for it: &lt;a href="https://jira.atlassian.com/browse/JRACLOUD-88163" rel="noopener noreferrer"&gt;JRACLOUD-88163&lt;/a&gt; (99 votes, since 2021) and &lt;a href="https://jira.atlassian.com/browse/JRACLOUD-88103" rel="noopener noreferrer"&gt;JRACLOUD-88103&lt;/a&gt; (90 votes, since 2014). We searched the eight Atlassian pages we re-read on 14 November for the phrase and found it on none of them.&lt;/p&gt;

&lt;p&gt;I think Atlassian's choice makes sense for them. A Jira site is shared by many teams, and a date that rewrites other teams' dates by itself would surprise people. So people who want the automatic version add a Gantt app on top of Jira, and there are plenty of those. A Marketplace search for "gantt" on 14 November returned 82 Jira Cloud apps, and 39 have Gantt in the name.&lt;/p&gt;

&lt;h2&gt;
  
  
  A Gantt app that moves dependent dates: LeanZero Management
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://marketplace.atlassian.com/apps/736826281/leanzero-management-gantt-charts-ppm-for-jira?hosting=cloud" rel="noopener noreferrer"&gt;LeanZero Management&lt;/a&gt; is ours. It's a Gantt and planning app for Jira Cloud, free on the Marketplace, and version 6.19.0 (released 6 November 2026) is current. It reads the same Jira blocks links as the Timeline and Plans, and a drag moves the work that waits on it.&lt;/p&gt;

&lt;p&gt;On our demo plan on 10 November we dragged one work item five working days later. The 7 work items that waited on it moved five working days each, each keeping its length, with the weekend skipped. Each one starts on the working day after its blocker finishes, plus any lag on the link (a wait you add to the link), counted in working days. A strip said how many work items moved, and a Why did this move? list named the blocker behind each one.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fh57pfi6rzxdecwl3qpgb.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fh57pfi6rzxdecwl3qpgb.png" title="LeanZero Management 6.19.0 right after one drag, 10 November 2026. Notice the strip under the tabs: 7 work items moved, and nothing has been written to Jira yet." alt="LeanZero Management plan after a drag: Your change moved 7 work items with a Why did this move? button, and Apply 8 changes in the plan header" width="800" height="439"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Jira isn't touched until you press Apply, the button that writes the plan's dates to Jira. Then a review lists the old and new dates. Our Apply wrote the 16 new start and due dates of all 8 work items in about 22 seconds, reading each one back from Jira. It writes with notifications off, so the people watching those work items don't get eight emails for one slip. The &lt;a href="https://dev.to/tutorials/jira-gantt-dependencies-leanzero-management"&gt;step-by-step tutorial&lt;/a&gt; walks the whole run, and the &lt;a href="https://dev.to/tutorials/jira-gantt-chart-critical-path-leanzero-management"&gt;critical path tutorial&lt;/a&gt; covers reading the chain that sets your finish date.&lt;/p&gt;

&lt;p&gt;What it doesn't do. There's no resource levelling, so it reports when one person has too much work and never moves anyone's dates to fix it. An Apply isn't one transaction: if it stops at work item 4 of 8, the first three stay written and Resume carries on from there. You also install an app and build a plan in it, which is more setup than switching on the Timeline. Our &lt;a href="https://dev.to/portfolio/leanzero-management"&gt;product page&lt;/a&gt; has the manual and the short videos, and an earlier post, &lt;a href="https://dev.to/blog/leanzero-management-jira-dependency-moves-dates"&gt;the Jira dependency that moves dates&lt;/a&gt;, explains how the chain is worked out.&lt;/p&gt;

&lt;h2&gt;
  
  
  Timeline, Plans or a Gantt app: which one fits your team
&lt;/h2&gt;

&lt;p&gt;I'd stay on the space Timeline if your dependencies live in one space and you only need to see them. Its red line is a reliable warning. And the Ctrl or Cmd multi-select drag is enough for a short chain.&lt;/p&gt;

&lt;p&gt;I'd use Plans if you're already on Premium and your teams plan with estimates and capacity. Select the work items you want re-dated before you run the auto-scheduler. Its popup says it then works on those (we ran it on all three). Read the rows in Unsaved changes before you save, and untick Send update notifications if you don't want the noise. Expect it to rewrite dates you set by hand. It rewrote ours.&lt;/p&gt;

&lt;p&gt;I'd add a Gantt app if you want the blocked work to follow a slip on each edit and you'd rather review the result than rebuild it. If that's your main reason for looking at Premium, try an app on Standard first and compare the bill.&lt;/p&gt;

&lt;p&gt;I'm curious how other teams live with this. If you plan in Jira, what do you do on the day a blocker slips: drag everything by hand, run the auto-scheduler, or keep the real schedule somewhere else? Tell me in the comments under this post.&lt;/p&gt;




&lt;p&gt;Originally published on &lt;a href="https://leanzero.net/blog/jira-timeline-vs-plans-leanzero-management?utm_source=devto&amp;amp;utm_medium=referral&amp;amp;utm_campaign=crosspost" rel="noopener noreferrer"&gt;leanzero.net&lt;/a&gt;. More Atlassian, Forge and local-AI write-ups at &lt;a href="https://leanzero.net/blog?utm_source=devto&amp;amp;utm_medium=referral&amp;amp;utm_campaign=crosspost" rel="noopener noreferrer"&gt;leanzero.net/blog&lt;/a&gt;, and if you're planning a migration or a Forge app, that's what we do: &lt;a href="https://leanzero.net/services?utm_source=devto&amp;amp;utm_medium=referral&amp;amp;utm_campaign=crosspost" rel="noopener noreferrer"&gt;leanzero.net/services&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>jira</category>
      <category>atlassian</category>
      <category>projectmanagement</category>
      <category>productivity</category>
    </item>
    <item>
      <title>Jira Gantt Dependencies: Drag One, Shift the Rest</title>
      <dc:creator>Mihai Perdum</dc:creator>
      <pubDate>Fri, 13 Nov 2026 12:00:20 +0000</pubDate>
      <link>https://dev.to/mihai_leanzero/jira-gantt-dependencies-drag-one-shift-the-rest-on2</link>
      <guid>https://dev.to/mihai_leanzero/jira-gantt-dependencies-drag-one-shift-the-rest-on2</guid>
      <description>&lt;p&gt;On 1 June 2026 a Jira user &lt;a href="https://community.atlassian.com/forums/discussion/3242379/is-microsoft-project-style-auto-scheduling-possible-in-jira-plans" rel="noopener noreferrer"&gt;asked the Atlassian Community&lt;/a&gt; whether Microsoft Project-style auto-scheduling was possible in Jira Plans. They summed up the problem in one line: "While JIRA supports dependencies, it doesn't automatically adjust start/due dates when upstream tasks shift—so updates are manual." The &lt;a href="https://jira.atlassian.com/browse/JRACLOUD-88193" rel="noopener noreferrer"&gt;feature request for exactly that&lt;/a&gt;, JRACLOUD-88193, has been open since July 2022 and had 119 votes when we read it on 10 November 2026.&lt;/p&gt;

&lt;p&gt;This tutorial shows Jira Gantt dependencies that move dates. In LeanZero Management, our Gantt and planning app for Jira Cloud, you drag one work item a week later and the work items that wait on it move too. On our demo plan one drag moved 7 waiting work items by five working days each. Apply then wrote the new start and due dates of all 8 work items back to Jira in about 22 seconds. Nothing reaches Jira before you press Apply, and the links that drive the move are Jira's own blocks links.&lt;/p&gt;

&lt;p&gt;We make the app, so I'm not neutral. We checked what Jira does without it first, on our test site, and that part is the first section below. There's a 73-second video of this walk, recorded on 1 October 2026. We ran the steps again on 10 November on version 6.19.0. Two things differ from the video. The video drags the work item two working days in The real plan view, and we dragged it five in the Everything view, which lists every row. And the Review changes dialog is now in sentence case: it says "Apply 8 changes" where the video shows "Apply 8 Changes".&lt;/p&gt;

&lt;p&gt;&lt;a href="https://www.youtube.com/watch?v=eFeg315eyfc" rel="noopener noreferrer"&gt;https://www.youtube.com/watch?v=eFeg315eyfc&lt;/a&gt;&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Note&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Before you start&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Jira Cloud with &lt;a href="https://marketplace.atlassian.com/apps/736826281/leanzero-management-gantt-charts-ppm-for-jira?hosting=cloud" rel="noopener noreferrer"&gt;LeanZero Management&lt;/a&gt; installed. It's free on the Marketplace today. We ran this on 6.19.0, released 6 November 2026.&lt;/li&gt;
&lt;li&gt;One plan in the app whose work items have start and due dates and are joined by Jira "blocks" links. A blocks link is Jira's standard way to say "this work item can't start until that one is done", and the app follows those links. The &lt;a href="https://dev.to/portfolio/leanzero-management"&gt;product page&lt;/a&gt; has the app's manual if you still need to set up a plan.&lt;/li&gt;
&lt;li&gt;The Editor role (or higher) on the plan, plus Browse Projects and Edit Issues in Jira on every work item you change, and Schedule Issues if your plan uses Jira's own Due date field. The app checks these before it writes.&lt;/li&gt;
&lt;li&gt;A desktop browser. Our window was 1,675 by 1,250 px.&lt;/li&gt;
&lt;li&gt;When you're done you'll have moved one slipped work item, seen why each of the others moved, and written the new dates to Jira with a record of each one.&lt;/li&gt;
&lt;/ul&gt;
&lt;/blockquote&gt;

&lt;p&gt;[[steps]]&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Open the plan on the Timeline at Week zoom&lt;/strong&gt;: you see the bars and the dates.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Find the work item that slipped&lt;/strong&gt;: its card shows its dates and its room.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Drag it a week later&lt;/strong&gt;: the strip says how many work items moved.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Click Why did this move?&lt;/strong&gt;: one line per moved work item, with what it waits on.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Click Apply 8 changes and read the review&lt;/strong&gt;: old dates struck through.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Click Apply 8 changes again&lt;/strong&gt;: the app writes each work item and reads it back.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Check that Jira holds the new dates&lt;/strong&gt;: the bar card says so.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  What the Jira timeline does with dependencies, and what it leaves to you
&lt;/h2&gt;

&lt;p&gt;We tested this on wolfaenpak, our test site, with no app involved. Two work items in a team-managed space, A and B. A blocks B. B starts the day after A ends. We dragged A eight days later on the space's Timeline and read both back over the Jira REST API (the web interface programs use to read and change Jira data).&lt;/p&gt;

&lt;p&gt;A moved. B didn't. Not by a day. Its dates, its last-updated time and its history were exactly as before. The dependency line turned red, and clicking it opened a card with a warning: "Dates overlap". A due date changed over the REST API instead of a drag did the same: B stayed put and the line went red.&lt;/p&gt;

&lt;p&gt;The red line was expected. What surprised us is that nothing else happened: no message came up, and the words "Dates overlap" only show if you go and click the line. On a plan with a few hundred links I'd want more than that.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fv1k6tj8rgzssrmqtyf84.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fv1k6tj8rgzssrmqtyf84.png" title="Illustration, generated locally with ERNIE-Image. Jira turns the dependency line red when two work items overlap and then says nothing else until you go and click the line yourself. Two robots, and a tower of blocks that never moved." alt="Two robots at a workbench with five coloured toy blocks on a rail, against a solid blue wall: one cheers and holds up a magnifying glass, the other pokes a sagging red cord with a knob on its end that runs over the blocks to the purple one and carries a blank paper tag, and a tower of five stacked blocks behind them stands untouched." width="800" height="448"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Flczt2vtv5dfw2eebn8fj.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Flczt2vtv5dfw2eebn8fj.png" title="Jira's own timeline after we dragged the blocker eight days later. Notice B's start date, still Nov 21, and the Dates overlap warning on the red link. Jira Cloud on our test site, 10 November 2026, Jira's own timeline, no app involved." alt="Jira timeline dependency card after a drag: A blocks B, A due Nov 28, B still starting Nov 21, with a yellow Dates overlap warning" width="799" height="299"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;That matches Atlassian's page &lt;a href="https://support.atlassian.com/jira-software-cloud/docs/manage-dependencies-between-epics-on-the-timeline/" rel="noopener noreferrer"&gt;What are dependencies on the timeline?&lt;/a&gt;: "In the event of overlapping dates, the dependency link turns red, signaling the potential for delay or risk." I think that's a fair warning. The same page says the timeline "can only show work items with the Blocks work item link type and link work items from a single space". Atlassian's own knowledge-base answer for moving a chain is manual: &lt;a href="https://support.atlassian.com/jira/kb/how-to-move-start-and-end-dates-of-issues-with-its-dependant-issues-in-the-project-timeline/" rel="noopener noreferrer"&gt;select the bars with Ctrl or Cmd and drag them together&lt;/a&gt;. That works when you know which bars to select. On a plan with 1,226 work items I wouldn't trust myself to find all seven.&lt;/p&gt;

&lt;h3&gt;
  
  
  Jira plan auto schedule: what it does with dependencies
&lt;/h3&gt;

&lt;p&gt;Jira Plans (the advanced planning in Premium and Enterprise) has an auto-scheduler, and it does use dependencies. Atlassian says it &lt;a href="https://support.atlassian.com/jira-software-cloud/docs/how-does-the-auto-scheduler-in-advanced-roadmaps-work/" rel="noopener noreferrer"&gt;balances "the dates assigned to a work item, work item estimates, a team's capacity and velocity, and any dependencies between work items"&lt;/a&gt;. You select Preview results, then Accept changes, and nothing reaches your Jira work items until you save, because the plan is "a sandbox environment". So Plans also lets you review before you write. If you're on Premium I'd try it first.&lt;/p&gt;

&lt;p&gt;Atlassian lists the limits on its &lt;a href="https://support.atlassian.com/jira-software-cloud/docs/auto-schedule-issues-on-your-advanced-roadmaps-timeline/" rel="noopener noreferrer"&gt;autoschedule page&lt;/a&gt;: by default it works only on work items "that have an estimation value", and it "will not overwrite any data for work items in an active sprint". The &lt;a href="https://support.atlassian.com/jira-software-cloud/docs/how-does-the-auto-scheduler-in-advanced-roadmaps-work/" rel="noopener noreferrer"&gt;how-it-works page&lt;/a&gt; adds that it ignores work items in a Done status. It also weighs all of that at once, so I think one late work item probably won't give you one predictable push down its chain. That push is what the 119 votes on JRACLOUD-88193 ask for: "automatically shift blocked tasks when changing end date".&lt;/p&gt;

&lt;h2&gt;
  
  
  Automatically shift the dates of dependent issues when a blocker slips
&lt;/h2&gt;

&lt;p&gt;The app's rule is a finish-to-start dependency, the standard kind in project scheduling: the blocked work item can start on the first working day after its blocker's due date. If one work item waits on several others, it starts after the latest of them. A lag on the link (extra working days between the two, set in the app) is added per link before the latest one is picked. Working days come from the plan's calendar, Monday to Friday unless you change it. Weekends don't count. A push moves a work item's start and keeps its length, so its due date moves by the same number of working days. The rule works in both directions: a waiting work item is placed exactly on the first day its blockers allow, so pulling a blocker earlier pulls the work items behind it earlier too. There are three exceptions: a work item that is Done never moves, one that is In Progress in Jira keeps its Jira dates, and work not started is never pulled onto today or a day that has passed. In the plan below, Dec 25 and Jan 1 count as working days, so the only days the example skips are weekends.&lt;/p&gt;

&lt;p&gt;If you want the reasoning behind that rule and where it gets subtle, Gabriela wrote &lt;a href="https://dev.to/blog/leanzero-management-jira-dependency-moves-dates"&gt;the concept piece on the Jira dependency that moves dates&lt;/a&gt;. Here we only use it.&lt;/p&gt;

&lt;p&gt;Our demo plan is the ITHELP Helpdesk Operations Plan on our demo site. ITHELP-102, "Migrate conference room AV" (the audio-visual kit), runs Dec 23 to Dec 28, 2026. Seven work items wait on it in one straight line: ITHELP-124, 131, 133, 139, 146, 148 and 149. The last one was due Feb 24, 2027. We'll pretend the AV hardware arrives a week late. Hardware does that.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 1: Open the plan on the Timeline at Week zoom
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;In Jira's top bar, open &lt;strong&gt;Apps&lt;/strong&gt; and select &lt;strong&gt;LeanZero Management&lt;/strong&gt;. The Plans page opens.&lt;/li&gt;
&lt;li&gt;In &lt;strong&gt;Find a plan or project key&lt;/strong&gt; at the top of the Plans page, type the plan's name or its Jira project key, then select the plan. We typed ITHELP. The plan opens on its summary cards, about 7 seconds for our plan of 1,226 work items (1,211 of them open).&lt;/li&gt;
&lt;li&gt;Below the cards, select the &lt;strong&gt;Timeline&lt;/strong&gt; tab. The bars appear with a toolbar above them.&lt;/li&gt;
&lt;li&gt;In the Timeline toolbar, select &lt;strong&gt;Everything&lt;/strong&gt;, then &lt;strong&gt;Week&lt;/strong&gt;, then &lt;strong&gt;Today&lt;/strong&gt;. Everything shows one row per work item, Week sets the scale to days, and Today scrolls to today's date.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;You should see a row per work item with State, Room and Finish columns. Room is how many working days it can slip before it moves the plan's finish. The plan header should read "Saved" with no Apply button. If an Apply button is already there, the plan already holds changes that Jira doesn't have: edits someone saved, or your own autosaved draft. Your Apply would write those too, so find out whose they are before you drag.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 2: Find the work item that slipped and read its card
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Scroll the Timeline down to the work item's row and across to its dates. In the Everything view rows are sorted by key as text, so ITHELP-102 sits between ITHELP-1019 and ITHELP-1020.&lt;/li&gt;
&lt;li&gt;Hover over its bar. A hover card opens. Ours read "ITHELP-102 · Migrate conference room AV / On track · Submitted · Dec 23, 2026 → Dec 28, 2026 (4 wd) / 456 wd of room before it moves the finish". The wd stands for working days.&lt;/li&gt;
&lt;li&gt;Optional: to see the link lines, open the &lt;strong&gt;⋯&lt;/strong&gt; menu at the right of the Timeline toolbar and select &lt;strong&gt;Show all connectors&lt;/strong&gt;. Lines are drawn from each bar to the work items it blocks.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;On a big plan the seven waiting work items are hundreds of rows away from the one you hover, so you won't see them on one screen. Step 4 lists them for you, and on a big plan I'd skip the hover and go straight there.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 3: Drag the work item a week later on the Jira Gantt chart
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Drag the bar to the right by one week. At Week zoom that's five working days. Release it. Within about 2 seconds a strip appears above the Timeline toolbar: "Your change moved 7 work items · the finish is the saved plan's", with &lt;strong&gt;Why did this move?&lt;/strong&gt;, &lt;strong&gt;Details&lt;/strong&gt; and a close button.&lt;/li&gt;
&lt;li&gt;Look at the plan header at the top. It now shows &lt;strong&gt;Save (8)&lt;/strong&gt; and &lt;strong&gt;Apply 8 changes&lt;/strong&gt;: the work item you dragged plus the seven that followed it.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Jira hasn't changed. Not yet. The new dates sit in your private draft, which the app saves for you and nobody else sees. Save puts them into the shared plan everyone sees, and only Apply writes them to Jira. I like it this way: I can try a date, look at what it does to the chain and throw it away.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fh57pfi6rzxdecwl3qpgb.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fh57pfi6rzxdecwl3qpgb.png" title="Right after the drag. Notice the strip under the tabs, the eight-change count in the plan header, and ITHELP-102's grey baseline line (its dates in the plan's saved baseline) to the left of its new bar. Production install on our demo site, 10 November 2026, version 6.19.0." alt="LeanZero Management plan after a drag: the strip Your change moved 7 work items with a Why did this move? button, Save (8) and Apply 8 changes in the plan header, and ITHELP-102 now finishing Jan 4, 2027" width="800" height="439"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;After the drag the plan's first card read "Late · at least 21 months". The demo plan was already 466 working days past its commitment (a date the plan promised someone, here "Helpdesk SLA Review" on Feb 10, 2027). One more week on the AV migration doesn't change that. On your own plan, I'd read that card after each drag. If your drag pushes a commitment, it says so there.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 4: Click Why did this move? to see each finish-to-start dependency
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;In the strip, select &lt;strong&gt;Why did this move?&lt;/strong&gt;. A dialog opens with one row per work item that moved.&lt;/li&gt;
&lt;li&gt;Read each row's second line. It names the date the work item now starts and the work item it waits for.&lt;/li&gt;
&lt;li&gt;Close the dialog with the × in its corner. Closing it changes nothing.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;You should see a first row like ours, with your own keys and dates:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;ITHELP-124 Automate mailing list surfaced in the postmortem  +5 wd
  now starts Jan 5, 2027 — can't begin until ITHELP-102 finishes Jan 4, 2027
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  Why did this move? A finish-to-start dependency in Jira, item by item
&lt;/h3&gt;

&lt;p&gt;Our dialog opened with "You rescheduled ITHELP-102 to Dec 30, 2026 → Jan 4, 2027 (was Dec 23, 2026 → Dec 28, 2026)", then "7 issues moved", then the seven rows. Each row read "+5 wd" with a line like "now starts Jan 5, 2027" followed by "can't begin until ITHELP-102 finishes Jan 4, 2027". So each work item in the chain starts on the first working day after the one before it finishes.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fj0rmvojs9a2q63sltk8u.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fj0rmvojs9a2q63sltk8u.png" title="The full explanation for one drag. Notice ITHELP-133: it now starts Monday Jan 25 because ITHELP-131 finishes Friday Jan 22, so the weekend is skipped. Demo site, 10 November 2026, 6.19.0." alt="Why did this move? dialog: ITHELP-102 rescheduled to Dec 30, 2026 to Jan 4, 2027, seven issues moved, each +5 wd with the work item it waits for" width="800" height="989"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;This list comes from the app's own schedule calculation, with no AI involved. The footer says "These facts are computed directly from the engine's cascade — nothing here changes your plan." The dialog and the Apply progress say "issues" where the strip says "work items". They're the same thing. It's also the screen I'd send a colleague who asks why their date moved.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 5: Click Apply 8 changes and review every date before it reaches Jira
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;In the plan header, select &lt;strong&gt;Apply 8 changes&lt;/strong&gt;. The &lt;strong&gt;Review changes&lt;/strong&gt; dialog opens, headed "8 changes will be written to Jira". Ours was ready in 0.2 seconds.&lt;/li&gt;
&lt;li&gt;Read the box at the top, &lt;strong&gt;What this does to your commitments&lt;/strong&gt;. Ours said "No commitment moves."&lt;/li&gt;
&lt;li&gt;Read &lt;strong&gt;Date changes 8/8&lt;/strong&gt;. Each row has a ticked checkbox and the Start and Due dates, the old one struck through and the new one beside it.&lt;/li&gt;
&lt;li&gt;Optional: to leave one work item as it is in Jira, untick its row. The count drops by one.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;I read the commitments box first. If it says a commitment moves, I'd stop and talk to whoever owns that date before pressing Apply.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Frdysakrm2bxfut8yz7n7.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Frdysakrm2bxfut8yz7n7.png" title="The review before anything is written. Notice the last row: ITHELP-149's due date goes from Feb 24 to Mar 3, 2027, five working days for the end of the chain. Demo site, 10 November 2026, 6.19.0." alt="Review changes dialog: No commitment moves, eight date rows for ITHELP-102 to ITHELP-149 with the old dates struck through, and buttons Discard all, Review with AI, Cancel and Apply 8 changes" width="800" height="1207"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;At the bottom are four buttons. &lt;strong&gt;Discard all&lt;/strong&gt; throws the eight changes away. &lt;strong&gt;Review with AI&lt;/strong&gt; asks the app's AI for a second read of the dates and appears only when AI is turned on in the app's settings (we didn't use it here). &lt;strong&gt;Cancel&lt;/strong&gt; closes the dialog and keeps your changes. &lt;strong&gt;Apply 8 changes&lt;/strong&gt; starts the write. I'd keep Review with AI for the bigger Applies, as a second opinion rather than a check: it reads up to 120 of the plan's rows, so on a plan like ours it doesn't see everything either.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 6: Apply the new start and due dates to Jira
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;In the review, select &lt;strong&gt;Apply 8 changes&lt;/strong&gt;. A progress dialog opens with four stages: &lt;strong&gt;Starting&lt;/strong&gt;, &lt;strong&gt;Writing&lt;/strong&gt;, &lt;strong&gt;Verifying&lt;/strong&gt; and &lt;strong&gt;Complete&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;Watch the line under the progress bar. It names each work item as it's written, for example "Writing ITHELP-133 · 4 of 8", and each finished key turns into a green chip.&lt;/li&gt;
&lt;li&gt;When the title says &lt;strong&gt;Applied&lt;/strong&gt; and "8 of 8 changes written to Jira", select &lt;strong&gt;Done&lt;/strong&gt;. The plan header goes back to "Saved" and the Apply button disappears.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;You should see something like this once the box under the stepper stops saying "Working out the plan's finish after this Apply…". The last line is our plan's finish; yours names your own plan's finish and commitment:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Applied
8 of 8 changes written to Jira
Plan now finishes Nov 23, 2028, at least 466 working days past Helpdesk SLA Review (Feb 10, 2027).
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F7txuxwsfxzsy6jnfvia8.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F7txuxwsfxzsy6jnfvia8.png" title="Caught at 38%, with 3 of 8 written. Notice the line under the bar: ITHELP-133 is being written as 4 of 8, and the green chips mark the work items already written. Demo site, 10 November 2026, 6.19.0." alt="Apply progress dialog: Writing to Jira, 3 of 8 issues written, stepper on Writing, 38%, Writing ITHELP-133 · 4 of 8, with ITHELP-102 and ITHELP-124 ticked" width="800" height="572"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;From the click to "Applied" took about 22 seconds. That sounds slow for eight work items. I'm fine with it, because the time goes on taking the lock, checking each work item before its write and reading all eight back after. Roughly 6 went on Starting, where the app takes a lock on the plan so nobody else can write it at the same time. The lock is renewed while the Apply runs, and frees itself 5 minutes after a writer's window disappears. About 11 went on Writing, around 1.3 seconds per work item. In the last 3 or so, Verifying, the app reads the eight work items back from Jira and refreshes its copy of the plan.&lt;/p&gt;

&lt;p&gt;Before each work item, the app asks Jira whether you may edit it and re-reads it. If its dates changed in Jira since you opened the review, it stops there. I think that check matters more than the speed. It writes as the app with notifications off, so Jira's history names the app and watchers get no email for each date.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F0fy6bkfosmcbig8xzgxd.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F0fy6bkfosmcbig8xzgxd.png" title="The end of the Apply. Notice the box under the stepper: the plan's finish after the write, Nov 23, 2028. Demo site, 10 November 2026, 6.19.0." alt="Applied dialog: 8 of 8 changes written to Jira, all four stages ticked, and a red Late (at least) box saying the plan now finishes Nov 23, 2028" width="800" height="492"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 7: Check that Jira holds the same dates as the plan
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;On the Timeline, click the dragged work item's bar. Its card opens.&lt;/li&gt;
&lt;li&gt;Read the dates line. Ours said "Dec 30, 2026 → Jan 4, 2027 · Jira holds the same dates · baseline Dec 28, 2026: +5 wd".&lt;/li&gt;
&lt;li&gt;Optional: on the card, select &lt;strong&gt;Open in Jira&lt;/strong&gt;. The work item opens in Jira.&lt;/li&gt;
&lt;li&gt;Optional: in Jira, read the Start date and Due date fields. They match the card. After a big Apply I'd open the last work item in the chain, ITHELP-149 here, since it's the date a sponsor asks about.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fmaliixxkn5qccmbhee69.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fmaliixxkn5qccmbhee69.png" title="The check after Apply. Notice Jira holds the same dates on the card, and the baseline note that records the five-day slip. Demo site, 10 November 2026, 6.19.0." alt="Bar card for ITHELP-102 after Apply: Dec 30, 2026 to Jan 4, 2027, Jira holds the same dates, baseline Dec 28, 2026 +5 wd" width="800" height="319"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;We also read all eight work items back from the Jira REST API right after Done. All 16 values matched the review row for row, ITHELP-102 at 2026-12-30 to 2027-01-04 and ITHELP-149 at 2027-02-24 to 2027-03-03. The plan's Duration field was empty on all eight before and after. The app doesn't write a Duration nobody typed.&lt;/p&gt;

&lt;p&gt;To check which version of the app the Marketplace serves today, ask its REST API. It should print three lines (you need curl and jq):&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;curl -s https://marketplace.atlassian.com/rest/2/addons/com.leanzero.jira.leanzeromanagement/versions/latest &lt;span class="o"&gt;|&lt;/span&gt; jq -r &lt;span class="s1"&gt;'.name, .release.date, .paymentModel'&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;





&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;6.19.0
2026-11-06
free
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  Undo a drag before Apply, and put dates back after it
&lt;/h2&gt;

&lt;p&gt;Before Apply, undo is easy. Use the undo arrow in the plan header, or Cmd+Z on a Mac and Ctrl+Z on Windows. The plan keeps the last 50 steps. If a single change moves more than 50 work items, a message "This moved N items." also appears with its own Undo button. Ours moved 7, so we didn't get it.&lt;/p&gt;

&lt;p&gt;After Apply, undo can't help: Apply, Discard all, a reload and a refresh of the plan all start the history over. I think that's right. The app's own answer is in its manual: "After a bad Apply, set the dates you want and apply again." Dragging the bar back five working days does that, and because each waiting work item sits exactly on the first day its blockers allow, the chain follows it back. We didn't test that route, so read the old and new dates in the review before you Apply. What we did test was the Jira route: put the old dates back in Jira in chain order, starting with the work item that slipped. That way plan protection never sees a work item start before the one it waits on. Then select &lt;strong&gt;Refresh from Jira now&lt;/strong&gt; from the &lt;strong&gt;⋯&lt;/strong&gt; menu at the right end of the plan header, next to Plan brief (not the Timeline toolbar's ⋯). We did that on our demo site with a script over the Jira REST API. Then we read all 24 values back (start, due and Duration for each), and 24 of 24 matched the dates from before the test. I'd like a one-click restore here, and I don't have one to show you.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fcwn297bafjhl850db99k.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fcwn297bafjhl850db99k.png" title="Illustration, generated locally with ERNIE-Image. After Apply the history starts over, so undo cannot take a drag back: you set the old dates and apply again, or put them back in Jira and refresh the plan. The undo button is taped down and the crossed-out one is already in the bin." alt="A blue robot pushes the first of eight coloured toy blocks back along a rail; a second robot presses a small yellow button next to a red button taped down beside a huge red lever labelled APPLY; a crossed-out red undo arrow lies in a wastebin; a third robot holds up a clipboard of tick marks against a solid green wall." width="800" height="448"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  If it didn't work
&lt;/h2&gt;

&lt;p&gt;You hover the bar and can't see the work items that wait on it. The hover card covers only that bar, and in the Everything view the waiting work items can be hundreds of rows away. Link lines show only after &lt;strong&gt;⋯&lt;/strong&gt; (Timeline toolbar), &lt;strong&gt;Show all connectors&lt;/strong&gt;. Drag anyway and read the list in Why did this move?.&lt;/p&gt;

&lt;p&gt;The Timeline is empty around the date you need. It only draws the rows near the part you're looking at, and Today jumps to today's date. Scroll down to the row first, then across to its dates.&lt;/p&gt;

&lt;p&gt;The Apply stopped with "ITHELP-131 Due date changed in Jira. Apply stopped before this issue was written." (with your own key and field). Someone edited that work item in Jira after you opened the review. The work items before it are already in Jira and stay there. Select &lt;strong&gt;End Apply here&lt;/strong&gt; (what's written stays in Jira), check the change in Jira, then select Apply again for the rest.&lt;/p&gt;

&lt;p&gt;"Your Jira account may not edit ITHELP-131 (Jira's Edit Issues permission), so nothing will be written for it." Your account lacks that permission on the work item (Schedule Issues when the plan writes Jira's Due date field). Ask your Jira admin, then select &lt;strong&gt;Resume saved Apply&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;"Jira could not confirm that your Jira account may edit ITHELP-131, so it was not written. Resume to try again." Jira didn't answer the permission check. Nothing was written for that work item. Select &lt;strong&gt;Resume saved Apply&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;"You do not have permission to perform this action." The Apply checks your plan role again, and you're no longer an Editor on this plan. Ask the plan's owner.&lt;/p&gt;

&lt;p&gt;"Jira did not retain Due date on ITHELP-131. Your intended schedule is retained." Jira accepted the write but read back a different value, so something in Jira changed it after the write. The Apply pauses and keeps your dates so you can find the cause and resume.&lt;/p&gt;

&lt;p&gt;An Apply isn't one transaction. If it stops at work item 4 of 8, the first three are in Jira and stay there, and the app never writes the same work item twice when you resume.&lt;/p&gt;

&lt;h2&gt;
  
  
  What it doesn't do
&lt;/h2&gt;

&lt;p&gt;A drag never writes to Jira; only Apply does. There's one exception, plan protection, which is on for a new plan. Say someone moves a work item's start in Jira to before its blocker finishes. The app puts the old start back and adds a comment headed "LeanZero Management: Date change reverted".&lt;/p&gt;

&lt;p&gt;It follows blocks links, including a link into an epic, which binds the work items under that epic. We tested one straight chain inside one project. A work item that waits on two others starts after the later of them, but our chain had no such fork, so this run doesn't show it. If your plan has forks, I'd try one drag and read Why did this move? before you Apply.&lt;/p&gt;

&lt;p&gt;We didn't test a buffer, and I'd have liked to show you one. A buffer is a work item you mark to absorb slip: its due date stays put and it shrinks until it's used up. The ITHELP plan has none, so the drag above passes straight through. The &lt;a href="https://dev.to/portfolio/leanzero-management"&gt;product page&lt;/a&gt; documents buffers, and the &lt;a href="https://dev.to/tutorials/jira-gantt-chart-critical-path-leanzero-management"&gt;critical path tutorial&lt;/a&gt; shows how to find the chain that sets your plan's finish before you start dragging.&lt;/p&gt;

&lt;h2&gt;
  
  
  What you have now
&lt;/h2&gt;

&lt;p&gt;[[takeaways]]&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;A slipped work item moved five working days on the Timeline, and the 7 work items that waited on it moved five working days each, with their lengths kept.&lt;/li&gt;
&lt;li&gt;A Why did this move? list with one line per moved work item and the work item it waits for.&lt;/li&gt;
&lt;li&gt;16 start and due dates reviewed, then written to Jira and read back in about 22 seconds.&lt;/li&gt;
&lt;li&gt;A bar card that says Jira holds the same dates as the plan.&lt;/li&gt;
&lt;li&gt;Not covered here: a work item with two blockers, and buffers.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;You moved one late work item on a Jira Gantt chart and the seven that depended on it moved with it, five working days each, with the weekend skipped and their lengths kept. You read why each one moved, checked all 16 dates before they reached Jira, wrote them in about 22 seconds, and confirmed Jira holds the same dates as the plan.&lt;/p&gt;

&lt;p&gt;My advice: open Why did this move? before you Apply. On a big plan it's the quickest way I know to see the whole chain at once, and it's where you'll catch the work item you didn't expect to move.&lt;/p&gt;




&lt;p&gt;Originally published on &lt;a href="https://leanzero.net/tutorials/jira-gantt-dependencies-leanzero-management?utm_source=devto&amp;amp;utm_medium=referral&amp;amp;utm_campaign=crosspost" rel="noopener noreferrer"&gt;leanzero.net&lt;/a&gt;. More Atlassian, Forge and local-AI write-ups at &lt;a href="https://leanzero.net/blog?utm_source=devto&amp;amp;utm_medium=referral&amp;amp;utm_campaign=crosspost" rel="noopener noreferrer"&gt;leanzero.net/blog&lt;/a&gt;, and if you're planning a migration or a Forge app, that's what we do: &lt;a href="https://leanzero.net/services?utm_source=devto&amp;amp;utm_medium=referral&amp;amp;utm_campaign=crosspost" rel="noopener noreferrer"&gt;leanzero.net/services&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>jira</category>
      <category>gantt</category>
      <category>projectmanagement</category>
      <category>forge</category>
    </item>
    <item>
      <title>Merge two Jira Cloud instances: Copy product data</title>
      <dc:creator>Mihai Perdum</dc:creator>
      <pubDate>Fri, 13 Nov 2026 09:00:48 +0000</pubDate>
      <link>https://dev.to/mihai_leanzero/merge-two-jira-cloud-instances-copy-product-data-294d</link>
      <guid>https://dev.to/mihai_leanzero/merge-two-jira-cloud-instances-copy-product-data-294d</guid>
      <description>&lt;p&gt;Someone asked on the Atlassian Community how to &lt;a href="https://community.atlassian.com/t5/Jira-questions/Merge-2-Atlassian-Cloud-Instances/qaq-p/798392" rel="noopener noreferrer"&gt;merge 2 Atlassian Cloud instances&lt;/a&gt;, and the thread had 10,283 views when I checked it on 13 November 2026. Atlassian's own help article on &lt;a href="https://confluence.atlassian.com/cloudkb/how-to-merge-two-jira-cloud-instances-691011863.html" rel="noopener noreferrer"&gt;how to merge two Jira Cloud instances&lt;/a&gt;, last changed on 7 March 2025, still says "Currently there is no way to do this in the JIRA Cloud interface" and sends you through a temporary Jira Server.&lt;/p&gt;

&lt;p&gt;That page is out of date. Atlassian has no merge button, but its Copy product data tool copies projects from one Jira Cloud site into another site that already has data, and adds to what's there instead of replacing it, with two exceptions: renamed Story and Epic types, and same-name groups, which merge. On 13 November 2026 we copied a 15-item test project between two of our sites with it. All 15 work items arrived with their keys unchanged and zero field differences. The automation rule didn't, and the copy took about 13 minutes although the screen promised under one.&lt;/p&gt;

&lt;p&gt;So I'd treat a merge of two Jira Cloud instances as a copy, done project by project, plus a short list of things you move by hand. This tutorial walks through the copy on real screens, lists what our run lost, and covers the Data Center case, where you merge a server into a Cloud site that is already in use.&lt;/p&gt;

&lt;p&gt;A word on names, because three are live at once. People search for "Copy product data". Atlassian Administration now shows a card called Copy app data, the page behind it is titled Data transfer, and the help page calls it &lt;a href="https://support.atlassian.com/organization-administration/docs/copy-jira-data/" rel="noopener noreferrer"&gt;Transfer Jira data&lt;/a&gt;. They're the same tool. Atlassian is also renaming "products" to "apps", and a Jira project is now a "space" in parts of the interface. I say project and work item throughout.&lt;/p&gt;

&lt;p&gt;[[steps]]&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Open Copy product data&lt;/strong&gt; (now Copy app data) in Atlassian Administration.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Create the transfer plan&lt;/strong&gt; and pick the source and destination sites.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Select the projects&lt;/strong&gt; to copy.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Choose what comes along&lt;/strong&gt; with the projects.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Validate the plan&lt;/strong&gt; and read every Check.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Copy the data&lt;/strong&gt; and wait for Complete.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Move what didn't copy&lt;/strong&gt; by hand.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Can you merge two Jira Cloud instances? What Atlassian offers in 2026
&lt;/h2&gt;

&lt;p&gt;As far as I can tell, you can't merge two sites into one in place. What you can do is copy one site's projects into the other and then retire the first. Atlassian's page on &lt;a href="https://support.atlassian.com/organization-administration/docs/what-product-data-is-copied/" rel="noopener noreferrer"&gt;what data is copied&lt;/a&gt; (updated 11 November 2026) describes it as transferring data "from one instance of your Atlassian app to another without overwriting any existing data", to "a new or an existing site within the same organization or in a different organization".&lt;/p&gt;

&lt;p&gt;An organization here is the top level in Atlassian Administration: it owns the sites and users, and it gets the bill. A site is one address like yourcompany.atlassian.net with its own Jira. If those two words still blur, our &lt;a href="https://leanzero.net/blog/atlassian-cloud-architecture-migration?utm_source=devto&amp;amp;utm_medium=referral&amp;amp;utm_campaign=crosspost" rel="noopener noreferrer"&gt;Atlassian Cloud architecture piece&lt;/a&gt; draws the map.&lt;/p&gt;

&lt;p&gt;It isn't new. It has been around since January 2024, when Atlassian &lt;a href="https://community.atlassian.com/forums/discussion/2542627/jira-cloud-to-cloud-migration-is-getting-a-new-home" rel="noopener noreferrer"&gt;moved Jira cloud-to-cloud migration into admin.atlassian.com&lt;/a&gt; and renamed it Copy product data. That post has 32,562 views. Atlassian's own help article predates it and still ranks for the question. People also try the cloud backup: in a December 2025 Community thread, someone couldn't find where to import their backup zip, and the answer was that the cloud backup "is NOT meant for site-to-site migration". A restore is the opposite of a merge: Atlassian's &lt;a href="https://support.atlassian.com/atlassian-cloud/kb/partial-or-selective-import-of-a-jira-backup-export-into-jira-cloud/" rel="noopener noreferrer"&gt;selective import page&lt;/a&gt; says it imports "overwriting all existing data".&lt;/p&gt;

&lt;p&gt;There's also an organization-level merge, where every app moves from one organization into another and the old organization is deleted. Atlassian changed that process this autumn. Its &lt;a href="https://support.atlassian.com/atlassian-cloud/kb/atlassian-organization-consolidation-guide/" rel="noopener noreferrer"&gt;consolidation guide&lt;/a&gt; (updated 16 September 2026) says new workflows, including self-service ones for eligible organizations, roll out in phases from 19 October to December 2026. Which one you get depends on your organization type. If your two Jira sites already sit in one organization, you only need the copy.&lt;/p&gt;

&lt;p&gt;After an acquisition the two sites usually sit in two organizations, and the copy still works across them. Atlassian's &lt;a href="https://support.atlassian.com/organization-administration/docs/before-you-start-copying-product-data/" rel="noopener noreferrer"&gt;before you start page&lt;/a&gt; says data moves "within or across organizations", and the destination list on our screen offered sites from two other organizations. You need one person who is an organization admin in both. Users who aren't on the destination yet are copied as their existing Atlassian accounts, and with &lt;strong&gt;Users with their groups&lt;/strong&gt; they count towards the destination's licence. I can't show the cross-organization user options from our run, because it stayed inside one organization, so those come from Atlassian's pages.&lt;/p&gt;

&lt;h2&gt;
  
  
  Before you start
&lt;/h2&gt;

&lt;blockquote&gt;
&lt;p&gt;Note&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Prerequisites&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Jira Cloud on any plan. Atlassian lists the feature for "All plans" on Atlassian Cloud and for Atlassian Government Cloud.&lt;/li&gt;
&lt;li&gt;One person who is an organization admin and a Jira admin (Atlassian calls it app admin) on both sites, and a user of both. The source and destination lists only show sites where you're an organization admin.&lt;/li&gt;
&lt;li&gt;Project keys that differ between the sites. A key that exists on both blocks that project.&lt;/li&gt;
&lt;li&gt;Time to finish within 14 days: a transfer plan expires 14 days after you create it.&lt;/li&gt;
&lt;li&gt;A destination on a paid plan if you'll copy more than 10 users with their groups: on a Free destination the copy stops, because Free allows 10 users.&lt;/li&gt;
&lt;li&gt;Jira Service Management (JSM) Premium or Enterprise on the destination if you copy Assets, the JSM database of things like laptops and contracts. Atlassian's &lt;a href="https://support.atlassian.com/organization-administration/docs/copy-assets-data/" rel="noopener noreferrer"&gt;Assets page&lt;/a&gt; says it won't copy Assets to Free or Standard.&lt;/li&gt;
&lt;li&gt;Our test: two Jira Cloud sites in one organization, a new company-managed Scrum project with 15 work items as the source, a site with one unrelated project as the destination.
When you're done you'll have the source project on the destination site with its work items, people, boards, filters and dashboards, and a list of what you still need to move by hand.&lt;/li&gt;
&lt;/ul&gt;
&lt;/blockquote&gt;

&lt;p&gt;Atlassian's &lt;a href="https://support.atlassian.com/organization-administration/docs/soft-limits-for-copying-jira-data/" rel="noopener noreferrer"&gt;limits page&lt;/a&gt; recommends batches of 200 projects per plan, and 100 GB of attachments per project (50 GB when both sites are in Europe). It lists no limit on the number of work items. Organizations with Units switched on get hard limits on top, such as fewer than 150,000 users and 60,000 groups. Ours doesn't use Units, so we didn't test those.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 1: Open Copy product data for Jira, now called Copy app data
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Go to &lt;strong&gt;admin.atlassian.com&lt;/strong&gt; and pick your organization if you have more than one. The organization overview opens.&lt;/li&gt;
&lt;li&gt;In the left menu, select &lt;strong&gt;Data management&lt;/strong&gt;. You'll see three cards: Backup and restore, &lt;strong&gt;Copy app data&lt;/strong&gt; and Manage sandboxes.&lt;/li&gt;
&lt;li&gt;On the &lt;strong&gt;Copy app data&lt;/strong&gt; card, select &lt;strong&gt;Start copying app data&lt;/strong&gt;. The &lt;strong&gt;Data transfer&lt;/strong&gt; page opens with your plans and a &lt;strong&gt;Create transfer plan&lt;/strong&gt; button.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fs1131ck0bzb2dsxadedx.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fs1131ck0bzb2dsxadedx.png" title="The entry point is the Copy app data card under Data management. The help page writes Data management, then Data transfer, which is the same place one click later." alt="Atlassian Administration, Data management page on 13 November 2026, with the Copy app data card and its Start copying app data button between Backup and restore and Manage sandboxes" width="799" height="389"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;You should see the &lt;strong&gt;Data transfer&lt;/strong&gt; page with its &lt;strong&gt;Create transfer plan&lt;/strong&gt; button.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 2: Create the transfer plan and pick source and destination
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;On &lt;strong&gt;Data transfer&lt;/strong&gt;, select &lt;strong&gt;Create transfer plan&lt;/strong&gt;. The &lt;strong&gt;How it works&lt;/strong&gt; page lists five stages, from selecting source and destination to reviewing and copying. Select &lt;strong&gt;Next&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;On &lt;strong&gt;Select an app&lt;/strong&gt;, select &lt;strong&gt;Jira&lt;/strong&gt;, then &lt;strong&gt;Next&lt;/strong&gt;. Confluence has its own transfer from the same screen.&lt;/li&gt;
&lt;li&gt;On &lt;strong&gt;Select source and destination&lt;/strong&gt;, pick the site to copy from in &lt;strong&gt;Select source&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;Pick the site to copy to in &lt;strong&gt;Select destination&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;Type a name in &lt;strong&gt;Name copy plan&lt;/strong&gt;. The screen checks it as you type and shows "Name available."&lt;/li&gt;
&lt;li&gt;In &lt;strong&gt;Choose migration stage&lt;/strong&gt;, pick &lt;strong&gt;Test&lt;/strong&gt; for a rehearsal or &lt;strong&gt;Production&lt;/strong&gt; for the real run.&lt;/li&gt;
&lt;li&gt;Select &lt;strong&gt;Next&lt;/strong&gt;.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;You should see the project list next. Our destination list also offered sites in two other organizations we administer, grouped by organization. That's how a copy between two organizations starts, and Atlassian says it needs the consent of the admins on both sides.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 3: Select the projects to copy
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;On &lt;strong&gt;Select projects&lt;/strong&gt;, find each project you want. Our list held 68 projects, each showing its work item count and an estimated copy time.&lt;/li&gt;
&lt;li&gt;Tick the project. Ours showed 15 work items, "0 KB" of attachments (a 56-byte file rounds to zero) and an estimate of "&amp;lt; 1 minute".&lt;/li&gt;
&lt;li&gt;Select &lt;strong&gt;Next&lt;/strong&gt; in the footer. The table's own pager also has a &lt;strong&gt;Next&lt;/strong&gt; button, which moves to the next page of projects. Use the one at the bottom right.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;You should see &lt;strong&gt;Select data you want to copy&lt;/strong&gt;, which opens with the user and group counts.&lt;/p&gt;

&lt;p&gt;Keys decide whether this step can work at all. Atlassian's &lt;a href="https://support.atlassian.com/organization-administration/docs/copy-jira-data/" rel="noopener noreferrer"&gt;Transfer Jira data&lt;/a&gt; page says "We can't copy projects with the same keys", and treats upper and lower case as the same. If both sites use the same key, rename one before you start, or that project stays behind. We checked our key MRG on both sites first: it didn't exist on either.&lt;/p&gt;

&lt;p&gt;To check a key yourself before you build the plan, search the destination's projects as a Jira admin. The search includes archived and trashed projects, and it returns only the keys that already exist. We ran it at 05:11 for our key and for KAN, a project the destination already has:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;curl -s -u &lt;span class="s2"&gt;"you@example.com:$API_TOKEN"&lt;/span&gt; \
  &lt;span class="s2"&gt;"https://&amp;lt;destination-site&amp;gt;.atlassian.net/rest/api/3/project/search?keys=MRG&amp;amp;keys=KAN&amp;amp;status=live&amp;amp;status=archived&amp;amp;status=deleted"&lt;/span&gt; \
  &lt;span class="o"&gt;|&lt;/span&gt; jq -r &lt;span class="s1"&gt;'.values[].key'&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;





&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;KAN
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;You should see only the keys that are already taken on the destination. Here KAN is taken and MRG is free, so MRG can copy. I'd still let Validate data have the final say.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 4: Choose users, groups, boards and dashboards
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;On &lt;strong&gt;Select data&lt;/strong&gt;, read the &lt;strong&gt;Users, groups, and teams&lt;/strong&gt; box first. Ours showed "59 users, 406 groups, and 3 teams" and the line "Your users exist in both the source and destination". There was nothing to choose there.&lt;/li&gt;
&lt;li&gt;Under &lt;strong&gt;Group memberships&lt;/strong&gt;, pick &lt;strong&gt;Users and groups separately&lt;/strong&gt; (the default) or &lt;strong&gt;Users with their groups&lt;/strong&gt;. The screen warns: "We merge groups with the same names. Some users in the destination may get unwanted permissions."&lt;/li&gt;
&lt;li&gt;Leave &lt;strong&gt;Customers and organizations&lt;/strong&gt;, &lt;strong&gt;Plans in Jira&lt;/strong&gt;, &lt;strong&gt;Dashboard&lt;/strong&gt; and &lt;strong&gt;Boards and filters&lt;/strong&gt; on the option that copies only what belongs to your selected projects. Ours found 1 dashboard and "1 board and 2 filters".&lt;/li&gt;
&lt;li&gt;Select &lt;strong&gt;Next&lt;/strong&gt;.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;You should see &lt;strong&gt;Validate data&lt;/strong&gt; start its checks.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fobsvzcue6w7o1yw3ypok.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fobsvzcue6w7o1yw3ypok.png" title="Both sites sat in one organization, so there were no users to copy. Same-name groups merge whichever option you pick; Users with their groups also adds the source's members to them." alt="The Select data step on 13 November 2026: 59 users, 406 groups and 3 teams already in both sites, and the group memberships choice with the warning that groups with the same names merge" width="800" height="600"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Same-name groups are where it can hurt, and the option doesn't switch that off. Atlassian's &lt;a href="https://support.atlassian.com/organization-administration/docs/understand-how-permissions-can-change-when-copying-groups/" rel="noopener noreferrer"&gt;page on group permissions&lt;/a&gt; uses a merge of two sites as its example: a merged group keeps the source group's project permissions and also gets the destination group's app and project permissions. With &lt;strong&gt;Users with their groups&lt;/strong&gt;, people who were only in the source group join too. Re-runs only add. I'd run the collision audit from our &lt;a href="https://leanzero.net/blog/migrate-jira-users-groups-same-name-merge?utm_source=devto&amp;amp;utm_medium=referral&amp;amp;utm_campaign=crosspost" rel="noopener noreferrer"&gt;same-name groups piece&lt;/a&gt; before the first copy. It takes minutes. Atlassian's &lt;a href="https://support.atlassian.com/organization-administration/docs/manage-blocklisted-groups-and-their-users/" rel="noopener noreferrer"&gt;blocklist page&lt;/a&gt; names four admin groups that are never copied (site-admins, system-administrators, atlassian-addons and Atlassian-addons-admin), but any other group that grants admin rights is.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 5: Validate the plan and read every Check
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;On &lt;strong&gt;Validate data&lt;/strong&gt;, wait for the checks. The plan is created at this point, and it expires 14 days later.&lt;/li&gt;
&lt;li&gt;Read each row. &lt;strong&gt;Fix&lt;/strong&gt; must be solved before you can copy, &lt;strong&gt;Check&lt;/strong&gt; is a warning, &lt;strong&gt;Ready&lt;/strong&gt; is fine.&lt;/li&gt;
&lt;li&gt;Select &lt;strong&gt;Next&lt;/strong&gt; to reach &lt;strong&gt;Review your selections&lt;/strong&gt;. Ours said "Saved - You can now copy your data."&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Validation took about 40 seconds on our plan. The screen listed 14 checks: 13 Ready and one Check, which said two marketplace or custom apps on the source were missing on the destination.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F4qvwym2tseqife0759js.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F4qvwym2tseqife0759js.png" title="One Check, and its list of apps to install came up empty in our capture. Note which apps the source runs before you trust this screen." alt="Validate data on 13 November 2026: Ready on users, projects, boards, filters and public access, and one Check for marketplace and custom apps missing on the destination, with an empty install list" width="800" height="630"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Oddly, the list of apps under that Check was empty in our capture, and the install link opens the destination's app manager. Atlassian is plain about app data: "We don't migrate Marketplace app data yet", and it asks you to contact each app's vendor. I'd install the same apps on the destination before the copy. Otherwise links to app data won't resolve.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 6: Copy the data and wait it out
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;On &lt;strong&gt;Review your selections&lt;/strong&gt;, select &lt;strong&gt;Copy data&lt;/strong&gt;. There's no confirmation dialog: the copy starts on the click.&lt;/li&gt;
&lt;li&gt;Watch the status move from &lt;strong&gt;Copying&lt;/strong&gt; to &lt;strong&gt;Complete&lt;/strong&gt;. Atlassian's page lists five statuses, Incomplete among them, and our screen said Copying where the page says Running. Incomplete means some projects copied and some didn't.&lt;/li&gt;
&lt;li&gt;Open the destination site.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;You should see the plan's status read &lt;strong&gt;Complete&lt;/strong&gt; and your project in the destination's project list.&lt;/p&gt;

&lt;p&gt;We clicked &lt;strong&gt;Copy data&lt;/strong&gt; at 04:21:50 Eastern European Time. The project row sat at 0% for about ten minutes, jumped to 100%, and the plan showed Complete at 04:34. So about 13 minutes for 15 work items, against "&amp;lt; 1 minute" on the same screen. I wouldn't plan a cutover on that estimate.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F5sxorz1zg8yafliofqwb.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F5sxorz1zg8yafliofqwb.png" title="Complete, 16 minutes after the plan was made. Read the Created and Completed times; the Time taken field said 20,771 days." alt="Review your selections after the copy on 13 November 2026: status Complete, 1 project, 15 work items, created 04:18, completed 04:34, and Time taken 20,771 days" width="800" height="619"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;The completed plan says "Time taken 20,771 days". That's about 57 years, roughly the time since 1 January 1970, so I think it's a duration counted from zero. Use your own clock. We also found no report to download, though the validation screen tells you to download one after the copy. It may only appear when something fails. Our run had no errors, so I can't say.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fxqxw18827s51szzo0338.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fxqxw18827s51szzo0338.png" title="Illustration, generated locally with ERNIE-Image. The completed plan reports Time taken 20,771 days, about 57 years, roughly the time since 1 January 1970, and we found no report to download, though the validation screen tells you to get one afterwards. The robot had time to grow a cobweb, and the mail slot stayed empty." alt="A robot asleep and cobwebbed at a desk beside a large hourglass, while a second robot holds a clipboard, under a row of calendar pages and a red arrow pointing at an empty mail slot." width="800" height="448"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Then the destination showed a yellow banner: "For up to 12 hours, filters, reports, JQL, attachments and some other searches might not show every item." I'd plan the checks around that and not announce the move on the hour the copy finishes.&lt;/p&gt;

&lt;h2&gt;
  
  
  What gets migrated in a Jira cloud to cloud migration, and what our run lost
&lt;/h2&gt;

&lt;p&gt;We checked the destination over the REST API (Jira's programming interface) at 04:36, against the source, field by field.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;item&lt;/th&gt;
&lt;th&gt;what Atlassian says&lt;/th&gt;
&lt;th&gt;what happened in our run&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;project key&lt;/td&gt;
&lt;td&gt;kept&lt;/td&gt;
&lt;td&gt;MRG kept, with a new internal project id&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;15 work items (1 epic, 11 stories, 3 bugs)&lt;/td&gt;
&lt;td&gt;copied&lt;/td&gt;
&lt;td&gt;15 of 15, keys MRG-1 to MRG-15 identical, 0 field differences&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;select custom field on all 15&lt;/td&gt;
&lt;td&gt;copied&lt;/td&gt;
&lt;td&gt;recreated with a new field id, all 15 values match&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;3 comments, 1 attachment, 1 Blocks link&lt;/td&gt;
&lt;td&gt;copied&lt;/td&gt;
&lt;td&gt;3 of 3 with the same author, 1 of 1, link present&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;epic parent on 14 children&lt;/td&gt;
&lt;td&gt;copied&lt;/td&gt;
&lt;td&gt;present on all 14&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;board and sprints&lt;/td&gt;
&lt;td&gt;copied&lt;/td&gt;
&lt;td&gt;board copied, every sprint with its name and state, the active one included&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;2 filters&lt;/td&gt;
&lt;td&gt;copied&lt;/td&gt;
&lt;td&gt;2 of 2, JQL using the custom field by name still works&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;dashboard&lt;/td&gt;
&lt;td&gt;copied&lt;/td&gt;
&lt;td&gt;1 of 1, gadget present (our test set the wrong gadget's settings, so this run can't say whether gadget settings copy)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;automation rule&lt;/td&gt;
&lt;td&gt;not copied&lt;/td&gt;
&lt;td&gt;not copied: 0 rules on the destination&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;people&lt;/td&gt;
&lt;td&gt;linked to existing accounts&lt;/td&gt;
&lt;td&gt;the same Atlassian account on every assignee, reporter, comment and lead&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fdshw0nkyvm7tgsau12k5.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fdshw0nkyvm7tgsau12k5.png" title="The board on the destination right after the copy, under the 12-hour refresh banner. Keys and people match the source." alt="The copied MRG board on the destination site, 13 November 2026, with the 12-hour refresh banner on top and the same work item keys, labels and epic as the source" width="800" height="350"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;To check the automation side yourself, ask the Automation REST API for the destination's rule list. You need the site's cloudId, which &lt;code&gt;https://&amp;lt;your-site&amp;gt;.atlassian.net/_edge/tenant_info&lt;/code&gt; prints. We ran this again at 04:52, after deleting the test project:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;curl -s -u &lt;span class="s2"&gt;"you@example.com:$API_TOKEN"&lt;/span&gt; \
  &lt;span class="s2"&gt;"https://api.atlassian.com/automation/public/jira/&amp;lt;destination-cloudId&amp;gt;/rest/v1/rule/summary?limit=100"&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;





&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;{"links":{"self":null,"next":null,"prev":null},"data":[]}
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;You should see an empty &lt;code&gt;data&lt;/code&gt; list, which means no rules on the destination. The same call against our source site returned 85 rules on its first page, so the call works and the destination really is empty.&lt;/p&gt;

&lt;p&gt;People came across without a single new account. Atlassian's &lt;a href="https://support.atlassian.com/organization-administration/docs/manage-users-and-groups-when-you-copy-product-data/" rel="noopener noreferrer"&gt;users page&lt;/a&gt; says it doesn't create new accounts. It links every user's data to their existing Atlassian account. Every person is identified by an accountId, a fixed ID that belongs to the person and not to the site, so the assignee on MRG-4 was the same account on both sites.&lt;/p&gt;

&lt;p&gt;I'd check your dashboard gadgets after the copy. Our setup script wrote Filter results settings onto a Starred filters gadget by mistake, so this run says nothing either way about gadget settings.&lt;/p&gt;

&lt;p&gt;Atlassian's list of what isn't copied is longer than one test project can show. In a merge I'd watch these lines from its &lt;a href="https://support.atlassian.com/organization-administration/docs/what-product-data-is-copied/" rel="noopener noreferrer"&gt;what data is copied page&lt;/a&gt;. Automation flows don't move, project-level ones included. Neither do global permissions or general configuration such as time zone and language. Apps and app data stay behind, so do comment reactions, and a moved work item's old key won't redirect. Confluence links keep pointing to the source site. JSM loses its email settings, for one. Plans in Jira lose their scenarios and saved views.&lt;/p&gt;

&lt;p&gt;Links someone pasted as a URL in a comment or description keep pointing at the old site. Atlassian says so on the &lt;a href="https://support.atlassian.com/organization-administration/docs/copy-jira-data/" rel="noopener noreferrer"&gt;Transfer Jira data&lt;/a&gt; page and recommends keeping the source for a few months before you cancel it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Same-name custom fields and schemes come back marked (migrated)
&lt;/h2&gt;

&lt;p&gt;Because Copy product data doesn't replace existing configuration, a clash creates a second copy. Atlassian's &lt;a href="https://support.atlassian.com/organization-administration/docs/how-data-is-linked-between-instances/" rel="noopener noreferrer"&gt;linking page&lt;/a&gt; says an entity with the same name as one on the destination arrives as a new one with a "(migrated)" tag. The next clash gets "(migrated 2)". Some entities, statuses and priorities among them, merge instead, but only when they're identical (a priority merges only if its name and its colour match).&lt;/p&gt;

&lt;p&gt;In a merge of two working sites, I'd expect two "Story Points" fields or two "Default notification scheme" entries. A Community user posted exactly that in July 2026: "Default notification scheme ---&amp;gt; Default notification scheme (Migrated)". Atlassian's fix request, &lt;a href="https://jira.atlassian.com/browse/JRACLOUD-82762" rel="noopener noreferrer"&gt;JRACLOUD-82762&lt;/a&gt;, has 127 votes and is In Progress. I'd probably rename the clashing fields on one side before the copy. The other option is to accept the (migrated) copies and clean them up afterwards, but decide before you start.&lt;/p&gt;

&lt;p&gt;One documented exception changes what's already on the destination. If the source renamed its Story or Epic work type, the copy renames the destination's own Story and Epic types to the source's names, and the new names show in every company-managed project on the destination that uses those types. &lt;a href="https://support.atlassian.com/organization-administration/docs/manage-story-and-epic-issue-types-during-copy-product-data/" rel="noopener noreferrer"&gt;Atlassian's Story and Epic page&lt;/a&gt; gives two ways out: before the copy, move the source's items to a new standard work type, or after it, rename the destination's types back. I'd check the source's work type names first. It's a two-minute look.&lt;/p&gt;

&lt;p&gt;Re-running the same plan isn't a sync. Atlassian documents no incremental copy of work items, and a project key already on the destination blocks it. To copy a project again, you remove it from the destination first. With the 14-day plan expiry on top, the safe pattern is a rehearsal on a test site that carries the destination's configuration, so the (migrated) clashes show up there, then one production copy behind a freeze. Our &lt;a href="https://leanzero.net/tutorials/make-jira-cloud-projects-read-only-migration-cutover?utm_source=devto&amp;amp;utm_medium=referral&amp;amp;utm_campaign=crosspost" rel="noopener noreferrer"&gt;read-only projects tutorial&lt;/a&gt; covers the freeze.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 7: Move automation rules, global permissions and app data by hand
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;On the source, go to &lt;strong&gt;Jira settings&lt;/strong&gt;, &lt;strong&gt;System&lt;/strong&gt;, &lt;strong&gt;Automation flows&lt;/strong&gt;, then &lt;strong&gt;More actions&lt;/strong&gt; and &lt;strong&gt;Export flows&lt;/strong&gt;. Atlassian says you must be a global administrator. The file must be 5 MB or smaller.&lt;/li&gt;
&lt;li&gt;On the destination, import the file from the same menu. Every imported flow arrives disabled, and a name that already exists becomes "Copy of" plus the name.&lt;/li&gt;
&lt;li&gt;Check each rule's actor (the account the rule runs as) and project scope on the destination, then enable the rules one at a time.&lt;/li&gt;
&lt;li&gt;Recreate global permissions and general settings by hand from the source's settings pages.&lt;/li&gt;
&lt;li&gt;Ask each app vendor how their data moves, and do it after the copy.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;You should see your rules on the destination, disabled, with owners that exist there. Atlassian's &lt;a href="https://support.atlassian.com/cloud-automation/docs/import-and-export-jira-automation-rules/" rel="noopener noreferrer"&gt;import and export page&lt;/a&gt; says owners need no change in the file for a Cloud to Cloud move, as long as those users are on the destination. The same page warns that import and export from Server or Data Center is supported only for one-to-one moves. That warning sits under the Server bullet, and it adds that a Cloud to Cloud move "is more likely to be successful". I'd still test it on a copy first.&lt;/p&gt;

&lt;p&gt;The failure we see most often on rules is the actor: a rule whose actor isn't on the destination fails to create with “The selected actor does not exist”. Our &lt;a href="https://leanzero.net/tutorials/jira-automation-rules-migration-actor-scope?utm_source=devto&amp;amp;utm_medium=referral&amp;amp;utm_campaign=crosspost" rel="noopener noreferrer"&gt;automation rules piece&lt;/a&gt; covers that error and the scope one. There's no REST API for Copy product data itself (&lt;a href="https://jira.atlassian.com/browse/CLOUD-12155" rel="noopener noreferrer"&gt;CLOUD-12155&lt;/a&gt; is still gathering interest), so a scripted copy goes through the normal Jira and automation APIs.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fopssaca374f5u0haov2a.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fopssaca374f5u0haov2a.png" title="Illustration, generated locally with ERNIE-Image. Automation rules don't come across with the copy, so you export and import them, and the failure we see most often there is the actor: a rule whose actor is not on the destination fails to create with “The selected actor does not exist”. The actor did not make it across the plank." alt="A robot with a stack of rule cards stands at one end of a plank between two floating islands while a small robot falls off the plank into the gap; on the far island a uniformed robot waits beside a red button and a clipboard of checkboxes crossed out with a red X." width="800" height="448"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Migrate Jira Data Center to cloud into a site that already has data
&lt;/h2&gt;

&lt;p&gt;The other merge is a Jira Data Center server joining a Cloud site that's already in use. The tool is JCMA (the Jira Cloud Migration Assistant, an app you install on the server), and it promises the same thing: Atlassian's &lt;a href="https://support.atlassian.com/migration/docs/what-gets-migrated-with-the-jira-cloud-migration-assistant/" rel="noopener noreferrer"&gt;JCMA page&lt;/a&gt; says it "adds data to a Jira Cloud site without overwriting any existing data". Both routes create "(migrated)" copies of clashing configuration. The differences are where your plan changes:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;question&lt;/th&gt;
&lt;th&gt;Data Center to Cloud (JCMA)&lt;/th&gt;
&lt;th&gt;Cloud to Cloud (Copy product data)&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;how people are matched&lt;/td&gt;
&lt;td&gt;by email address; a cloud account with the same email wins&lt;/td&gt;
&lt;td&gt;the person's existing Atlassian account, no matching&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;same-name groups&lt;/td&gt;
&lt;td&gt;members join the existing cloud group&lt;/td&gt;
&lt;td&gt;groups merge; options decide memberships&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;what blocks a project&lt;/td&gt;
&lt;td&gt;the same project name or key on the destination&lt;/td&gt;
&lt;td&gt;the same key, case-insensitive; old keys can also clash (&lt;a href="https://jira.atlassian.com/browse/CLOUD-11750" rel="noopener noreferrer"&gt;CLOUD-11750&lt;/a&gt;)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;automation rules&lt;/td&gt;
&lt;td&gt;migrated, disabled after migration, actors not migrated&lt;/td&gt;
&lt;td&gt;not copied; export and import&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;where you run it&lt;/td&gt;
&lt;td&gt;the app on your server&lt;/td&gt;
&lt;td&gt;Atlassian Administration&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;One thing does get overwritten on the Data Center side. If you migrate automation flows a second time, Atlassian's &lt;a href="https://support.atlassian.com/migration/docs/how-to-migrate-automation-rules/" rel="noopener noreferrer"&gt;automation migration page&lt;/a&gt; says the Data Center versions replace the Cloud copies, edits included.&lt;/p&gt;

&lt;p&gt;Email matching is the other trap there, and the one I'd fix first. Atlassian's &lt;a href="https://support.atlassian.com/migration/docs/migrate-users-and-groups/" rel="noopener noreferrer"&gt;users and groups page&lt;/a&gt; says a user whose email already exists in the cloud site isn't migrated, and their username isn't updated. Two people who share an old address, or one person with two addresses, become a data clean-up before the migration. On Cloud to Cloud that question doesn't come up.&lt;/p&gt;

&lt;p&gt;Atlassian's &lt;a href="https://support.atlassian.com/atlassian-cloud/kb/project-name-and-project-key-conflict-when-migrating-using-jira-cloud-migration-assistant-jcma/" rel="noopener noreferrer"&gt;key conflict page&lt;/a&gt; also advises renaming the project on the source when names or keys clash, because "Changing a project key is more impactful and should be avoided if possible." Old keys matter too: on Cloud to Cloud, an open Atlassian ticket (&lt;a href="https://jira.atlassian.com/browse/CLOUD-11750" rel="noopener noreferrer"&gt;CLOUD-11750&lt;/a&gt;) says a historical key that matches one used on the destination can leave a project half-copied with nothing in the report to explain it. Check old keys on both sides when either site has renamed projects.&lt;/p&gt;

&lt;p&gt;The March 2025 help page's advice, merging through a temporary Jira Server and re-importing, belongs to neither route. I wouldn't use it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Does merging pool your Rovo credits and automation steps?
&lt;/h2&gt;

&lt;p&gt;Only when the two sites sit in different organizations. Atlassian's usage pages (read 13 November 2026) say allowances for &lt;a href="https://support.atlassian.com/rovo/docs/rovo-usage-limits/" rel="noopener noreferrer"&gt;Rovo credits&lt;/a&gt; and &lt;a href="https://support.atlassian.com/cloud-automation/docs/how-is-my-usage-calculated/" rel="noopener noreferrer"&gt;automation steps&lt;/a&gt; are "pooled at the organization level", and usage-based billing starts on 3 December 2026. Two sites in one organization already share that pool, so copying one into the other changes nothing there. Sites in two organizations draw on two separate pools. Atlassian doesn't name pooling as a reason to merge; that's my reading of its pages.&lt;/p&gt;

&lt;p&gt;What a merge inside one organization does save is the second subscription. Atlassian's &lt;a href="https://support.atlassian.com/organization-administration/docs/understand-how-copying-affects-your-billing/" rel="noopener noreferrer"&gt;billing page&lt;/a&gt; says you keep paying for both sites until you change the source, and suggests moving the source to Free when you no longer need it.&lt;/p&gt;

&lt;h2&gt;
  
  
  If it didn't work
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;The site isn't in the source or destination list.&lt;/strong&gt; You're not an organization admin of that site's organization. Fix the role, or get the person who is admin in both.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;"Project already exist in Destination"&lt;/strong&gt; on validation: the key, in any case, exists on the destination. Rename it on one side or remove it from the plan.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The copy won't start on a Free destination.&lt;/strong&gt; You picked &lt;strong&gt;Users with their groups&lt;/strong&gt; with more than 10 users. Upgrade the destination, or pick &lt;strong&gt;Users and groups separately&lt;/strong&gt;, where Atlassian says copied users don't take a licence.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Work items are missing from a filter or JQL search after the copy.&lt;/strong&gt; The destination is still refreshing. Atlassian's banner says up to 12 hours.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Links to work items show "Failed to load".&lt;/strong&gt; Application links aren't copied. Atlassian's &lt;a href="https://support.atlassian.com/organization-administration/docs/resolve-issue-and-page-links-after-copying-jira-cloud-data/" rel="noopener noreferrer"&gt;link fixing page&lt;/a&gt; covers the repair, which needs an organization admin and Atlassian Guard Standard.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A rule fails on import with "The selected actor does not exist".&lt;/strong&gt; The rule's actor isn't on the destination. Change the actor or add the user, then import again.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The plan disappeared or won't run.&lt;/strong&gt; Plans expire 14 days after creation, and an expired plan can't be edited, run or viewed. Create a new one.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  What you have now, and what I'd do
&lt;/h2&gt;

&lt;p&gt;[[takeaways]]&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;What you have.&lt;/strong&gt; The source project and its work items on the destination with the same keys, while the source site keeps running.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;What to check on yours.&lt;/strong&gt; The work item count per project on both sites after the 12-hour refresh, and the automation rule summary on the destination.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;What this doesn't cover.&lt;/strong&gt; What didn't copy (Step 7), and a copy between two organizations, because our run stayed inside one. The Data Center route is JCMA, covered above.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;For two sites, I'd run the copy twice: once as a rehearsal on a test site that carries the destination's configuration, and once for real after a freeze, then export the automation rules the same hour. For a Data Center server joining a live Cloud site, clean up email addresses before JCMA runs, because that's the step you can't undo by copying again. If you've run a merge across two organizations, I'd like to hear how users and licences came out on the Community.&lt;/p&gt;




&lt;p&gt;Originally published on &lt;a href="https://leanzero.net/tutorials/merge-two-jira-cloud-instances?utm_source=devto&amp;amp;utm_medium=referral&amp;amp;utm_campaign=crosspost" rel="noopener noreferrer"&gt;leanzero.net&lt;/a&gt;. More Atlassian, Forge and local-AI write-ups at &lt;a href="https://leanzero.net/blog?utm_source=devto&amp;amp;utm_medium=referral&amp;amp;utm_campaign=crosspost" rel="noopener noreferrer"&gt;leanzero.net/blog&lt;/a&gt;, and if you're planning a migration or a Forge app, that's what we do: &lt;a href="https://leanzero.net/services?utm_source=devto&amp;amp;utm_medium=referral&amp;amp;utm_campaign=crosspost" rel="noopener noreferrer"&gt;leanzero.net/services&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>jira</category>
      <category>atlassian</category>
      <category>migration</category>
      <category>cloud</category>
    </item>
    <item>
      <title>Jira Automation with Rovo: 2 of 10 Rules Worked</title>
      <dc:creator>Mihai Perdum</dc:creator>
      <pubDate>Fri, 13 Nov 2026 05:58:59 +0000</pubDate>
      <link>https://dev.to/mihai_leanzero/jira-automation-with-rovo-2-of-10-rules-worked-2ndk</link>
      <guid>https://dev.to/mihai_leanzero/jira-automation-with-rovo-2-of-10-rules-worked-2ndk</guid>
      <description>&lt;p&gt;We gave Create with Rovo 10 automation requests on our Jira Premium test site on 13 November 2026, and 2 of the rules it built worked as built. Seven needed edits and one couldn't be switched on at all. Each message to Rovo cost about 10 Rovo credits, and a rule that ran and did its job cost 3 or 4 automation steps per run.&lt;/p&gt;

&lt;p&gt;The reason to test it now is a request on Atlassian's tracker. On 4 June 2026 Scott Boisvert commented on &lt;a href="https://jira.atlassian.com/browse/JRACLOUD-98402" rel="noopener noreferrer"&gt;JRACLOUD-98402&lt;/a&gt;, which asks to bring back the "Create flows quickly with Rovo" box in Jira automation: "This is major impact to organizations that limit the use of Studio to a small group of users." By 13 November that request had 24 votes and 19 watchers, and a new Create with Rovo button was back under &lt;strong&gt;Create flow&lt;/strong&gt;. The flows it builds live in Rovo Studio, where Atlassian's docs say every Studio user can create flows by default, and the drafts we got were editable by all Studio users.&lt;/p&gt;

&lt;p&gt;Rovo is still useful. It picked a sensible trigger in 9 of 10 drafts, asked a good question when it couldn't find a Confluence space, and wrote down its assumptions when the request was vague. But two drafts would have failed silently: one ran twice and did nothing, and one would send an empty email every Monday. I think that matters more than the score.&lt;/p&gt;

&lt;p&gt;A note on words. Atlassian now calls an automation rule a &lt;strong&gt;flow&lt;/strong&gt;, a project a &lt;strong&gt;space&lt;/strong&gt; and an issue a &lt;strong&gt;work item&lt;/strong&gt;, and I'll use the names the screens use. &lt;strong&gt;Rovo Studio&lt;/strong&gt; is Atlassian's separate app for building agents and automations with Rovo. &lt;strong&gt;Rovo credits&lt;/strong&gt; are the units Atlassian bills Rovo's AI work in.&lt;/p&gt;

&lt;h2&gt;
  
  
  Rovo got the triggers right and the details wrong: 6 findings
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;2 of 10 drafts worked as built.&lt;/strong&gt; Rovo refused nothing and asked one clarifying question. Seven drafts used a wrong component, field or smart value, and one was blocked by the editor.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Generating costs Rovo credits.&lt;/strong&gt; Our org meter moved 10 credits per message, 140 credits over 14 messages. We found no Atlassian page that says whether generating a flow is billed.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Running costs automation steps at the usual rate.&lt;/strong&gt; A run that acted cost 3 or 4 steps. Runs that stopped at a condition cost nothing.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The worst draft gave no error.&lt;/strong&gt; The "close the parent when all sub-tasks are done" flow ran twice and never moved the parent.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Rovo doesn't check your space's setup.&lt;/strong&gt; Its drafts named a "Closed" status our space doesn't have and searched by the old Epic Link field.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Flows live in Rovo Studio,&lt;/strong&gt; and the drafts we got were set so that &lt;strong&gt;All Studio users&lt;/strong&gt; can edit them.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Where Create with Rovo is in Jira automation now, and why it disappeared in May
&lt;/h2&gt;

&lt;p&gt;In May 2026, with the general release of Studio V2 (the current version of Rovo Studio), the old in-product Create with Rovo button "was intentionally deprecated", as the tracker &lt;a href="https://jira.atlassian.com/browse/AUTO-2376" rel="noopener noreferrer"&gt;AUTO-2376&lt;/a&gt; puts it. From 17 August to 28 September the weekly Cloud release notes listed "Build automation rules with Rovo" as rolling out, and on 1 September Sophia Do from the Automation team &lt;a href="https://community.atlassian.com/forums/discussion/3283328/introducing-create-with-rovo-for-automation" rel="noopener noreferrer"&gt;announced it on the Community&lt;/a&gt;: "The flows you build will live in Rovo Studio, but you can view and access them from your Product Automation Flows List."&lt;/p&gt;

&lt;p&gt;You need Jira Cloud on Standard, Premium or Enterprise with Rovo turned on for Jira, and access to Rovo Studio. Atlassian says Rovo isn't available for Jira in its Government environment. The release notes last listed the button as rolling out, so it may not be on your site yet. On our site, on 13 November 2026, this is where it was:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;In your Jira space, open &lt;strong&gt;Space settings&lt;/strong&gt; and select &lt;strong&gt;Automation&lt;/strong&gt;. A purple banner says "Automation is now available in Rovo Studio".&lt;/li&gt;
&lt;li&gt;Select &lt;strong&gt;Create flow&lt;/strong&gt;. A menu opens with &lt;strong&gt;Create with Rovo&lt;/strong&gt;, &lt;strong&gt;Create from scratch&lt;/strong&gt; and &lt;strong&gt;Create from template&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;Select &lt;strong&gt;Create with Rovo&lt;/strong&gt;. The box "Automate work in minutes with Rovo" opens, with the footer "Uses AI. Verify results."&lt;/li&gt;
&lt;li&gt;Describe the rule. Rovo plans it in the chat and then offers &lt;strong&gt;Build flow in Studio&lt;/strong&gt;, which Atlassian's doc says opens the draft in Rovo Studio in a new tab.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F7me9mlcoaunr84y6g3e1.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F7me9mlcoaunr84y6g3e1.png" title="Space settings &gt; Automation on our test site, 13 November 2026. Create with Rovo is the first item under Create flow. The yellow template card underneath offers 'When all child issues are completed then close parent', which comes up again below." alt="Jira space settings Automation page with the Create flow menu open, showing Create with Rovo, Create from scratch and Create from template, under a purple banner saying Automation is now available in Rovo Studio." width="800" height="556"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;For us that hand-off failed twice, with "Invoke action failed because unknown error" in the chat. We were driving a headless browser, so you may not see it in a normal one. The second route worked in all our tries: in Rovo Studio, select &lt;strong&gt;Create&lt;/strong&gt; at the top and type into "Describe your idea or problem, Rovo Studio will build it". All 10 drafts below come from there. The same Jira menu is also in global automation (&lt;strong&gt;Jira settings &amp;gt; Automation&lt;/strong&gt;).&lt;/p&gt;

&lt;p&gt;If your users say the button "disappeared", check AI access first. Atlassian's &lt;a href="https://support.atlassian.com/organization-administration/docs/manage-rovo-access/" rel="noopener noreferrer"&gt;Manage Rovo access&lt;/a&gt; page says Create with Rovo stays available "as long as any Jira app on that site still has Rovo enabled". We blocked Rovo for our Jira app for about three minutes and the button was still there. Our article on &lt;a href="https://leanzero.net/blog/disable-rovo-jira-confluence?utm_source=devto&amp;amp;utm_medium=referral&amp;amp;utm_campaign=crosspost" rel="noopener noreferrer"&gt;disabling Rovo in Jira and Confluence&lt;/a&gt; walks through that blocklist.&lt;/p&gt;

&lt;h2&gt;
  
  
  We tested 10 requests in a fresh Jira space
&lt;/h2&gt;

&lt;p&gt;We made a company-managed Kanban space called RVAT, with the statuses Backlog, Selected for Development, In Progress and Done. We typed each request into Rovo Studio, signed in as an org admin, and read each draft in the flow editor component by component. A draft "worked as built" if it did what we asked with no change. It "needs edits" if it had a wrong component, field, status or smart value (a &lt;strong&gt;smart value&lt;/strong&gt; is a placeholder like &lt;code&gt;{{issue.key}}&lt;/code&gt; that automation fills in when it runs). And "can't be enabled" means the editor refused it.&lt;/p&gt;

&lt;p&gt;We published three drafts, triggered each one by creating and moving real work items, and read the result on the work items and in the Studio audit log. A plan took 97 to 129 seconds to appear, and about 23 seconds of that was our own browser driver loading and waiting. &lt;strong&gt;Build flow&lt;/strong&gt; took another 20 to 23 seconds. Afterwards we deleted all of it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Jira automation rules examples: 10 we asked Rovo to build, scored
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;#&lt;/th&gt;
&lt;th&gt;What we asked for (shortened)&lt;/th&gt;
&lt;th&gt;What Rovo built&lt;/th&gt;
&lt;th&gt;Verdict&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;1&lt;/td&gt;
&lt;td&gt;New bug with priority Highest: assign to the space lead, add a comment&lt;/td&gt;
&lt;td&gt;JQL condition, assign to a named person, comment&lt;/td&gt;
&lt;td&gt;Worked as built, lead written in by name&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;2&lt;/td&gt;
&lt;td&gt;Every Monday at 9am, email me overdue work items&lt;/td&gt;
&lt;td&gt;Scheduled trigger, lookup, email with a table&lt;/td&gt;
&lt;td&gt;Needs edits: the search finds nothing&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;3&lt;/td&gt;
&lt;td&gt;New work item: create a Confluence page with key, summary, description, comment the link&lt;/td&gt;
&lt;td&gt;Asked which space we meant, then built it&lt;/td&gt;
&lt;td&gt;Worked as built, link shows brackets&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;Item moves to Done: comment on each open linked item that the blocker is resolved&lt;/td&gt;
&lt;td&gt;Branch over linked items, comment&lt;/td&gt;
&lt;td&gt;Needs edits: the comment names the wrong item&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;5&lt;/td&gt;
&lt;td&gt;"Make sure urgent stuff doesn't get forgotten"&lt;/td&gt;
&lt;td&gt;Daily reminder on Highest items, assumptions listed&lt;/td&gt;
&lt;td&gt;Needs edits: branch over a smart value that doesn't exist&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;6&lt;/td&gt;
&lt;td&gt;Resolved for 5 days with no update: close it, tell the reporter&lt;/td&gt;
&lt;td&gt;Daily lookup, comment, transition to Closed&lt;/td&gt;
&lt;td&gt;Needs edits: our space has no Resolved or Closed status&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;7&lt;/td&gt;
&lt;td&gt;All sub-tasks Done: move the parent to Done&lt;/td&gt;
&lt;td&gt;Sub-task check, then branch to the parent&lt;/td&gt;
&lt;td&gt;Needs edits: ran and did nothing&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;8&lt;/td&gt;
&lt;td&gt;Story due date changes: set the epic's due date to the latest story's&lt;/td&gt;
&lt;td&gt;Lookup by Epic Link, variable, edit the epic&lt;/td&gt;
&lt;td&gt;Needs edits: old field, blank trigger field&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;9&lt;/td&gt;
&lt;td&gt;Label database: assign to a named person; label frontend: assign to the lead&lt;/td&gt;
&lt;td&gt;If / else-if on labels&lt;/td&gt;
&lt;td&gt;Can't be enabled&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;10&lt;/td&gt;
&lt;td&gt;High or Highest with no update for 4 hours: comment mentioning the assignee, email the lead, weekdays only&lt;/td&gt;
&lt;td&gt;Hourly weekday schedule, lookup, comment, email&lt;/td&gt;
&lt;td&gt;Needs edits: the mention is plain text&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Two drafts were close to what an admin would build. Prompt 1 matched &lt;code&gt;issuetype = Bug AND priority = Highest&lt;/code&gt;, assigned the work item and commented "The project lead has been notified." It assigned the right person. But it did it by name: Rovo looked up today's lead and wrote that person into the rule, so when your lead changes the rule keeps assigning to the old one. Prompt 3 was the nicest surprise. We'd named a Confluence space key that doesn't exist on our site, and Rovo said it couldn't find a space matching &lt;code&gt;LZ&lt;/code&gt; and asked for the right one. With the key &lt;code&gt;DEMO&lt;/code&gt;, the flow created four real pages with Key, Summary and Description headings. The comment's link came out as &lt;code&gt;[RVAT-2 - summary|url]&lt;/code&gt; with the brackets showing, which is cosmetic.&lt;/p&gt;

&lt;p&gt;We asked for prompt 1 four times, twice in Jira and twice in Studio. Three plans used one JQL condition and one used two separate field conditions. The comment text also differed between the Jira and Studio routes. So don't expect the same request to give your colleague the same rule.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fe152mzpwj3ll4izhd0au.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fe152mzpwj3ll4izhd0au.png" title="Illustration, generated locally with ERNIE-Image. We asked for prompt 1 four times and got two different plans: three used one JQL condition, one used two separate field conditions. Same sheet, different towers." alt="Cartoon of three identical red robots handed the same sheet of instructions, each assembling a different tower, while a green robot holding a ring of keys wonders which one to trust." width="800" height="448"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Mistakes Rovo made in the rules, and how to catch them in the preview
&lt;/h2&gt;

&lt;h3&gt;
  
  
  A flow that looked right, ran twice and did nothing
&lt;/h3&gt;

&lt;p&gt;If you plan to switch drafts on without reading them, look at prompt 7 first. Rovo built: work item moves to Done, if the type is Sub-task, if a parent exists, if the sub-tasks match &lt;code&gt;status = Done&lt;/code&gt;, then branch to the parent and move it to Done. A &lt;strong&gt;branch&lt;/strong&gt; is the part of a rule that runs its actions on other work items, here the parent.&lt;/p&gt;

&lt;p&gt;The trouble is where the sub-task check sits. It runs on the sub-task that just moved, before the branch, so it never asks about the parent's other sub-tasks. We created a task with two sub-tasks and moved both to Done. The parent stayed in Backlog.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fbzsfze2wv4s974i9eb9h.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fbzsfze2wv4s974i9eb9h.png" title="Illustration, generated locally with ERNIE-Image. The sub-task check only inspects the card that just moved, so the parent is never asked about its other sub-tasks and stays in Backlog. Nobody went to check the dusty shelf." alt="Cartoon of a blue robot crouched over a conveyor belt examining one green-ticked card with a magnifying glass, while another robot waits on a cobwebbed crate and the unchecked red-dot cards sit on a dusty shelf." width="800" height="448"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fmyqhqktrp1jwdohjgdw1.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fmyqhqktrp1jwdohjgdw1.png" title="The Studio audit log on our test site, 13 November 2026. The sub-task flow stops after its second Related work items condition and shows No actions performed in green, with no error." alt="Rovo Studio audit log with the sub-task flow expanded: Work item transitioned, Work item fields condition and two Related work items condition rows, status No actions performed, and other rows showing 3 and 4 automation steps with Success." width="800" height="556"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Look at the status in that screenshot. The audit log says "No actions performed", in green, and shows no error. The editor says the owner gets an email when a flow fails, and nothing here failed, so I wouldn't expect one. You'd find out when someone asks why the parent is still open. Atlassian's template list offers this exact job ("When all child issues are completed then close parent", the yellow card in the Jira screenshot above). We didn't open it, so check where its sub-task condition sits before you trust it either.&lt;/p&gt;

&lt;h3&gt;
  
  
  A draft that searches by the old Epic Link field
&lt;/h3&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fuw09trt93umfvxre73bs.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fuw09trt93umfvxre73bs.png" title="Prompt 8 in the Rovo Studio editor, 13 November 2026. Look at the Lookup work items step: its JQL searches by 'Epic Link'. Rovo's own note on the right says you may need to change it." alt="Rovo Studio flow editor with a draft named Sync Epic Due Date to Latest Story Due Date, a Lookup work items step whose JQL uses 'Epic Link', and Rovo's chat note saying the flow uses the Epic Link field." width="800" height="556"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;For prompt 8, Rovo looked up the stories with &lt;code&gt;'Epic Link' = {{issue.parent.key}}&lt;/code&gt;. Atlassian &lt;a href="https://community.atlassian.com/forums/discussion/2377758/introducing-the-new-parent-field-in-company-managed-projects" rel="noopener noreferrer"&gt;replaced Epic Link with the Parent field&lt;/a&gt; in company-managed spaces, and Rovo's chat note half admits it: "If your project uses the newer parent-child hierarchy model, you may need to adjust the JQL query after building." The trigger also showed no field to watch, and the last step pointed at a field the editor labelled "due (deleted field?)". It needed three edits before it could work.&lt;/p&gt;

&lt;h3&gt;
  
  
  A draft the editor wouldn't switch on
&lt;/h3&gt;

&lt;p&gt;Prompt 9 got the logic right (if the label is database, else if the label is frontend), and again wrote the lead in by name. When we selected &lt;strong&gt;Save and enable&lt;/strong&gt;, the editor said: "Your flow contains errors that need to be resolved. Please review and validate your flow again before turning it on." You can't miss this kind of failure, which makes it the easy one.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F81pzo2pfeiag50zlti6a.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F81pzo2pfeiag50zlti6a.png" title="Prompt 9 after Save and enable, 13 November 2026. The tooltip at the top blocks the flow from being turned on." alt="Rovo Studio editor with a label-based assignment flow and a tooltip over Save and enable reading Your flow contains errors that need to be resolved." width="800" height="556"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  Statuses, branches, searches and mentions that don't work
&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;A search that finds nothing.&lt;/strong&gt; Prompt 2 filters by the space's long internal ID instead of its key. Jira's search accepts that without an error and returns nothing (we checked the same form of ID against another of our spaces), so the Monday email would arrive empty every week.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Statuses your space doesn't have.&lt;/strong&gt; Prompt 6 transitions to "Closed" and looks for "Resolved". RVAT has neither. Rovo didn't check or warn. We didn't run it, but there was nothing for it to move to.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The wrong work item inside a branch.&lt;/strong&gt; In prompt 4, the comment uses &lt;code&gt;{{issue.key}}&lt;/code&gt; inside a branch over linked items. Inside a branch, &lt;code&gt;{{issue}}&lt;/code&gt; is the linked item, so each comment names itself. It needs &lt;code&gt;{{triggerIssue.key}}&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;A smart value that isn't there.&lt;/strong&gt; Prompt 5 branches over &lt;code&gt;{{lookupIssue}}&lt;/code&gt;; the lookup's output is &lt;code&gt;{{lookupIssues}}&lt;/code&gt;. For this vague request, though, Rovo did write down its assumptions, such as "Only "Highest" priority issues trigger reminders".&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;A mention that won't notify.&lt;/strong&gt; Prompt 10 writes the assignee's name and raw account ID into the comment. Atlassian's &lt;a href="https://support.atlassian.com/cloud-automation/docs/jira-smart-values-users/" rel="noopener noreferrer"&gt;user smart values page&lt;/a&gt; says a mention needs &lt;code&gt;[~accountId:...]&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;So here's my checklist for the preview. Read the trigger's field. Check that the statuses the rule names exist in your workflow. Inside a branch, look for &lt;code&gt;{{issue}}&lt;/code&gt; where you meant &lt;code&gt;{{triggerIssue}}&lt;/code&gt;. Make sure no person is typed in where a role was meant. Then trigger it once on a test work item and open the audit log, because "No actions performed" can also mean "built wrong".&lt;/p&gt;

&lt;h2&gt;
  
  
  Jira automation cost with Rovo: credits to create a rule, steps to run it
&lt;/h2&gt;

&lt;p&gt;None of the Atlassian pages we read on 13 November say whether generating a flow spends Rovo credits. &lt;a href="https://support.atlassian.com/rovo/docs/rovo-usage-limits/" rel="noopener noreferrer"&gt;How Rovo credits work&lt;/a&gt; lists a "Create with Rovo" row at variable credits, but that row links to Confluence's Create with Rovo for pages and whiteboards, not to automation. The name is shared: &lt;a href="https://leanzero.net/tutorials/solution-composer-atlassian-create-with-rovo?utm_source=devto&amp;amp;utm_medium=referral&amp;amp;utm_campaign=crosspost" rel="noopener noreferrer"&gt;Jira Service Management has a Create with Rovo too&lt;/a&gt;, for building a whole service space. So we read our org's credit meter, the one behind &lt;strong&gt;Platform usage&lt;/strong&gt; in Atlassian Administration, before and after.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;What we did&lt;/th&gt;
&lt;th&gt;Rovo credits&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;One prompt, measured on its own (639 to 649)&lt;/td&gt;
&lt;td&gt;10&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;The whole test: 13 prompts (10 requests, prompt 1 repeated 3 times) plus 1 clarification reply&lt;/td&gt;
&lt;td&gt;140&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Build flow, Save and enable, running flows without a Rovo step&lt;/td&gt;
&lt;td&gt;0&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;So it's about 10 credits per message to Rovo. A clarification reply counts too. That's the same 10 credits a quick Rovo Chat answer costs in our &lt;a href="https://leanzero.net/blog/rovo-credits-per-user?utm_source=devto&amp;amp;utm_medium=referral&amp;amp;utm_campaign=crosspost" rel="noopener noreferrer"&gt;Rovo credits per user measurements&lt;/a&gt;. The meter is org-wide. Anyone else using Rovo in the same minutes would have shown up too. At Atlassian's extra usage price of USD 0.01 per credit, which applies from 3 December 2026, ten prompts would cost about a dollar. A 200-user Jira Standard site gets 25 credits per user per month, 5,000 credits pooled, so those ten prompts would use 2% of it.&lt;/p&gt;

&lt;p&gt;Running a flow is billed in &lt;strong&gt;automation steps&lt;/strong&gt;: each executed trigger, condition, action and branch counts, apart from a few free system steps such as Lookup work items. Atlassian's &lt;a href="https://support.atlassian.com/cloud-automation/docs/how-is-my-usage-calculated/" rel="noopener noreferrer"&gt;usage page&lt;/a&gt; says usage-based billing starts on 3 December 2026. From the audit log:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Flow&lt;/th&gt;
&lt;th&gt;Run&lt;/th&gt;
&lt;th&gt;Automation steps&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Highest bug: assign and comment&lt;/td&gt;
&lt;td&gt;matched a bug&lt;/td&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Highest bug: assign and comment&lt;/td&gt;
&lt;td&gt;not a bug, stopped at the condition&lt;/td&gt;
&lt;td&gt;0&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Confluence page and comment&lt;/td&gt;
&lt;td&gt;each new work item&lt;/td&gt;
&lt;td&gt;3&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Sub-tasks to parent&lt;/td&gt;
&lt;td&gt;stopped at the condition&lt;/td&gt;
&lt;td&gt;0&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Four steps means the trigger and the condition plus two actions. The zero rows are new: since 5 November 2026, Atlassian doesn't charge steps for runs with the status No actions performed. Our earlier &lt;a href="https://leanzero.net/tutorials/jira-automation-usage-billing-steps-per-rule?utm_source=devto&amp;amp;utm_medium=referral&amp;amp;utm_campaign=crosspost" rel="noopener noreferrer"&gt;steps per rule measurements&lt;/a&gt; predate that change for failed conditions, so use this table for those. If a generated flow includes a &lt;strong&gt;Use agent&lt;/strong&gt; action, that part is billed in Rovo credits each time it runs, which we measured in &lt;a href="https://leanzero.net/tutorials/rovo-agent-pricing-jira-automation?utm_source=devto&amp;amp;utm_medium=referral&amp;amp;utm_campaign=crosspost" rel="noopener noreferrer"&gt;Rovo agent pricing in Jira automation&lt;/a&gt;; Atlassian bills &lt;strong&gt;Use Rovo&lt;/strong&gt; the same way. None of our 10 drafts added either.&lt;/p&gt;

&lt;h2&gt;
  
  
  Who can create rules with Rovo: Rovo Studio access and the Automation creator role
&lt;/h2&gt;

&lt;p&gt;In plain Jira automation, a space admin builds flows for their space and a Jira admin builds them for everything. Rovo Studio works differently. Atlassian's &lt;a href="https://support.atlassian.com/studio/docs/manage-who-can-create-in-studio/" rel="noopener noreferrer"&gt;Manage who can create in Studio&lt;/a&gt; says the App creator and Automation creator roles "are granted to all Studio users by default". And &lt;a href="https://support.atlassian.com/organization-administration/docs/use-rovo-studio-in-your-organization/" rel="noopener noreferrer"&gt;Use Rovo Studio in your organization&lt;/a&gt; says people who had a user role in Jira, Confluence or Jira Service Management were given the Studio user role automatically, in organizations that had the previous Studio experience.&lt;/p&gt;

&lt;p&gt;That first page also says a Studio app admin can take Automation creator away from all Studio users on Studio Standard, Premium or Enterprise: select the settings icon at the top right of Studio, open &lt;strong&gt;Studio settings&lt;/strong&gt;, go to &lt;strong&gt;Apps and automations&lt;/strong&gt;, and on the &lt;strong&gt;All Studio users&lt;/strong&gt; row use the &lt;strong&gt;Roles&lt;/strong&gt; list to clear &lt;strong&gt;Automation creator&lt;/strong&gt;. Our site's Studio is on the Free plan, and its settings only showed the switch for who can create Rovo agents, so we couldn't try those steps. We also only tested as an org admin, so what a non-admin sees is still open.&lt;/p&gt;

&lt;p&gt;On our site, the drafts had &lt;strong&gt;Who can edit this flow?&lt;/strong&gt; set to &lt;strong&gt;All Studio users&lt;/strong&gt;. Two open tracker items add to that. &lt;a href="https://jira.atlassian.com/browse/ROVO-933" rel="noopener noreferrer"&gt;ROVO-933&lt;/a&gt; says "Rovo Studio automations and their audit logs are visible to all users with Studio access". &lt;a href="https://jira.atlassian.com/browse/ROVO-980" rel="noopener noreferrer"&gt;ROVO-980&lt;/a&gt; says an Actor (the user a flow runs as) can't be set for Studio automations yet, and a customer comment on it says Studio flows run as their creator, so their actions show that one person's name. If you want to see how Studio's agent builder handles access, our &lt;a href="https://leanzero.net/tutorials/build-rovo-agent-jira-triage-rovo-studio?utm_source=devto&amp;amp;utm_medium=referral&amp;amp;utm_campaign=crosspost" rel="noopener noreferrer"&gt;Rovo Studio triage agent tutorial&lt;/a&gt; walks through it.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I'd do before your team uses Create with Rovo
&lt;/h2&gt;

&lt;p&gt;I'd let people use it, as long as someone who knows your Jira setup reads each draft before it's switched on. Rovo finds a sensible trigger and lays out the steps, and at 10 credits a message it's cheap to try. It doesn't know your space: your statuses, your fields, who the lead is, and three of its ten drafts searched for the wrong thing.&lt;/p&gt;

&lt;p&gt;So, concretely:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Decide who should build flows in Studio, then ask your Studio app admin to restrict the Automation creator role to that group, if your Studio plan offers it. By default it's everyone with Studio access.&lt;/li&gt;
&lt;li&gt;On each flow you keep, open &lt;strong&gt;Who can edit this flow?&lt;/strong&gt; and pick the narrowest option it offers. We only ever saw &lt;strong&gt;All Studio users&lt;/strong&gt; there, so check what your site lists.&lt;/li&gt;
&lt;li&gt;Read each draft against the checklist above, then trigger it once on a test work item and open the audit log.&lt;/li&gt;
&lt;li&gt;For common jobs, like closing a parent when its sub-tasks are done, look at Atlassian's template first and check it the same way.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;For the budget, count about 10 Rovo credits per message to Rovo, plus the steps each run uses.&lt;/p&gt;

&lt;p&gt;I'm curious how it went on your site. Did Create with Rovo get your first rule right, or did you end up rebuilding it from scratch? Tell me in the comments or on the &lt;a href="https://community.atlassian.com/" rel="noopener noreferrer"&gt;Atlassian Community&lt;/a&gt; :)&lt;/p&gt;




&lt;p&gt;Originally published on &lt;a href="https://leanzero.net/blog/jira-automation-with-rovo-rules-tested?utm_source=devto&amp;amp;utm_medium=referral&amp;amp;utm_campaign=crosspost" rel="noopener noreferrer"&gt;leanzero.net&lt;/a&gt;. More Atlassian, Forge and local-AI write-ups at &lt;a href="https://leanzero.net/blog?utm_source=devto&amp;amp;utm_medium=referral&amp;amp;utm_campaign=crosspost" rel="noopener noreferrer"&gt;leanzero.net/blog&lt;/a&gt;, and if you're planning a migration or a Forge app, that's what we do: &lt;a href="https://leanzero.net/services?utm_source=devto&amp;amp;utm_medium=referral&amp;amp;utm_campaign=crosspost" rel="noopener noreferrer"&gt;leanzero.net/services&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>jira</category>
    </item>
    <item>
      <title>Jira Guest Access: 5 Free Guests per Paid User</title>
      <dc:creator>Mihai Perdum</dc:creator>
      <pubDate>Thu, 12 Nov 2026 11:59:35 +0000</pubDate>
      <link>https://dev.to/mihai_leanzero/jira-guest-access-5-free-guests-per-paid-user-28h2</link>
      <guid>https://dev.to/mihai_leanzero/jira-guest-access-5-free-guests-per-paid-user-28h2</guid>
      <description>&lt;p&gt;In October 2017 someone asked on the Atlassian Community about &lt;a href="https://community.atlassian.com/forums/Jira-questions/Guest-access-to-JIRA/qaa-p/667764" rel="noopener noreferrer"&gt;guest access to Jira&lt;/a&gt;. That thread had 30,175 views when we checked it on 12 November 2026. Its accepted answer sets up a "guests" group that still uses a normal licence, and a later comment sums it up: "You're still burning user licenses and paying the JIRA fees". That was right at the time. On 27 April 2026 Atlassian &lt;a href="https://jirareleases.atlassian.com/announcements/bring-external-collaborators-into-jira-without-adding-seats" rel="noopener noreferrer"&gt;announced free guest access&lt;/a&gt; for Jira Cloud. Its &lt;a href="https://support.atlassian.com/jira-cloud-administration/docs/invite-guests-to-jira/" rel="noopener noreferrer"&gt;guest doc&lt;/a&gt; now says "Guests are free of charge (up to 5 guests per paid user)" on the Standard, Premium and Enterprise plans. I'm glad it's here.&lt;/p&gt;

&lt;p&gt;So the next contractor, client or vendor who only works in one Jira space doesn't need a paid seat. On our test site, adding an outside address to a space as a guest showed "0 new licenses have been added to Jira", and the licensed user count didn't move. The people you already pay for can't be switched, though: Atlassian's policy says "You may not convert current or former paid users to guests". That includes removing a paid contractor and inviting them back as a guest, since they'd be a former paid user.&lt;/p&gt;

&lt;p&gt;If 40 of the 200 seats a company would otherwise buy are for new outside people, guest access saves USD 3,936 a year on monthly Standard billing at today's list prices. On annual billing the saving only appears if guests keep you below the bottom of a price tier, for example at 400 users instead of 500.&lt;/p&gt;

&lt;p&gt;We tested the admin side on our own Jira Cloud test site, which is on Premium, on 12 November 2026. We couldn't log in as the guest, so what a guest sees comes from Atlassian's documentation. A note on words: Atlassian now calls a Jira project a space, and an issue a work item.&lt;/p&gt;

&lt;p&gt;[[steps]]&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Invite the guest to your site&lt;/strong&gt; as a site admin, with the Guest role.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Add the guest to one space&lt;/strong&gt; with the Guest - Collaborator role.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Give the guest role Browse spaces&lt;/strong&gt; if the space is company-managed.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Check the licence counts&lt;/strong&gt; in Atlassian Administration.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Remove the guest&lt;/strong&gt; from the space and from Jira when the work ends.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Do Jira guest users need a license? Who can be a guest, and who still needs a paid seat
&lt;/h2&gt;

&lt;p&gt;Atlassian's doc defines a guest as "anyone outside your organization, its affiliates, subsidiaries, or related entities", like clients, vendors, freelancers or external consultants. Their email domain can't match any domain your organisation owns, so a contractor you gave a company email address can't be a guest.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Question&lt;/th&gt;
&lt;th&gt;Can be a guest&lt;/th&gt;
&lt;th&gt;Needs a paid seat&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Plan&lt;/td&gt;
&lt;td&gt;Standard, Premium, Enterprise&lt;/td&gt;
&lt;td&gt;Free has no guest access&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Who they are&lt;/td&gt;
&lt;td&gt;Outside your organisation, own email domain&lt;/td&gt;
&lt;td&gt;Employees, or anyone on a company domain&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;How many spaces&lt;/td&gt;
&lt;td&gt;One Jira business or software space per site&lt;/td&gt;
&lt;td&gt;Two or more spaces on the same site&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Space type&lt;/td&gt;
&lt;td&gt;Business or software space&lt;/td&gt;
&lt;td&gt;Service space, as an agent&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Paid history&lt;/td&gt;
&lt;td&gt;Never a paid user&lt;/td&gt;
&lt;td&gt;Current or former paid user&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;How many&lt;/td&gt;
&lt;td&gt;Up to 5 guests per paid user, within the site's 100,000 user limit&lt;/td&gt;
&lt;td&gt;Anyone over the 5:1 ratio&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;The rule people trip over is the space one. I'd check it first. Someone who works in two spaces on the same site can't be a guest there and needs a paid seat, although the same person can be a guest on several different sites with one space on each of them.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fuc0xifoyxq4yjapp2dfg.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fuc0xifoyxq4yjapp2dfg.png" title="Illustration, generated locally with ERNIE-Image. A Jira guest gets one space per site, so someone who also files bugs in a second space needs a paid seat, while the same person can be a guest on several sites with one space on each. One doorway per house; the robot is welcome at all of them." alt="Cartoon robot shut inside a blue house with a giant red X nailed across its doorway, while three separate houses in green, red and blue each have a waving robot in their single doorway with a big green tick floating above." width="800" height="448"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;We saw what that looks like. When we tried to add our guest to a second space, the people picker showed them greyed out with the label "Not in this space", and we couldn't select them. There was no error message and no tooltip. So plan the space before you invite.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F8q9yrkcj3j5hdi4gd36y.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F8q9yrkcj3j5hdi4gd36y.png" title="The Add people dialog in a second space on our test site, 12 November 2026. Our guests are greyed out with 'Not in this space'. You can't select them, and nothing explains why." alt="A Jira Add people dialog with Guest - Collaborator selected; the people list shows two guest.tutorial entries greyed out, each labelled Not in this space." width="798" height="1061"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Before you start
&lt;/h2&gt;

&lt;blockquote&gt;
&lt;p&gt;Note&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Prerequisites&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Jira Cloud on the Standard, Premium or Enterprise plan. Our test site is on Premium.&lt;/li&gt;
&lt;li&gt;A site admin for the invite and for the permission scheme in Step 3, and a space admin to add the guest to a space.&lt;/li&gt;
&lt;li&gt;The guest's email address, on a domain your organisation doesn't own, for someone who has never been a paid user.&lt;/li&gt;
&lt;li&gt;Atlassian's weekly change log still listed "Guest role available for Jira" as rolling out in its &lt;a href="https://confluence.atlassian.com/cloud/blog/2026/09/atlassian-cloud-changes-sep-21-to-sep-28-2026" rel="noopener noreferrer"&gt;21-28 September 2026 post&lt;/a&gt;, the newest one we could find. If you don't see a Guest role, your site may not have it yet.&lt;/li&gt;
&lt;/ul&gt;
&lt;/blockquote&gt;

&lt;p&gt;Guests are external users, so your organisation's external user security settings apply to them. Atlassian's Manage guest access doc names some of them, like two-step verification, periodic re-verification and API token access.&lt;/p&gt;

&lt;p&gt;When you're done you'll have an outside collaborator working in one space, counted as a guest and not as a licensed user.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 1: Invite a guest user to Jira from User management
&lt;/h2&gt;

&lt;p&gt;This is Atlassian's procedure from &lt;a href="https://support.atlassian.com/jira-cloud-administration/docs/manage-guest-access-in-jira/" rel="noopener noreferrer"&gt;Manage guest access in Jira&lt;/a&gt;. You need to be a site admin.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;In Jira's top navigation, select &lt;strong&gt;Settings&lt;/strong&gt;, then &lt;strong&gt;User management&lt;/strong&gt;. The Users page opens.&lt;/li&gt;
&lt;li&gt;Select &lt;strong&gt;Invite users&lt;/strong&gt;. The invite form opens.&lt;/li&gt;
&lt;li&gt;In the email field, enter the guest's email address.&lt;/li&gt;
&lt;li&gt;In the &lt;strong&gt;Apps&lt;/strong&gt; tab, find your Jira site, and in the &lt;strong&gt;Roles&lt;/strong&gt; dropdown select &lt;strong&gt;Guest&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;Select &lt;strong&gt;Next&lt;/strong&gt;, check the summary, and select &lt;strong&gt;Grant access&lt;/strong&gt;.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The doc says that once the person accepts and signs in with an Atlassian account, "they'll appear as a guest on your site". It adds that "they still can't see any work until a space admin adds them to a specific space". As site admins we skipped this step, because adding a new address in Step 2 sent the invite for us. If the person adding guests to your space isn't a site admin, ask a site admin to do Step 1 first. Atlassian documents that order, and we only tried the shortcut as site admins.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 2: Add the guest to one space with the Guest - Collaborator role
&lt;/h2&gt;

&lt;p&gt;We ran this step. The space admin does it from the space's own settings.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;In your space, open &lt;strong&gt;Space settings&lt;/strong&gt; and select &lt;strong&gt;Access&lt;/strong&gt; (Atlassian's doc calls this page &lt;strong&gt;People&lt;/strong&gt;). You see the people with a role in this space.&lt;/li&gt;
&lt;li&gt;Select &lt;strong&gt;Add people&lt;/strong&gt;. A dialog opens with &lt;strong&gt;Names or emails&lt;/strong&gt; and &lt;strong&gt;Role&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;In &lt;strong&gt;Names or emails&lt;/strong&gt;, type the guest's full email address and pick the line that shows exactly that address. The address appears as a chip with an envelope icon.&lt;/li&gt;
&lt;li&gt;Open &lt;strong&gt;Role&lt;/strong&gt; and select &lt;strong&gt;Guest - Collaborator&lt;/strong&gt;. Its description ends with "(non-billable)".&lt;/li&gt;
&lt;li&gt;Select &lt;strong&gt;Add 1 person&lt;/strong&gt;. A confirmation dialog opens.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;You should see this:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Added people to space
You have added 1 person to your space and 0 new licenses have been added to Jira.
New to Jira
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fkjw254w3tr55vadjzopu.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fkjw254w3tr55vadjzopu.png" title="The Add people dialog on our test site, 12 November 2026. Read the end of the second role's description: '(non-billable)'. That's the role that makes someone a guest." alt="The Add people dialog in a Jira space with the Role menu open, showing Administrator, Guest - Collaborator with its non-billable description, Member and Viewer. The suggested people row is masked." width="800" height="1397"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fvmdgcw5ti6ha7k0t14fv.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fvmdgcw5ti6ha7k0t14fv.png" title="The confirmation after adding our guest, 12 November 2026. Look for '0 new licenses'. We masked the guest's address." alt="The Added people to space confirmation: 1 person added and 0 new licenses added to Jira, with a New to Jira badge. The guest's email is masked." width="798" height="668"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;We typed a brand new address here without doing Step 1 first, and Jira sent the invite itself. It was a test address on a mail domain our test organisation doesn't manage, and Atlassian Administration labelled the account External user. The email's subject was "Action requested: Admin invited you to join your team in Jira", with an &lt;strong&gt;Accept invite&lt;/strong&gt; button. Behind the scenes Jira put our guest in a group called jira-guests-wolfaenpak (wolfaenpak is our test site), with the role Guest.&lt;/p&gt;

&lt;p&gt;Look twice. Check the address before you select &lt;strong&gt;Add&lt;/strong&gt;. When we typed only part of a name, the list offered an address built from that name and our admin's email domain, and we invited an address that doesn't exist.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 3: Give the guest role Browse spaces in a company-managed space
&lt;/h2&gt;

&lt;p&gt;Our test space is team-managed (configured from inside the space), so we skipped this. Atlassian's doc asks for it only in company-managed spaces, the ones a Jira admin configures with shared schemes. There, the guest "won't be able to access the space" unless the permission scheme gives the guest role &lt;strong&gt;Browse spaces&lt;/strong&gt;. These are the doc's steps.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;In Jira, go to &lt;strong&gt;Settings&lt;/strong&gt;, then &lt;strong&gt;Work items&lt;/strong&gt;, then &lt;strong&gt;Permission schemes&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;Select the permission scheme your guest's space uses.&lt;/li&gt;
&lt;li&gt;Find &lt;strong&gt;Browse spaces&lt;/strong&gt; and select &lt;strong&gt;Update&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;Select &lt;strong&gt;Space role&lt;/strong&gt;, then &lt;strong&gt;Guest - Collaborator&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;Select &lt;strong&gt;Save&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;Optional: repeat for each other permission your guests need, like &lt;strong&gt;Create work items&lt;/strong&gt; or &lt;strong&gt;Add comments&lt;/strong&gt;.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Step 4: Check the guest isn't counted as a licensed user
&lt;/h2&gt;

&lt;p&gt;Finance will want proof that no seat was used.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;In &lt;a href="https://admin.atlassian.com" rel="noopener noreferrer"&gt;admin.atlassian.com&lt;/a&gt;, open &lt;strong&gt;Apps&lt;/strong&gt;, then &lt;strong&gt;Atlassian apps&lt;/strong&gt;, then &lt;strong&gt;Jira&lt;/strong&gt; for your site. The page shows &lt;strong&gt;Total users&lt;/strong&gt;, &lt;strong&gt;Licensed users&lt;/strong&gt; and your &lt;strong&gt;Plan&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;Compare the two counts. Guests are in Total users and not in Licensed users.&lt;/li&gt;
&lt;li&gt;Optional: open the guest from &lt;strong&gt;Directory&lt;/strong&gt; &amp;gt; &lt;strong&gt;Users&lt;/strong&gt;. Their Jira row shows the role &lt;strong&gt;Guest&lt;/strong&gt;, and Last seen reads "Not tracked for this role".&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;You should see Total users go up by one for each guest while Licensed users stays the same. On our site, three guest adds took Total users from 12 to 15, and Licensed users stayed at 8. Two of those adds were our own mistakes (two wrong picks from the suggestion list), which is why there were three. Finance can check it the same way.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fknj7wmpac98j9c97t6gi.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fknj7wmpac98j9c97t6gi.png" title="Jira's app page in Atlassian Administration on our test site, 12 November 2026: Total users 15, Licensed users 8. The jira-guests group's member count read 1 on this page while Jira's API listed 3 guests, so trust the two totals at the top. We masked one test group row." alt="Atlassian Administration Jira app page showing Total users 15, Licensed users 8, Plan Premium, and a jira-guests-wolfaenpak group with the role Guest." width="799" height="373"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;We didn't see the 5:1 ratio, or how many guests you have left, on this page or on Billing and subscriptions. If you're anywhere near it (a 10-user site can have up to 50 guests), keep your own count. A spreadsheet is enough.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 5: Remove a guest when the engagement ends
&lt;/h2&gt;

&lt;p&gt;When we removed our guest from the space, the flag said "guest.tutorial no longer has access to this space", and the account was still a Jira guest on the site. Atlassian's doc says the same: they "can't access Jira at all, but will remain in the guest list". So there are two removals.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Ftlp6mw3c8tamwrzadbdh.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Ftlp6mw3c8tamwrzadbdh.png" title="Illustration, generated locally with ERNIE-Image. Removing a guest from the space revokes that space but leaves the account on the site's guest list, so the removal is really two steps. One robot kicks, the other wipes the card, and neither waits for the first." alt="Cartoon robot bouncer kicking a small robot out of a green clubhouse doorway while a second robot on a stepladder erases the still-ticked card off a wall clipboard." width="800" height="448"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;In the space, open &lt;strong&gt;Space settings&lt;/strong&gt; &amp;gt; &lt;strong&gt;Access&lt;/strong&gt;, select &lt;strong&gt;Remove&lt;/strong&gt; on the guest's row, and confirm. The guest loses the space.&lt;/li&gt;
&lt;li&gt;In admin.atlassian.com, open &lt;strong&gt;Directory&lt;/strong&gt; &amp;gt; &lt;strong&gt;Users&lt;/strong&gt; and select the guest. Their user page opens.&lt;/li&gt;
&lt;li&gt;In the row for Jira, select &lt;strong&gt;More actions&lt;/strong&gt; (•••), then &lt;strong&gt;Remove access&lt;/strong&gt;. The doc says this "completely revokes the guest's access to Jira on your site".&lt;/li&gt;
&lt;li&gt;Optional: to remove the person from your organisation, select &lt;strong&gt;More actions for user&lt;/strong&gt; &amp;gt; &lt;strong&gt;Remove user&lt;/strong&gt;. The dialog says "They'll lose access to all apps, but most content they created won't be deleted."&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;You should see no apps on the guest's user page. We did item 3 a different way, by removing the account from the jira-guests-wolfaenpak group through Jira's REST API, and the user page then read "No apps added".&lt;/p&gt;

&lt;p&gt;To check from the API that no guests are left on the site, list the guest group's members. Use your own site name, admin email and &lt;a href="https://id.atlassian.com/manage-profile/security/api-tokens" rel="noopener noreferrer"&gt;API token&lt;/a&gt;:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;curl -s -u &lt;span class="s2"&gt;"you@example.com:$API_TOKEN"&lt;/span&gt; &lt;span class="s2"&gt;"https://&amp;lt;your-site&amp;gt;.atlassian.net/rest/api/3/group/member?groupname=jira-guests-&amp;lt;your-site&amp;gt;"&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;You should see &lt;code&gt;"total":0&lt;/code&gt; once every guest is removed. Ours printed this after our cleanup (we trimmed the &lt;code&gt;self&lt;/code&gt; URL):&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;{"maxResults":50,"startAt":0,"total":0,"isLast":true,"values":[]}
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  What a Jira guest can and can't see
&lt;/h2&gt;

&lt;p&gt;When we tried to log in as our guest, Atlassian's sign-up page asked us to tick "I'm not a robot", which we couldn't complete in our automated test. So this section comes from Atlassian's &lt;a href="https://support.atlassian.com/jira-cloud-administration/docs/guest-permissions-in-jira/" rel="noopener noreferrer"&gt;guest permissions doc&lt;/a&gt; and the invite doc. We'd have liked to see it ourselves.&lt;/p&gt;

&lt;p&gt;A guest can browse their one space. They can create and edit work items there, and move them through the workflow. They can be assigned work and assign it to others. They can comment, add attachments, log work and link work items inside the same space. Boards and backlogs work too, "as allowed by the guest role and space configuration".&lt;/p&gt;

&lt;p&gt;A guest can't open any other space, administer the space, manage sprints, archive work items or move them to another space, or act as a service agent. They get no global permissions, so they can't share dashboards or filters or make bulk changes. Atlassian's announcement adds that guests "can't see your Goals, team directory, or other spaces".&lt;/p&gt;

&lt;p&gt;We found no Atlassian page that says whether a Jira guest can use Rovo (Atlassian's AI), or how a guest behaves inside automation rules. For Confluence guests, Atlassian's &lt;a href="https://jira.atlassian.com/browse/ROVO-38" rel="noopener noreferrer"&gt;ROVO-38&lt;/a&gt; says Rovo isn't available "because Confluence guest users are not billable for Rovo". I'd probably assume the same for Jira until Atlassian says otherwise.&lt;/p&gt;

&lt;h2&gt;
  
  
  Converting a licensed Jira user to a guest: not allowed, and the space role doesn't do it
&lt;/h2&gt;

&lt;p&gt;The request to allow it, &lt;a href="https://jira.atlassian.com/browse/JRACLOUD-98504" rel="noopener noreferrer"&gt;JRACLOUD-98504&lt;/a&gt;, was at 35 votes and Gathering Interest on 12 November 2026. Going the other way is fine. You can promote a guest to a licensed role, and from then on they count toward your bill.&lt;/p&gt;

&lt;p&gt;We wanted to see what happens if you try anyway. In a space's Add people dialog we gave our paid test user the Guest - Collaborator role. Jira accepted it. The toast said "Invite sent", with no warning. She kept her paid licence. She also stayed in the Jira users group, so on a paying user Guest - Collaborator is just a space role. The Jira row's menu on her user page had no item to change her role to Guest. We couldn't open our site's row in the admin role list, so we don't know whether Guest is offered there.&lt;/p&gt;

&lt;p&gt;Jira did let us add, as a guest, a person who pays for Jira on another site in our organisation. Jira not blocking it doesn't make it allowed. Atlassian defines a guest as "anyone outside your organization", so don't use the Guest role for your own people.&lt;/p&gt;

&lt;p&gt;For seats you already pay for, the lever is people who've left: finding and removing &lt;a href="https://dev.to/blog/find-inactive-users-jira-cost-slasher"&gt;inactive users&lt;/a&gt; frees those.&lt;/p&gt;

&lt;h2&gt;
  
  
  Jira guest access cost: the seat saving at 50, 200 and 500 users
&lt;/h2&gt;

&lt;p&gt;Prices are Atlassian's &lt;a href="https://www.atlassian.com/software/jira/pricing" rel="noopener noreferrer"&gt;Jira list prices&lt;/a&gt; in US dollars as we read them on 12 November 2026, after the 13 October increase. Monthly billing is graduated: on Standard you pay USD 9.70 per user for users 1-100, USD 8.20 for 101-250 and USD 6.85 for 251-1,000 (Premium USD 19.60, 14.65 and 10.20). Annual is different. You pay one flat price for each user tier, like 101-200 or 401-500.&lt;/p&gt;

&lt;p&gt;My assumptions: 20% of the seats you'd otherwise buy are for new outside people with their own email domains, each works in one space, and none of them was ever a paid user. List prices, Jira only, no discounts.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Seats you'd need without guests&lt;/th&gt;
&lt;th&gt;New outside people as guests&lt;/th&gt;
&lt;th&gt;Standard monthly&lt;/th&gt;
&lt;th&gt;Premium monthly&lt;/th&gt;
&lt;th&gt;Standard annual&lt;/th&gt;
&lt;th&gt;Premium annual&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;50&lt;/td&gt;
&lt;td&gt;10&lt;/td&gt;
&lt;td&gt;USD 1,164 a year&lt;/td&gt;
&lt;td&gt;USD 2,352 a year&lt;/td&gt;
&lt;td&gt;USD 0&lt;/td&gt;
&lt;td&gt;USD 0&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;200&lt;/td&gt;
&lt;td&gt;40&lt;/td&gt;
&lt;td&gt;USD 3,936 a year&lt;/td&gt;
&lt;td&gt;USD 7,032 a year&lt;/td&gt;
&lt;td&gt;USD 0&lt;/td&gt;
&lt;td&gt;USD 0&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;500&lt;/td&gt;
&lt;td&gt;100&lt;/td&gt;
&lt;td&gt;USD 8,220 a year&lt;/td&gt;
&lt;td&gt;USD 12,240 a year&lt;/td&gt;
&lt;td&gt;USD 6,500&lt;/td&gt;
&lt;td&gt;USD 10,000&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Why is the annual saving zero at 50 and 200? It's the tiers. 200 users and 160 users both sit in the 101-200 tier, at USD 18,000 a year on Standard. At 500 users, staying at 400 puts you in the 301-400 tier (USD 32,500) instead of 401-500 (USD 39,000). If guests take you below your current tier, Atlassian's &lt;a href="https://www.atlassian.com/licensing/future-pricing/cloud-pricing/faqs" rel="noopener noreferrer"&gt;cloud pricing FAQ&lt;/a&gt; says you get the lower tier by contacting them "when your renewal is due". The monthly saving per guest also gets smaller as you grow: above 250 users each seat you don't buy on Standard is USD 6.85 a month.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F78qvdstyuixg2repmapd.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F78qvdstyuixg2repmapd.png" title="Illustration, generated locally with ERNIE-Image. The annual bill is set by your pricing tier, so guests released inside the 101-200 tier save nothing a year, while dropping from 401-500 (USD 39,000) to 301-400 (USD 32,500) on Standard saves 6,500. Sweeping a coin along the same step leaves the tower exactly as high." alt="Cartoon robots on a staircase built of giant gold coin-steps: one sweeps a coin sideways along the same step beside a coin tower that stays the same height, while the other slides down to the next step where the tower is much shorter and coins spill." width="800" height="448"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;The 5:1 cap didn't matter in any of these rows, since 160 paid users could have 800 guests, while the one-space rule matters a lot more, so count how many of your outside people work in two spaces before you give finance a number.&lt;/p&gt;

&lt;p&gt;On 3 December 2026 Atlassian starts billing &lt;a href="https://dev.to/blog/atlassian-usage-based-pricing-budget-2027"&gt;usage meters&lt;/a&gt; like Rovo credits and automation steps. Each user adds an allowance to a shared pool for each meter. No Atlassian page we found says whether guests count as users for that. For per-seat prices at larger sizes, see our &lt;a href="https://dev.to/blog/jira-premium-vs-enterprise-pricing-200-500-seats"&gt;Jira Premium vs Enterprise pricing&lt;/a&gt; breakdown.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where guest access stops: service spaces, Confluence and apps
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Jira Service Management.&lt;/strong&gt; A guest can't be a service agent, and your customers (the people who raise requests on the portal) were already free, so they don't need the Guest role either.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Confluence.&lt;/strong&gt; Confluence has its own guests with the same 5-per-paid-user ratio, but some rules differ. Guests there can open any space that allows anonymous access, and Marketplace apps are on for them by default, according to Atlassian's page on &lt;a href="https://support.atlassian.com/confluence-cloud/docs/what-can-guests-see-and-do-on-confluence/" rel="noopener noreferrer"&gt;what Confluence guests can see and do&lt;/a&gt;. Its &lt;a href="https://support.atlassian.com/confluence-cloud/docs/invite-guests-for-external-collaboration/" rel="noopener noreferrer"&gt;Confluence guest invite doc&lt;/a&gt; adds that guests "are not currently supported in Confluence mobile apps".&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Apps in Jira.&lt;/strong&gt; Atlassian's &lt;a href="https://developer.atlassian.com/platform/forge/access-to-forge-apps-for-unlicensed-users/" rel="noopener noreferrer"&gt;Forge developer doc&lt;/a&gt;, updated 28 October 2026, says "By default, Forge modules don't allow unlicensed user access", and only four Jira module types can let guests in. So if your team uses a Marketplace app inside the space, ask its vendor whether guests can use it. Check before the guest's first day.&lt;/p&gt;

&lt;h2&gt;
  
  
  If it didn't work
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;The guest is greyed out with "Not in this space".&lt;/strong&gt; They're already a guest in another space on your site. Atlassian's doc says you'll "need to remove them before adding them to another space" (Step 5, item 1).&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The guest accepted the invite and sees nothing.&lt;/strong&gt; In a company-managed space the permission scheme needs Browse spaces for Guest - Collaborator (Step 3).&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;You invited the wrong address.&lt;/strong&gt; Remove that account from the space and from Jira (Step 5), and type the full address next time.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;There's no Guest role in the dialog.&lt;/strong&gt; Check the plan first, since Free has no guest access, then the rollout note under Before you start.&lt;/p&gt;

&lt;h2&gt;
  
  
  What you have now, and what I'd do
&lt;/h2&gt;

&lt;p&gt;[[takeaways]]&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;What you set up.&lt;/strong&gt; An outside collaborator in one space, counted in Total users and not in Licensed users, and a clean way to take them out when the work ends.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;What to check on yours.&lt;/strong&gt; The Jira page in Atlassian Administration before and after the add: Licensed users shouldn't move.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;What this doesn't cover.&lt;/strong&gt; The guest's own view (we couldn't log in), Rovo and automation for guests, and the company-managed permission step, which we took from Atlassian's doc.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;I think the saving is mostly in new engagements. If you're on monthly billing, I'd make Guest - Collaborator the default for each new contractor, client or vendor who works in a single space, starting with the next contract you sign. If you're on annual billing, check before your renewal whether guests keep you below a tier boundary, because that's when it changes the bill.&lt;/p&gt;

&lt;p&gt;If you try this and your guest sees something different from what Atlassian's doc describes, I'd love to hear about it on the Community :)&lt;/p&gt;




&lt;p&gt;Originally published on &lt;a href="https://leanzero.net/tutorials/jira-guest-access?utm_source=devto&amp;amp;utm_medium=referral&amp;amp;utm_campaign=crosspost" rel="noopener noreferrer"&gt;leanzero.net&lt;/a&gt;. More Atlassian, Forge and local-AI write-ups at &lt;a href="https://leanzero.net/blog?utm_source=devto&amp;amp;utm_medium=referral&amp;amp;utm_campaign=crosspost" rel="noopener noreferrer"&gt;leanzero.net/blog&lt;/a&gt;, and if you're planning a migration or a Forge app, that's what we do: &lt;a href="https://leanzero.net/services?utm_source=devto&amp;amp;utm_medium=referral&amp;amp;utm_campaign=crosspost" rel="noopener noreferrer"&gt;leanzero.net/services&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>jira</category>
      <category>atlassian</category>
    </item>
    <item>
      <title>Jira Storage Limit: Uploads Blocked at 250 GB</title>
      <dc:creator>Mihai Perdum</dc:creator>
      <pubDate>Thu, 12 Nov 2026 05:59:09 +0000</pubDate>
      <link>https://dev.to/mihai_leanzero/jira-storage-limit-uploads-blocked-at-250-gb-33m8</link>
      <guid>https://dev.to/mihai_leanzero/jira-storage-limit-uploads-blocked-at-250-gb-33m8</guid>
      <description>&lt;p&gt;On 29 October 2026 Atlassian started rolling out a change called &lt;a href="https://community.atlassian.com/gateway/api/public/app-updates/v1/change-details/7oDOrs4ajMJpuvbUHIKsnq" rel="noopener noreferrer"&gt;Standard storage limit enforcement&lt;/a&gt; (that link opens Atlassian's change entry as raw data). Jira Standard sites have been getting storage warnings since at least 2023. What's new is the block: once a site reaches 100% of its 250 GB allowance, Jira blocks uploads until an admin deletes files or starts a 30-day Premium trial.&lt;/p&gt;

&lt;p&gt;So if you're a Jira Standard admin, check your usage on the Storage page in Atlassian Administration this week and find the work items with the heaviest attachments. I'd only pay for Premium if you want its other features too. At 200 users it's about USD 19,620 a year more on monthly billing, and that's a lot of money for disk space.&lt;/p&gt;

&lt;p&gt;If you searched for this before, you probably found the opposite advice. In May 2024 someone asked on the Community about &lt;a href="https://community.atlassian.com/forums/discussion/2696508/storage-limits-for-jira" rel="noopener noreferrer"&gt;storage limits for Jira&lt;/a&gt; (6,318 views when I checked on 10 November 2026) and wrote: "in the Jira admin portal, there is a statement that the storage limit is not being enforced." Atlassian staff said the same in at least five answers between 2018 and 2024, quoting Atlassian's own documentation at the time. That was true then. For Jira Standard it isn't any more.&lt;/p&gt;

&lt;p&gt;We measured what we could on our own Jira Cloud test site. It's on Premium, so it can't show the new block screen, and we haven't seen it. Every number below says where it came from.&lt;/p&gt;

&lt;h2&gt;
  
  
  Seven things we found: only uploads are blocked, and there's no add-on
&lt;/h2&gt;

&lt;p&gt;Each of these is argued further down, with its source.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Only uploads are named as blocked.&lt;/strong&gt; At "100% usage" the change entry says to "delete files or start a 30-day Premium trial to unblock uploads". It doesn't say anything else stops working.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;There's no storage add-on.&lt;/strong&gt; Atlassian's storage doc says "the only way to increase your storage is to upgrade your plan".&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The 250 GB is per app.&lt;/strong&gt; Jira and Confluence each have their own allowance, and the change entry lists Jira (&lt;code&gt;jira-software&lt;/code&gt;) only.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Most storage sits in very few places.&lt;/strong&gt; On our site one space held 93.4% of 63.41 MB of attachments.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Jira's own top-ten list missed one.&lt;/strong&gt; It skipped a business-space work item that our REST count ranked 8th.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Archiving a work item didn't free anything we could see.&lt;/strong&gt; Archiving is Premium and Enterprise only, and on our Premium site the archived 100 MB test item stayed on Jira's storage list.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Premium is USD 5,940 to 19,620 a year more&lt;/strong&gt; at 50 and 200 users on monthly billing.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  What changed on 29 October: Jira Standard's 250 GB storage limit is being enforced
&lt;/h2&gt;

&lt;p&gt;The change entry is short. It's marked "Rolling out" with a start date of 29 October 2026 and no end date, so your site may get it later than someone else's. The summary reads: "Jira Standard sites near or over the 250 GB storage allowance will see warnings and upload blocking in product and via email notifications. Admins can start a 30-day Premium trial, and non-admins can send a request asking an admin to upgrade, so teams have a path to keep uploads available."&lt;/p&gt;

&lt;p&gt;For admins it says to watch for warnings "sent by email, Slack, or in-product when the site is near or over the 250 GB allowance", and "If storage reaches 100% usage, delete files or start a 30-day Premium trial to unblock uploads." For everyone else: "If a warning or block appears when uploading a file, request an upgrade from an admin."&lt;/p&gt;

&lt;p&gt;It lists one product, &lt;code&gt;jira-software&lt;/code&gt;. Jira Service Management (JSM) isn't named, so I wouldn't assume a JSM Standard site is in scope. JSM's Free plan got a different rule in September, and it's also still rolling out. Since 11 September 2026, &lt;a href="https://community.atlassian.com/gateway/api/public/app-updates/v1/change-details/4UirIlwlh5vBpSqkdR8l7k" rel="noopener noreferrer"&gt;Service Collection&lt;/a&gt; (Atlassian's bundle of JSM and Customer Service Management) "automatically starts a 14-day trial of the Standard plan for Free plan instances that exceed the 2 GB storage limit". On JSM Free the trial starts by itself. On Jira Standard an admin has to start it.&lt;/p&gt;

&lt;p&gt;Atlassian's general storage doc, &lt;a href="https://support.atlassian.com/organization-administration/docs/track-storage-and-move-data-across-products/" rel="noopener noreferrer"&gt;Track storage and move data across apps&lt;/a&gt;, says what happens at the limit: "We won't remove any of your data, but some actions in Jira and Confluence will become restricted until you upgrade or free up storage." It doesn't name the actions. The change entry names uploads, and that's the only one I can point you to.&lt;/p&gt;

&lt;h2&gt;
  
  
  What happens when Jira storage is full: warnings, then blocked uploads
&lt;/h2&gt;

&lt;p&gt;I couldn't find the new warning or block wording in Atlassian's docs or on the Community as of 10 November 2026, and our Premium site can't trigger it. What admins pasted before still tells you what to look out for.&lt;/p&gt;

&lt;p&gt;In 2023 a Jira Cloud customer quoted a banner reading &lt;a href="https://community.atlassian.com/forums/discussion/2482264/storage-issue" rel="noopener noreferrer"&gt;"Your site is over the 250 GB storage limit"&lt;/a&gt;. In May 2024 the asker in the storage-limits thread quoted an email: "Your Jira Software site has reached 90% of its 250 GB storage limit on your Jira Software Standard plan. Once you reach 100%, you will either need to clear storage space from your site or upgrade to Jira Software Premium for access to unlimited storage." That 90% comes from one customer's inbox in 2024. The change entry itself only says "near or over".&lt;/p&gt;

&lt;p&gt;If you're not an admin and an upload fails with a storage message, the change entry says to request an upgrade from an admin. JSM has a &lt;a href="https://community.atlassian.com/gateway/api/public/app-updates/v1/change-details/4OgPWvF8tWUVZpyrL0ETvQ" rel="noopener noreferrer"&gt;Request a Premium trial&lt;/a&gt; flow, rolling out since the same day, that sends your billing admin a notification. Its entry lists only JSM, so I'm not certain the Jira storage block uses the same button.&lt;/p&gt;

&lt;p&gt;Atlassian has done this on another plan before. In October 2023 it announced it would enforce the 2 GB limit on Confluence Free, and the &lt;a href="https://confluence.atlassian.com/cloud/blog/2023/10/atlassian-cloud-changes-oct-23-to-oct-30-2023" rel="noopener noreferrer"&gt;cloud changes post&lt;/a&gt; said "you won't be able to create anything new in Confluence until you get more storage or upgrade". That was Confluence Free. Jira Standard's entry says upload blocking, and I wouldn't read the Confluence rule into it.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to check Jira storage usage, and what counts toward the 250 GB
&lt;/h2&gt;

&lt;p&gt;Before you start: you need to be a site admin. Atlassian's doc says "You must be a site admin to track storage." Everything below is Jira Cloud.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Go to &lt;a href="https://admin.atlassian.com" rel="noopener noreferrer"&gt;Atlassian Administration&lt;/a&gt; and select your organization if you have more than one.&lt;/li&gt;
&lt;li&gt;Open the site. If your admin home lists sites by name and URL (the original layout), select the site. If it has an &lt;strong&gt;Apps&lt;/strong&gt; menu (the centralized layout), select &lt;strong&gt;Apps&lt;/strong&gt;, then the site on the left.&lt;/li&gt;
&lt;li&gt;Under &lt;strong&gt;Site settings&lt;/strong&gt;, select &lt;strong&gt;Storage&lt;/strong&gt;. Each app shows the storage used and, if it isn't unlimited, the amount left.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fidbhjurihfctuw6oxxnp.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fidbhjurihfctuw6oxxnp.png" title="The Storage page in Atlassian Administration on our Premium test site, 10 November 2026. Read the line under the heading: changes take up to 30 minutes to show for Jira and up to 4 hours for Confluence. Jira and Confluence each have their own row." alt="Atlassian Administration Storage page for our test site: Jira Service Management Premium 0 of unlimited GB used, Jira Premium 62.0 MB of unlimited GB used, Customer Service Management Premium 0 of unlimited GB used, Confluence Premium 134.1 MB of unlimited GB used." width="800" height="640"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;On our test site, in the screenshot above, each app has its own row. That matches Atlassian's &lt;a href="https://support.atlassian.com/jira-cloud-administration/docs/configure-file-attachments/" rel="noopener noreferrer"&gt;file attachment doc&lt;/a&gt;: "The Standard plan allows up to 250 GB per app, and file storage is unlimited on Premium plans." Free is 2 GB per app. So Confluence Standard has its own 250 GB, and a big Confluence site doesn't eat into Jira's allowance. We searched all 1,086 entries in Atlassian's change feed and found no enforcement entry for Confluence Standard.&lt;/p&gt;

&lt;p&gt;What counts? Atlassian's storage doc says "This storage is primarily used for attachments" and doesn't list anything else. No current doc I found says whether avatars, app data, trashed spaces or archived work items count. If your Storage page shows a number you can't explain, you're not alone. A request for more detail, &lt;a href="https://jira.atlassian.com/browse/JRACLOUD-75922" rel="noopener noreferrer"&gt;JRACLOUD-75922&lt;/a&gt;, has 218 votes. It was raised in January 2021 and has been In Progress since September 2024.&lt;/p&gt;

&lt;p&gt;Two other limits get mixed up with this one. A single file defaults to 1 GB and can go up to 2 GB (&lt;strong&gt;Settings&lt;/strong&gt; &amp;gt; &lt;strong&gt;System&lt;/strong&gt; &amp;gt; &lt;strong&gt;Advanced&lt;/strong&gt; &amp;gt; &lt;strong&gt;Attachments&lt;/strong&gt;). And new sign-ups get a 7-day trial of Standard or Premium, which is a different thing from the 30-day Premium trial in the storage change.&lt;/p&gt;

&lt;h2&gt;
  
  
  Find large attachments in Jira: Storage management and a REST script
&lt;/h2&gt;

&lt;p&gt;Knowing you're at 240 GB doesn't tell you where it went, and Atlassian says so: "Currently, in Jira Cloud, Storage can be tracked per product but not per space." A space is what Atlassian used to call a project. There are two ways to find the heavy work items.&lt;/p&gt;

&lt;h3&gt;
  
  
  Jira's Storage management page lists ten work items, not always the top ten
&lt;/h3&gt;

&lt;p&gt;You need to be a Jira admin for this page.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;In Jira, select &lt;strong&gt;Settings&lt;/strong&gt; (the gear), then &lt;strong&gt;Products&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;Under Jira, select &lt;strong&gt;Storage management&lt;/strong&gt;. A table lists 10 work items with their &lt;strong&gt;Total attachment size&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;Select a work item to open it and remove the attachments you don't need. The page itself says: "To free up space, click on the work items and remove attachments, or upgrade for more storage".&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F3ieusfwnqsv5uqzt8hyf.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F3ieusfwnqsv5uqzt8hyf.png" title="Jira's Storage management page on our test site, 10 November 2026. There's no total and no space filter: it's ten work items and their attachment size." alt="Jira Storage management page listing ten work items with their total attachment size, from WFH-152 at 9.43 MB down to WFH-229 at 1.19 MB." width="800" height="680"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;On our site the page's sizes matched our REST count, rounded to decimal megabytes: WFH-152 holds 9,429,299 bytes and the page shows 9.43 MB. But the list wasn't complete. A work item in a business space (the kind Jira Work Management used to create) held 1,502,486 bytes, which our REST count ranked 8th, and it wasn't on the page at all. The page's 10th row was 1.19 MB. I don't know why. If your heavy files live in business spaces, don't rely on this page alone.&lt;/p&gt;

&lt;h3&gt;
  
  
  Atlassian's REST method gives you the full list per space (project)
&lt;/h3&gt;

&lt;p&gt;Atlassian has a knowledge base article on &lt;a href="https://support.atlassian.com/jira/kb/find-total-attachment-size-per-project-in-jira-cloud-using-rest-api/" rel="noopener noreferrer"&gt;finding total attachment size per project&lt;/a&gt;. It searches every work item with the JQL (Jira's search language) query &lt;code&gt;attachments IS NOT EMPTY&lt;/code&gt; and adds up the &lt;code&gt;size&lt;/code&gt; of each attachment. You need an API token for an account that can browse every space you want to measure and see its attachments. Admin rights alone don't guarantee that. The script pages through this request, 100 work items at a time:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;curl -s -u &lt;span class="s2"&gt;"you@example.com:$JIRA_API_TOKEN"&lt;/span&gt; \
  -H &lt;span class="s2"&gt;"Content-Type: application/json"&lt;/span&gt; \
  -X POST &lt;span class="s2"&gt;"https://your-site.atlassian.net/rest/api/3/search/jql"&lt;/span&gt; \
  -d &lt;span class="s1"&gt;'{"jql":"attachments IS NOT EMPTY","maxResults":100,"fields":["project","attachment"]}'&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Each work item in the answer carries &lt;code&gt;fields.attachment&lt;/code&gt;, a list with a &lt;code&gt;size&lt;/code&gt; in bytes per file. Add them up per &lt;code&gt;fields.project.key&lt;/code&gt;, and pass the &lt;code&gt;nextPageToken&lt;/code&gt; from each answer into the next request until &lt;code&gt;isLast&lt;/code&gt; is true. Our script did exactly that and wrote out per-space totals plus the ten largest files. If you go on to download the files themselves, the content endpoint answers with a redirect, which &lt;a href="https://leanzero.net/blog/atlassian-attachment-download-redirect?utm_source=devto&amp;amp;utm_medium=referral&amp;amp;utm_campaign=crosspost" rel="noopener noreferrer"&gt;we wrote up here&lt;/a&gt;.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;What we measured on our test site, 10 November 2026&lt;/th&gt;
&lt;th&gt;Result&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Work items on the site (approximate count)&lt;/td&gt;
&lt;td&gt;about 25,450&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Work items with attachments&lt;/td&gt;
&lt;td&gt;267&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Attachments&lt;/td&gt;
&lt;td&gt;632&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Time for the whole scan&lt;/td&gt;
&lt;td&gt;1.7 seconds, 3 pages&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Total attachment size&lt;/td&gt;
&lt;td&gt;63,412,642 bytes (63.41 MB)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Software spaces&lt;/td&gt;
&lt;td&gt;61.90 MB&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Business spaces&lt;/td&gt;
&lt;td&gt;1.52 MB&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Service spaces&lt;/td&gt;
&lt;td&gt;0&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Spaces holding attachments&lt;/td&gt;
&lt;td&gt;14 of 65&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Biggest single space&lt;/td&gt;
&lt;td&gt;93.4% of the total&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;So 1 work item in about 95 had an attachment, and one space held almost all of it. The largest file was a 9.30 MB screen recording. Three of the ten largest files were screen recordings, all from 2023, and the rest were PDFs, a zip and PNG images. Your site will have its own mix, so run the count before you decide what to delete.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fy4duxs56mrm1h3chsuo3.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fy4duxs56mrm1h3chsuo3.png" title="Illustration, generated locally with ERNIE-Image. In the site we measured, about 1 work item in 95 had an attachment, and one space held nearly all of it. The robot found the one loud box; the other ninety-four stayed quiet." alt="A blue robot with a clipboard and a magnifying glass inspects a long receding row of small grey boxes; one open box holds a giant red tomato that dwarfs the whole row, with a magnifier showing a bar chart, a film reel and blank papers on top of it, and a green bin at the end of the row, on a solid yellow background." width="800" height="448"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;The admin Storage page said 62.0 MB for Jira while REST added up to 63.41 MB. The software spaces alone came to 61.90 MB, which is closer, but no Atlassian source explains the gap, so I can't tell you whether business spaces count the same way.&lt;/p&gt;

&lt;p&gt;The REST method also has a blind spot. Atlassian's trash doc says work items in a trashed space "won't appear in basic or advanced search results", so a JQL scan can't see their attachments. We couldn't check whether trashed spaces still count toward storage: our nine trashed spaces gave nothing back over REST, and we had nothing to compare them with. Archived work items drop out of search too, while Jira's Storage management page kept listing our archived one at 100 MB.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to bulk delete attachments in Jira Cloud
&lt;/h2&gt;

&lt;p&gt;Deleting is the free exit, and it's permanent. Atlassian's doc says you can "back up the data of your apps before freeing up the storage space", so get a copy of anything you might need first. You've got two native options today, and a third is on the way.&lt;/p&gt;

&lt;h3&gt;
  
  
  Delete all attachments on one work item
&lt;/h3&gt;

&lt;p&gt;Open the work item, find the &lt;strong&gt;Attachments&lt;/strong&gt; section, select &lt;strong&gt;More actions&lt;/strong&gt; (···), then &lt;strong&gt;Delete all&lt;/strong&gt;. You need to be an admin to delete all attachments on a work item. Files pasted into fields or comments have to be removed one by one (&lt;a href="https://support.atlassian.com/jira-software-cloud/docs/delete-all-attachments-in-the-attachments-panel/" rel="noopener noreferrer"&gt;Atlassian's steps&lt;/a&gt;).&lt;/p&gt;

&lt;h3&gt;
  
  
  Delete old attachments with an automation rule
&lt;/h3&gt;

&lt;p&gt;Atlassian's &lt;a href="https://support.atlassian.com/atlassian-cloud/kb/how-to-use-automation-rules-in-jira-to-delete-attachments-from-old-issues/" rel="noopener noreferrer"&gt;knowledge base article&lt;/a&gt; builds the rule like this:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Go to &lt;strong&gt;Settings&lt;/strong&gt; &amp;gt; &lt;strong&gt;System&lt;/strong&gt; &amp;gt; &lt;strong&gt;Global Automation&lt;/strong&gt; and create a rule.&lt;/li&gt;
&lt;li&gt;Pick the &lt;strong&gt;Scheduled&lt;/strong&gt; trigger and give it a JQL. Atlassian's example is &lt;code&gt;attachments is not empty and updated &amp;lt; startOfDay("-7d")&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Add the &lt;strong&gt;Delete Attachments&lt;/strong&gt; action and set it to all attachments.&lt;/li&gt;
&lt;li&gt;Select &lt;strong&gt;Turn on rule&lt;/strong&gt; and give the rule a name. It runs on the schedule you set, and &lt;strong&gt;Run rule&lt;/strong&gt; runs it once straight away.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Atlassian's own warning is worth repeating word for word: "once you remove the attachments, there is no backup file or anything you can do to retrieve them." Its article also suggests "a more restrictive JQL query initially". I'd start with one space and a much older date, for example &lt;code&gt;project = ABC and attachments is not empty and updated &amp;lt; startOfDay("-730d")&lt;/code&gt;, and widen it once you've seen what it removed.&lt;/p&gt;

&lt;h3&gt;
  
  
  Bulk delete from the attachments panel is on the way
&lt;/h3&gt;

&lt;p&gt;It's marked Coming soon, with no date. The &lt;a href="https://community.atlassian.com/gateway/api/public/app-updates/v1/change-details/70XBZdg9h66A8ne0xxFfgX" rel="noopener noreferrer"&gt;change entry&lt;/a&gt; says "You can only bulk delete 25 attachments at once."&lt;/p&gt;

&lt;h3&gt;
  
  
  Trashing or archiving a space isn't a quick win
&lt;/h3&gt;

&lt;p&gt;A trashed space keeps its work items and attachments for 60 days before Atlassian deletes them permanently, and we couldn't confirm whether they count during those 60 days. Archiving a space is Premium and Enterprise only, so on Standard you can't archive new spaces.&lt;/p&gt;

&lt;h3&gt;
  
  
  Archiving a work item didn't take it off the storage list
&lt;/h3&gt;

&lt;p&gt;Archiving work items is only available on Premium and Enterprise. Atlassian's &lt;a href="https://support.atlassian.com/jira/kb/bulk-archive-issues-in-jira-cloud/" rel="noopener noreferrer"&gt;bulk archive article&lt;/a&gt; says "Archiving work items is available on Premium and Enterprise plans", so a Standard site can't archive work items. It matters if you're on a trial or already on Premium and wondering whether archiving old work frees storage, so we tested it on our Premium test site.&lt;/p&gt;

&lt;p&gt;At 00:57 on 10 November 2026 (Bucharest time) we created a task, LZPT-615, and uploaded one file of exactly 100,000,000 bytes. When we first opened Jira's Storage management page, 21 minutes later, LZPT-615 was at the top with 100 MB. Then we archived it. A JQL search for its key found nothing after that, while the REST API still returned it by key.&lt;/p&gt;

&lt;p&gt;Sixteen minutes after archiving, the Storage management page still listed LZPT-615 at 100 MB, as in the screenshot below, and a re-check at 28 minutes showed the same. The admin total couldn't tell us more. It said 62.0 MB right after the upload and still said 62.0 MB 54 minutes later, even though the page says changes may take up to 30 minutes. We archived at minute 21, so we can't tell whether that figure is slow or skips archived files.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fd9i0ffs2y0c06u9h91c5.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fd9i0ffs2y0c06u9h91c5.png" title="Jira's Storage management page on our Premium test site at 01:34 on 10 November 2026 (Bucharest time), 16 minutes after we archived LZPT-615. The archived work item is still the first row, at 100 MB." alt="Jira Storage management page with LZPT-615, Storage experiment 2026-11-10: 100 MB file (delete after), at the top with 100 MB, above WFH-152 at 9.43 MB." width="800" height="680"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;So if you're cleaning up to get under a limit, delete attachments, and don't count on archiving work items to free anything.&lt;/p&gt;

&lt;p&gt;After a cleanup, give the meter time. The admin page says changes may take up to 30 minutes for Jira, and on our Premium site the figure still hadn't moved 54 minutes after a 100 MB upload (we had archived that work item at minute 21, so part of that wait may be the archive, not the meter). In December 2025 a Jira Free admin &lt;a href="https://community.atlassian.com/forums/discussion/comment/3162907#Comment_3162907" rel="noopener noreferrer"&gt;reported&lt;/a&gt; the meter stuck at 2 GB after deleting attachments, and a Community Champion replied that updates can take a day or two.&lt;/p&gt;

&lt;h2&gt;
  
  
  Jira Standard vs Premium pricing: is cleanup cheaper than the upgrade?
&lt;/h2&gt;

&lt;p&gt;Premium removes the limit, and there's nothing smaller to buy. The prices below are Atlassian's list prices in USD from its &lt;a href="https://www.atlassian.com/licensing/future-pricing/cloud/list/pricing-tables" rel="noopener noreferrer"&gt;cloud pricing tables&lt;/a&gt;, effective 13 October 2026. Monthly billing is progressive: each of your first 100 users costs more than each user from 101 to 250.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Jira Cloud, list price&lt;/th&gt;
&lt;th&gt;50 users&lt;/th&gt;
&lt;th&gt;200 users&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Standard, monthly billing&lt;/td&gt;
&lt;td&gt;USD 485 a month (50 × 9.70)&lt;/td&gt;
&lt;td&gt;USD 1,790 a month (100 × 9.70 + 100 × 8.20)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Premium, monthly billing&lt;/td&gt;
&lt;td&gt;USD 980 a month (50 × 19.60)&lt;/td&gt;
&lt;td&gt;USD 3,425 a month (100 × 19.60 + 100 × 14.65)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Extra for Premium, per year (monthly billing)&lt;/td&gt;
&lt;td&gt;USD 5,940&lt;/td&gt;
&lt;td&gt;USD 19,620&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Standard, annual tier&lt;/td&gt;
&lt;td&gt;USD 4,850&lt;/td&gt;
&lt;td&gt;USD 18,000&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Premium, annual tier&lt;/td&gt;
&lt;td&gt;USD 9,800&lt;/td&gt;
&lt;td&gt;USD 34,500&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Extra for Premium, per year (annual)&lt;/td&gt;
&lt;td&gt;USD 4,950&lt;/td&gt;
&lt;td&gt;USD 16,500&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;What you'd actually pay on an upgrade depends on what you've already paid. Atlassian's own note says "Plan and user tier upgrade pricing depends on what you've previously paid."&lt;/p&gt;

&lt;p&gt;A cleanup costs admin hours and no licence money. We haven't timed one on a real 250 GB site, so I won't put a number on it. But at 200 users, USD 19,620 a year buys a lot of afternoons spent deleting old screen recordings.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fxx7dv2gvhkc9gonjehml.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fxx7dv2gvhkc9gonjehml.png" title="Illustration, generated locally with ERNIE-Image. Clearing storage costs admin hours and no licence money, while Premium at 200 users is USD 19,620 a year. The robot on the crate got through a lot of recordings for free." alt="A split panel: on the left a blue robot hands a tall stack of gold coins to a violet shopkeeper robot at a red-awning stall, who points up at a price board of blank tags; on the right a green robot sits on a yellow crate, tiredly stuffing film reels, floppy discs and papers into an enormous grey sack that towers over it, with a round wall clock and an untouched coin jar beside it." width="800" height="448"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Premium does a lot more than storage, of course. If you already wanted its other features, the storage limit is one more reason, and our &lt;a href="https://leanzero.net/blog/jira-premium-vs-enterprise-pricing-200-500-seats?utm_source=devto&amp;amp;utm_medium=referral&amp;amp;utm_campaign=crosspost" rel="noopener noreferrer"&gt;Premium vs Enterprise pricing at 200 to 500 users&lt;/a&gt; goes into those. If you're also budgeting for usage-based charges, our &lt;a href="https://leanzero.net/blog/atlassian-usage-based-pricing-budget-2027?utm_source=devto&amp;amp;utm_medium=referral&amp;amp;utm_campaign=crosspost" rel="noopener noreferrer"&gt;cost per user at 50 to 500 seats&lt;/a&gt; has the numbers.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I'd do this week on a Jira Standard site
&lt;/h2&gt;

&lt;p&gt;Open the admin &lt;strong&gt;Storage&lt;/strong&gt; page and write down the Jira figure with the date. Take a second reading a few weeks later, and the difference tells you how fast you're growing and how often you need to look.&lt;/p&gt;

&lt;p&gt;If you're close, open Jira's &lt;strong&gt;Storage management&lt;/strong&gt; page, then run Atlassian's REST method, because the page only shows ten work items. Back up what you might need. Then clean up with a narrow automation rule.&lt;/p&gt;

&lt;p&gt;And keep the 30-day Premium trial for when uploads are actually blocked and the cleanup can't finish in time. Once it starts, the clock runs.&lt;/p&gt;

&lt;p&gt;Has your site already hit the new warning? If you've seen the wording, I'd love to know what it says, because I haven't found it posted anywhere yet. You can find me on the &lt;a href="https://community.atlassian.com" rel="noopener noreferrer"&gt;Atlassian Community&lt;/a&gt; or reach us at &lt;a href="https://leanzero.net?utm_source=devto&amp;amp;utm_medium=referral&amp;amp;utm_campaign=crosspost" rel="noopener noreferrer"&gt;leanzero.net&lt;/a&gt;.&lt;/p&gt;




&lt;p&gt;Originally published on &lt;a href="https://leanzero.net/blog/jira-storage-limit-250-gb?utm_source=devto&amp;amp;utm_medium=referral&amp;amp;utm_campaign=crosspost" rel="noopener noreferrer"&gt;leanzero.net&lt;/a&gt;. More Atlassian, Forge and local-AI write-ups at &lt;a href="https://leanzero.net/blog?utm_source=devto&amp;amp;utm_medium=referral&amp;amp;utm_campaign=crosspost" rel="noopener noreferrer"&gt;leanzero.net/blog&lt;/a&gt;, and if you're planning a migration or a Forge app, that's what we do: &lt;a href="https://leanzero.net/services?utm_source=devto&amp;amp;utm_medium=referral&amp;amp;utm_campaign=crosspost" rel="noopener noreferrer"&gt;leanzero.net/services&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>jira</category>
      <category>atlassian</category>
      <category>storage</category>
      <category>attachments</category>
    </item>
  </channel>
</rss>
