ArtUp Labs

ArtUp Release for Jira Cloud

One release across many Jira projects

Put your Jira projects into a program and name a lead project. Create a version there, rename it, change its dates, release or archive it — ArtUp Release repeats it in the same-named version of every project in the program, usually in seconds, up to a few minutes. On top: readiness of the release by project, release notes in Markdown, Word and PDF, and a snapshot taken at release. Your teams keep working in Jira's own Releases page, Fix versions, JQL and boards. The app writes only project versions, never your issues.

How it works What it does Documentation

Coming to the Atlassian Marketplace. Sites with up to 10 users will use it free.

  • Nothing leaves Atlassian
  • Free for up to 10 users
  • 2 to 100 projects per program
  • Company- and team-managed
  • 26 languages, light and dark
// Lead project WEB: you release version 2.4 in Jira's own Releases page
WEB   2.4   Released

// ArtUp Release repeats it in every project of the program
API   2.4   Released   In sync
MOB   2.4   Released   In sync
OPS   2.4   Released   Waiting to sync

What it does

Teams that ship one product from several Jira projects create, rename and release the same version by hand in every project. ArtUp Release does it once, and shows the whole release in one place.

  • Create a version once, get it in every project

    Whatever you do to a version in the lead project — create, rename, change the description or the start and release dates, release, unrelease, archive, unarchive — is copied to every project in the program. Copies are linked to the lead version by id, so a rename does not break the link.

  • Readiness by project

    All issues of the release across the projects, split into To Do, In Progress and Done, with a table by project and an Open in search link that opens every issue of the release in the issue navigator.

  • Release notes that stay put

    When a program version is released, the app saves a snapshot of its issues, so the release notes do not change later. Markdown, Word and PDF, grouped by issue type or by project, with a comparison of the snapshot and today.

How a change reaches the other projects

The lead project is the source of truth. The app never loses a change silently: each project shows whether its copy is in sync, waiting, or different, and why.

  • Usually seconds, up to a few minutes

    A change to a lead version reaches the member projects usually in seconds, up to a few minutes. The time depends on Jira's own queues and on the request limit of your site. When the limit is used up, the app waits and says so on the page instead of failing silently.

  • The lead wins

    If someone edits a copy by hand, the app brings it back to the lead version: the hourly check does it for unreleased versions, the daily full check for released and archived ones. The same checks catch a change whose Jira notification was lost. A version that exists only in a member project is never touched.

  • Differences you can see and retry

    A copy that cannot follow the lead shows the reason — for example Name taken in this project or Released or archived differs — and a Retry button.

How it works

A Jira administrator sets up a program once. Everyone else keeps working in Jira.

  1. Install.

    A Jira administrator installs ArtUp Release from the Atlassian Marketplace. Sites with up to 10 users use it free.

  2. Create a program.

    On the app's administration page, Manage programs, choose Create program: a name, the lead project and the member projects — 2 to 100 projects in all, the lead included. A project belongs to one program only.

  3. Preview the matching.

    Preview matching finds versions that already exist in member projects by exact name and shows, field by field, what would change. A released or archived difference is a conflict that changes nothing unless you check Bring to lead. Then Apply and create program; matching runs in the background.

  4. Release as usual.

    Work with versions in the lead project — in Jira, or from Apps → ArtUp Release, which shows the program's versions, readiness, sync state and release notes.

Version 1

What ArtUp Release does not do

  • Never writes to issuesIt writes only project versions, and its sync never deletes a version.
  • Deletes do not spreadDeleting or merging a lead version leaves its copies. The page lists them and lets you delete them, choosing for each project where its issues go.
  • Versions onlyNo components, project categories or order of versions.
  • Fixed lead projectTo change it, delete the program and create it again; matching by exact name makes that safe.
  • One built-in layoutWord and PDF release notes use one layout; no custom templates and no Confluence publishing in this version.
  • Jira Cloud onlyNot Data Center. A program too large for the app's share of Jira's request limit can be skipped by the background check.

Nothing leaves Atlassian

ArtUp Release is a Forge app that runs on Atlassian. There are no ArtUp Labs servers in the path.

  • No egressNo external servers and no outbound calls. Word and PDF files are built in your browser.
  • Writes only versionsScopes read:jira-work, manage:jira-project (project versions) and storage:app. No write:jira-work.
  • Your permissions on the pageEverything on the page is read as you. A project you cannot see shows “No access”, without numbers.
  • Complete snapshots, filtered viewsA snapshot is taken as the app; rows you cannot see are hidden and counted.
  • Little storedPrograms, version links, a short sync log and release snapshots (issue key, project, type, summary, status category). No comments, descriptions of issues, attachments or user data.
  • Versions stay yoursRemove a project, delete a program or uninstall the app: the versions stay as ordinary Jira versions.

Details: Privacy Policy and Security.

Questions

  • Does it change my issues?

    No. It writes only project versions. When you delete the copies of a deleted lead version yourself, Jira moves their issues to the version you choose, or removes the version from them.

  • Some projects already have these versions

    They are matched by exact name and linked, not duplicated. The preview shows what changes in each. Two versions with the same name in one project are not linked until you remove the extra one.

  • Can a team edit its copy?

    It can, but the lead wins: the hourly check brings an unreleased copy back, the daily full check a released or archived one. Versions that exist only in that project are never touched.

  • Who sees what?

    You see the programs whose lead project you can browse. Creating and releasing versions from the page needs the Administer projects permission in the lead project; programs are managed by Jira administrators.

Free for up to 10 users

Larger sites subscribe through the Atlassian Marketplace, billed by Atlassian with your other apps, per user: $100 per month for 200 users. Without an active licence the app makes no new syncs or snapshots; versions and links already made stay as they are, and the sync checks catch up when the licence is back.

Licensing details Documentation Support