Review unused access
Use separate policies for Confluence, Jira and Jira Service Management agents. Review recorded access, activity gaps and protection before deciding what can be released.
Policy and activity guidePut unused Atlassian licences back to work.
Manage Confluence, Jira and Jira Service Management agent access, with separate rules for each app.
Set a separate inactivity policy for each managed app. Define its allowance, warning period and restore protection, and exclude specific people from automatic inactivity release.
The engine keeps unknown activity and uncertain changes visible. Existing access, reserved returns and unconfirmed writes stay accounted for in the seat pool.
Read the release conditionsA seat is reclaimed only after access is verified absent.

For administrators managing a shared seat pool, identity teams maintaining group membership, and people returning to work.
Use separate policies for Confluence, Jira and Jira Service Management agents. Review recorded access, activity gaps and protection before deciding what can be released.
Policy and activity guideKeep a SCIM-managed group as the eligibility source. Map a separate writable group to paid access, and preview wider group-routing rules before publishing them.
Group ownership and routingGive members a place to review their allowance and book time away. A confirmed protected return holds capacity for their scheduled return, with the actual booking state visible.
Member and return journeysCost Slasher manages membership in your approved app-access groups. It does not suspend Atlassian accounts or remove existing page, project or work item permissions.
My access, a recovery journey and protected returns from time away.
Open Apps → Cost Slasher in Jira or Confluence to see your recorded access, inactivity allowance and next permitted action. Check access or request restoration explicitly; signing in does not grant a seat.
If access is denied, the organisation's Atlassian access message links to a dedicated recovery website. Sign in with Atlassian is still the first choice there, but Atlassian refuses it for an account with no Jira or Confluence product left on any site. If Cost Slasher released your only seats, the recovery website therefore also accepts a browser you asked it to remember or a code sent to your work email. After a verified restore, return to the original page or work item. Space and project permissions still apply.
Set up the remembered browser while you still have access: open My access, choose Open the recovery page under Keep a way back in, sign in, then choose Remember this browser for recovery. Forget this browser or Use another account removes it again. Sign out everywhere on the recovery page ends every recovery sign-in and remembered browser you have for that company, and a privacy deletion request ends them too.
Read the member journeyChoose the apps, departure, return date and time zone. Preview the return, then confirm a time-away booking separately.
A confirmed protected return reserves its seat while you are away. Restoration is scheduled before the recorded return, subject to current eligibility and provider availability.
How a protected return worksThe configured Atlassian access message provides the recovery link where that denial surface supports it.
Use Sign in with Atlassian, a browser you remembered earlier, or an 8-digit code sent to your work email. The page then shows only your own licences.
Check eligibility if needed, then choose Restore. Restore checks your eligibility and the free seats again before anything changes.
Wait for the recorded verified result, then reopen the app or your original page. A queued request is still pending.
The recovery website is hosted outside Atlassian. A guest account or a Jira Service Management customer portal is not the recovery entry point. Administrators configure the Atlassian access message with the URL Cost Slasher gives them, and test the actual route for each managed app before relying on it.

A SCIM-managed group establishes eligibility. A separate, explicitly writable group controls the selected paid app.
Preview Add, Mirror or Move rules before publishing them. Routing tracks its own contributions, preserves other owners and verifies a destination before removing an approved source membership.
Identity provisioning decides eligibility. Cost Slasher uses a separate, explicitly writable destination that grants exactly the selected paid app on your bound site. It does not turn a SCIM-managed group into an app-writable group.
Routing records its own contribution. Manual access and contributions from another rule stay distinct; removing a rule offers an explicit choice to retain memberships or clean up only its verified contributions.
Rules reconcile memberships in bounded background work. Inspect the preview scope and continuation, then follow the job and recorded result. A partial preview or queued change is not a complete directory outcome.
Install from Marketplace, open Apps → Cost Slasher, and follow the administrator setup guide.
A Jira site administrator starts the installation. Organisation administration access is needed for the organisation and directory IDs, an Admin API key, the intended eligibility sources and dedicated writable access groups.
Confluence and Jira Service Management are optional managed apps. Jira Service Management means paid agent access; customer portal use is a different role and does not establish agent activity.
The Admin API key is saved in encrypted Forge secret storage and never leaves Forge. When the recovery website checks an email code or a remembered browser, your installation looks the person up in your directory with that key. The recovery service never receives it.
Connection requirementsRun the native installation safety check and read its current result. Wait for this installation to report storage ready.
Save your organisation and directory, store the Admin API key, request recovery pairing from LeanZero and check the connection.
Preview one app mapping and its seat limit, apply the reviewed mapping, and verify complete adoption of existing seats.
Save the recovery message in Atlassian Administration. Use an ordinary account to test denied access, sign-in, restoration and return.
Automatic release starts off. Verify activity, delivered warnings, recovery and capacity before enabling it for an eligible app.
The app highlights the next missing requirement and opens its setup control. A healthy API-key check verifies the configured directory; it does not prove group writability or successful restoration.
A management brief for your stakeholders, with the original events available to inspect.
Prepare a PDF, CSV or JSON management report for a chosen period and app scope. It separates verified access changes from already-present or absent access, and includes trends, dated capacity, source definitions and controls needing attention.
Management downloads contain aggregates without individual account identities. Optional seat-price assumptions produce a labelled planning estimate, with its observation dates and limits attached.
What the management report containsFilter the audit by date, app, category, outcome, entry point, exact account or reference. Open an event to see its action, reason, recorded and occurrence times, and available safe details.
Export all matching retained events as CSV or JSON, including the frozen filters and recording cutoff. A request accepted, a provider acknowledgement and a verified access change remain separate stages.
Explore audit and export controls
One workspace, with navigation and actions matched to the person's assigned site and app scope.
Members manage their own access and bookings. Operators handle scoped licence operations. Routing managers work within approved group boundaries, auditors inspect and export, and administrators manage configuration and permissions.
Read the role boundariesIssue a named token with an expiry, selected apps and explicit capabilities. Integrate access, policies, routing, reports and audit through the same command handlers, previews and version checks used by the native app.
Explore the REST guideConsumption shows its observation window and collection sources. Records handled and observed payload bytes are named for what was measured. Missing measurements remain unavailable; partial coverage stays visible.
Understand the figuresMembers can request their own data or deletion and inspect the resulting request. Access safety and audit records are retained as disclosed. What's new carries the application release notes inside the workspace.
Privacy and support guideA native Forge workspace, with a separate recovery service and explicit checks before paid access changes.
The Jira and Confluence workspace and business records run on Atlassian Forge. Recovery identity, the controller registry, shared organisation request budgeting and minimal notification processing use AWS Ireland, with CloudFront transit.
The organisation Admin API key stays in Forge secret storage. The external recovery service establishes who is asking through Atlassian sign-in, a browser the person remembered earlier, or an email code checked against your directory. A successful sign-in does not grant a seat.
Read the data boundaryLonger work is processed in bounded pages and tracked by its original reference. The engine rechecks permissions, eligibility, ownership and capacity. Unknown provider outcomes remain unresolved until reconciled.
Warnings, provider acknowledgements and verified access changes are separate events. Seat-value estimates are planning assumptions, and synthetic load tests do not certify live 20,000-user throughput.
Follow operations and resultsProduction walkthroughs recorded on our demo site in the released 0.4.4 app.
Find the recovery URL and native access message, then read the ordinary-user checks required before relying on returning-user recovery. This walkthrough does not publish the message or restore access.
Watch on YouTubeFind a person within your assigned scope and inspect their recorded app access. Read the impact required for an explicit access change without submitting one.
Watch on YouTubeApply an exact action filter and inspect the original event. Read occurrence time, recording time, actor and outcome without treating a recorded request as a verified access change.
Watch on YouTubePrepare a filtered audit export and inspect its original CSV, JSON and manifest parts. Follow the same recorded request and matched event scope through the download.
Watch on YouTubeCost Slasher is available on the Atlassian Marketplace. It is permanently free for sites with up to ten Jira users. From 11 users every user is charged: USD 0.10 per user per month, whatever the size of the site.
Cost Slasher 0.4.23 is deployed to production as Forge 3.14.0 (Marketplace version 3.14.0). People whose only seats were released can now get back in to the recovery website with a remembered browser or an email code, because Atlassian's own sign-in refuses an account with no product left. Administrators can switch the email codes off. On 15 October 2026, Atlassian approved the app listing and its Privacy and Security declaration, and Cost Slasher was released on the Atlassian Marketplace. Automatic licence release starts disabled. Complete storage-first setup and verify activity, warning delivery and returning-user recovery for your installation before enabling it. Saved pricing includes a permanent free tier for up to ten Jira users; paid pricing applies above ten.
These guides cover the current paid beta, including workspace subscription guidance, storage-first setup, Saved requests and background-work status. Check What’s New in your installation for its authored version and release notes. Open the chapter you need and follow its prerequisites for each managed app.
Sites with up to ten Jira users use Cost Slasher free of charge, permanently: USD 0 per month and USD 0 per year. This is not a time-limited trial. Above ten users, paid pricing applies. It is priced close to what it costs us to run the app: the AWS and Forge compute it uses, plus the Marketplace fee. The saved Marketplace pricing includes this permanent small-site free tier. Confirm the final price and billing interval on the Marketplace before subscribing. Run costs vary with managed population, activity pages and retries; a Jira billing tier does not determine the number of people managed in Confluence or Jira Service Management. Your Atlassian subscriptions remain separate; this page does not start a subscription.
Above ten Jira users, the monthly total is USD 0.10 for each user, at every site size. The free tier applies to a site with up to ten users; the first ten users are not deducted from a larger site's bill. For example, 11 users is USD 1.10 per month, 100 users is USD 10 per month and 2,500 users is USD 250 per month. Marketplace sets annual rates automatically at ten times the monthly rate, so 2,500 users is USD 2,500 per year. These examples are derived from the rate above, not a separately observed customer quote. The price does not certify managed-user capacity. Confirm the final quote on the Marketplace before subscribing.
Install Cost Slasher from the Atlassian Marketplace, then follow Administration → Setup. Start with Storage safety, connect the organisation and map each managed app. Contact LeanZero if you need help with your site, identity groups or recovery journey.
The screenshots and tutorials come from the released 0.4.4 app, installed as Forge 3.2.0 on our demo site. The screenshots show the actual policy editor, recorded access and protected return, and a report with one verified Confluence removal and one grant for the displayed period. Each tutorial describes the controls and recorded result shown in that workflow.
It starts disabled. Complete access adoption, verified app-specific activity, confirmed warning delivery and tested returning-user recovery are required. Jira Service Management automatic agent reclamation stays disabled until agent-activity evidence exists.
Test the full returning-user journey for your installation: the access-denied message, recovery sign-in, restoration and protected return from time away. Check app-specific activity and warning delivery, then preview and test your group-routing rules. Keep automatic release disabled until these checks succeed.
Yes, as the read-only eligibility source. Paid access must use a separate explicitly writable group in the configured directory, granting exactly the selected app on the bound site. Cost Slasher does not take over SCIM ownership or create an account in another directory.
No. The recovery entry is a dedicated website. Administrators configure the access-denied message in Atlassian Administration with the URL Cost Slasher gives them, and test the actual route for each managed app. People sign in there with Atlassian, with a browser they asked it to remember, or with an email code. Signing in does not restore a licence automatically: the person explicitly checks or requests access, and existing space and project permissions still apply.
On the recovery page, the person types their work email. If Cost Slasher released their access on that company's site, an 8-digit code goes to that address. It works once, within 10 minutes, in the same browser that asked for it, and the email carries no link. The page gives the same answer whether or not the address exists. No code is sent while any of the organisation's installations can't be reached. Codes also pause by themselves if code emails draw complaints or hard bounces, and the page then says “Email codes are paused for now”.
Yes. Recovery sign-in by email code, under Administration → Support and privacy, is on by default and applies to the whole organisation. Turning it off on any installation stops new codes everywhere at once and ends browsers that were remembered after an email code. Organisations that require single sign-on or two-step verification for every sign-in can switch it off, because a code only proves access to the mailbox. Turning it back on can take up to 10 minutes. Sign in with Atlassian and browsers remembered after it keep working.
Cost Slasher manages Jira Service Management agent seats. A customer portal account is a different access model. Agent inactivity reclamation remains disabled without reliable agent-activity evidence; ordinary Jira activity and customer portal use cannot substitute for that evidence.
Use the Cost Slasher support portal for recovery pairing, setup questions and a request that needs investigation. Include the app and its recorded request reference, with no API keys, pairing exports or tokens. The manual below covers the member, administrator and REST journeys.
The native workspace and business records use Atlassian Forge. Recovery identity, controller registry, shared organisation budgeting and notification processing use AWS Ireland, with CloudFront transit. The organisation Admin API key stays in Forge secret storage. Read the dedicated privacy disclosure for the full boundary.
No. A capacity value estimate is a planning assumption, not an invoice saving. Local synthetic tests do not certify 20,000-user tenant throughput; deployed scale and physical headroom remain separate checks.
Read the published product privacy policy, paid terms and customer data processing agreement before planning an installation.
40 chapters covering member access, administration and REST integration for the paid beta. Start with the setup guide and follow the prerequisites for your managed apps.
This guide covers Cost Slasher paid beta, available on the Atlassian Marketplace. Manage inactivity policies, self-service restoration and protected returns for Jira, Confluence and Jira Service Management agent access. Open Apps → Cost Slasher in Jira or Confluence. Sites with up to ten Jira users are permanently free, monthly and annually. From 11 users every user is charged: USD 0.10 per user per month at every site size, annual is ten times monthly, and Atlassian subscriptions remain separate. Automatic inactivity release starts disabled. Administrators should begin with Administration → Setup → Storage safety, then connect the organisation, map access groups and test activity, warnings and returning-user recovery before enabling release.
In the paid build, fresh access checks, allocations, configuration and automation require the server's trusted Marketplace context to report an active Cost Slasher licence. A trial or other no-charge entitlement is valid only when Atlassian reports license.active: true; a missing or unknown value is refused. Opening a page, an OAuth identity grant or a Cost Slasher REST token does not purchase a subscription or confer licence authority. Current account, scope, permissions, eligibility, storage and provider safeguards still apply.
The workspace shows one Cost Slasher readiness notice before page actions when the server reports an inactive subscription or unverified availability. It distinguishes the app subscription from Jira, Confluence and Jira Service Management seats and tells members to contact their administrator. Incomplete paid status is described as unavailable, not inactive. The notice does not change your role or bypass any request, download, recovery or protected-return check.
Recorded-result reads remain subject to current permissions. Narrow safety handling preserves an exact proven prior-release recovery or fully held return commitment, issued-effect readback and genuine security compensation after licence lapse; it is not a general unlicensed grant. Read the original operation's result rather than assuming a restore.
In Jira or Confluence, choose Apps → Cost Slasher. My access opens first; its heading is Your access. Jira Service Management agent access appears separately through the Jira entry. The views and actions available to you follow your Cost Slasher permissions.
The app follows Jira or Confluence's theme automatically. Change it through that app's Profile → Theme control.
Each configured Confluence, Jira or Jira Service Management app shows your recorded access status, inactivity allowance, last observed activity and permitted next action. Jira Service Management access means an agent seat, not customer portal access. Reasons, warning deadlines, protection, planned returns and current operations stay visible. Activity unavailable means the app has no verified activity observation; it does not mean you have been inactive. Expand Access details for the last verification time and seat-pool state.
Expand How inactivity works for the release conditions. An inactivity allowance alone does not enable automatic release. Release requires enabled app automation, verified inactivity, confirmed warning delivery, the configured warning period and fresh eligibility, activity and protection checks.
Last verified access status describes the earlier access observation. Opening this page does not check current eligibility or recent app activity. An unverified status does not prove that access is absent; use the separate access check when offered, or ask your administrator to review the stated reason.
Use the action offered for the relevant app. Check my Confluence access, Check my Jira access or Check my agent access in the Jira Service Management row checks current eligibility without granting a seat. Assistive technology announces the agent button as Check my Jira Service Management agent access. After an eligible check, choose Restore Confluence, Restore Jira or Restore agent access separately. A Check and restore action performs the required fresh checks as part of your restoration request.
Read the actual operation result. Request recorded or Processing finished does not mean access has been restored. If no seat is available, check the waiting request's expiry and cancellation option. Do not submit another request to bypass an uncertain change. Once the result says Access restored, use the app link or return to your original page or work item tab and refresh. Space, project and work item permissions still apply.
If you cannot enter the app, your organisation's configured access-denial message can link to its recovery website. Use Sign in with Atlassian and check the displayed account, site and app before requesting restoration. Sign-in alone grants nothing.
Atlassian's sign-in refuses an account that has no Jira or Confluence product left on any site ("Access denied ... requires access to a User identity site"). That is often the case once Cost Slasher released your only seats, so the recovery website offers two other ways in:
Either way the page then shows only your own licences, and Restore still checks your eligibility and the free seats first.
An unconfirmed result is neither a verified restoration nor proof that the request made no change. Keep its original reference and use the offered original-request check or retry. Read the accompanying explanation before starting any further change.
If a native change loses its response, open Saved requests in the workspace and choose Check saved request. The browser retains request references across navigation and reload, tied to your current account, site, installation, app and environment. It saves no form values, credentials or one-time secrets. This check uses your current permissions and reads the original request; it does not submit the change again.
When offered, choose View recorded operation, View recorded request or View recorded storage check to inspect the actual result, then Refresh recorded work if it is still in progress. A recorded request is not proof that access changed. If the server cannot find an acceptance record, follow Return to action and the displayed guidance. Where a retry is permitted, re-enter the exact original input and reviewed version to use the retained reference; changed input is blocked while that intent remains unresolved. An unknown result does not mean no effect. Only an explicit server-confirmed no-effect result establishes that nothing was changed by that request.
Keep in recorded work removes this browser's entry after a fresh check of the retained server work. It does not cancel or complete that work. Your requests is the separate durable request history. Saved requests does not transfer to another account or installation and cannot recover a one-time credential secret.
Choose Plan time away or open Time away. The shortcut opens planning after this page's access records load and at least one app permits a booking. After your access records load, if no app permits a booking, Plan time away stays disabled. Review the recorded reasons and use Review my access, or contact your administrator if that action is unavailable. The app does not open an unusable form. Loading remains a check in progress; a failed prerequisite offers a retry. An empty visible booking page with Next page asks you to continue through your bookings, not assume there are none. For permitted apps, select Apps, Departure, Return and Time zone, then choose Preview return. The dialog reveals and focuses the original check result. An unblocked preview has not reserved a return seat yet; blocked previews show the specific checks to resolve. Choose Confirm time away separately after reviewing the result. Inspect each booking's result: a pending booking is not a guaranteed return. A confirmed protected return keeps its seat reserved while you are away; restoration is scheduled to start 30 minutes before the recorded return, subject to current eligibility and provider availability. Protection follows the confirmed booking's actual terms. Use the booking's edit, cancel or I'm back early action when permitted.
Cancelling does not undo access work already started. Any access already restored is kept. Check the booking and your access status afterwards: a recorded cancellation may still need verification, and does not prove that its return seat reservation was released.
Choose View access history beside the Your access heading to bring the history section into view and move keyboard focus there. It does not check or change access. Your access history shows at most five visible events per page, newest recorded first. Known actions use readable labels, including Generate management report, Export audit and Check own app access. Request accepted, Result recorded and Processing finished describe recorded processing stages; they do not prove that a licence changed. The timestamp shows when the action happened. A delayed event can be recorded recently while showing an older action time; hover over the timestamp to see its Recorded time when the two differ.
Use Next page for earlier recorded events and Previous page to return. Page numbers describe visited pages, not a known total. If a page has no visible events but still offers Next page, continue; that page does not prove the remaining history is empty. During loading or a failed read, the requested page's events are unavailable; use the offered retry to check again.
Your requests loads its history only when you first open it; that history is not fetched for the initial collapsed My access view. It shows up to five durable requests per page. Use Open management report or Open audit export to retrieve the original prepared file. Inspect request remains beside these actions for the original processing status, reason, outcomes and available chunks, including earlier formats. Processing finished does not guarantee successful licence changes, delivery or deletion. Closing this panel retains your selected and in-flight processing result while you stay on My access; it does not cancel the request. Reloading or leaving the page does not promise to retain the open panel or its selected result.
Open Your data and privacy to request your own records or record a deletion request. Cost Slasher processes deletion requests to remove cached names and email addresses and expire personal exports; access safety and audit records are retained. Inspect the request result, including any pending recovery-session revocation. Your Atlassian account and app access are unchanged. Closing the panel preserves its in-flight result while you stay on the page.
If your assigned role includes reporting, open Reports, choose Period and the permitted App. For Custom dates, enter From date and the inclusive Through date before choosing Generate report. Reporting periods use UTC and may cover up to 366 days. Read the prepared brief and use Download PDF, Download CSV or JSON. Management downloads contain aggregates without individual account identities. The PDF is designed for sharing with management and includes verified access removals and grants, app outcomes, a daily trend, controls needing attention, separately dated capacity and source definitions. Expand Current capacity and planning estimate for each app's observation and reason; expand Sources, scope and metric definitions for the exact interval, recording cutoff, definitions and historical coverage limits.
The chart's Highest daily removals or grants is the largest count of either outcome on one UTC day, rather than the period total or the sum of removals and grants. One removal and one grant on the same day gives a scale of 1 while the period summary retains both outcomes.
Already-absent or already-present access is not counted as an access change. Missing historical write evidence stays Change origin unverified. Pending figures count recorded events, not outstanding cases or distinct people. An administrator can add an optional monthly seat-price assumption; its estimated free-capacity value is a planning estimate and does not prove invoice savings.
The management CSV contains summary, per-app outcome, daily trend, entry-point and purpose sections, dated capacity figures and reasons, source notes, metric definitions and estimate status. Keep these context rows with the figures when sharing or importing the spreadsheet. An unavailable capacity or value stays unavailable; an empty value does not mean zero. JSON preserves the complete aggregate report with its exact machine values.
For authorised auditors and administrators, Audit shows at most 20 events per page, newest recorded first. Edit Search, Period, Event category, Outcome and App, then choose Apply filters. Reset returns to the default period and starts paging again. Dates filter when the event occurred, from the first UTC day through the last. More filters adds entry point, exact actor and affected-account references, an event/object/operation reference search and exact action and outcome codes. An exact outcome code overrides the selected outcome category. Inspect opens the original action and outcome, occurrence and recording times, actor, affected account, product/site/object/version/operation references, reason and available safe structured details. Historical fields appear only when they were recorded. A command acceptance, provider acknowledgement and verified change are separate recorded stages.
Event and Outcome use readable labels for known codes. Request accepted, Result recorded and Processing finished do not confirm that access changed or a notification was delivered. Access present (verified) or Access absent (verified) describes the observed state, which may already have existed; it does not by itself prove that Cost Slasher made a membership change. Inspect → Exact action and Exact outcome, exact-code filters and CSV/JSON downloads keep the original codes. Unknown codes appear unchanged.
The App filter offers only apps covered by your current audit permissions. All assigned apps reads the records permitted by the server. Missing permission metadata disables app selection and preparation until you reload and check your permissions; saved filters and older exports are preserved.
Choose Download matching events, review Export app and the readable Export filters summary, then choose Prepare export. An explicit applied app filter is kept. If your authority permits separate app exports, select an authorised app for this file; the sole permitted app is selected for you. All assigned apps is available for export only when your current grant covers every app. This export choice does not change the live Audit view or previous exports. Expand Exact filter details only if you need the exact final machine filters. Download complete CSV or Download JSON retrieves every matching retained event across all pages, not only the visible page. The request freezes its original filters and recording cutoff. Changing the explorer's filters leaves that prepared export unchanged; prepare another export to download a different set of events.
Audit CSV has one export-metadata row and then event rows, identified by the recordType column. Keep the metadata row: it carries the original filters, cutoff, available-until time, complete-export totals and evidence limits, even when there are zero events. Filter recordType to event when analysing the event rows. JSON includes the same manifest and exact safe event values. Audit files contain individual actor and affected-account references; management reports contain aggregates.
Downloads verify every part and recheck your current role, ownership and expiry after formatting. Expired, missing or altered parts cannot produce a misleading complete file. The available-until time describes the prepared file's retrieval window in the app. During a report or audit download, only the selected action shows progress; the other download actions wait until it finishes. Download manifest is beside the whole-file audit downloads. For exports above the 32 MiB whole-file limit, expand Saved filters and numbered parts to inspect the saved filters and download individually validated parts. Each numbered CSV identifies its part and this file's event count separately from the original export total; it does not claim to contain the whole export. Import reference columns as text in spreadsheets. Retention or previously unpublished evidence can leave historical gaps; an empty retained result does not establish that nothing happened.
Prepared reports lead the Reports page, with their original period and apps attached. New report settings keeps preparation secondary; Prepare another report opens and focuses those settings. Opening optional settings generates nothing until you choose Generate report.
Choosing Generate report or Prepare export again checks the earlier recorded request before starting a new one. You can prepare another file with the same settings or different settings directly from Reports or Audit. The earlier request stays in Your requests. If its response was lost or its reference cannot be verified, use Saved requests before changing the input; the app does not replace an uncertain request with a new reference.
You can move between Reports, Audit and other app pages and return to the original prepared report or export within the current workspace session. Audit retains draft inputs and applied filters separately; Original export filters stays beside the original file's downloads. Returning retrieves the same owned request; it does not submit another preparation intent. A role change or expired result can still block retrieval or download. Browser reload or a new session clears selected references; Your requests → Open management report or Open audit export reopens an original durable request using fresh ownership, permission and expiry checks. Earlier requests may require paging. Automatic status checks pause while the tab is hidden, resume when you return and stop after 20 visible checks per open request view. Use Refresh report or Refresh export if checks have paused. Checking status, Preparing, Expired and unavailable-download guidance describe different conditions; an expired complete file is never represented as preparing.
Open What's New for the installed build's authored release notes. Use the version displayed in your installation when reporting a problem. The current and historical release entries describe their own authored versions. Expand Earlier releases to read the retained history. The App release footer opens the same page and shows the authored version; Forge deployment numbers and production acceptance are separate. When reporting a problem, expand the displayed operation, request or error reference and use Copy reference. Contact your organisation's administrator or LeanZero support. Never include credentials or recovery pairing secrets.
Free for sites with up to ten Jira users. From 11 users every user is charged: USD 0.10 per user per month at every site size. Your Atlassian subscriptions are billed separately.