Project releases

Manage planned releases, current issue targets and publication history without confusing delivery with deployment.

Application revision 8c09715b · Docs d2d4fba5

    Create and assign

    Create a release in a project’s release area. Give it a name unique within that project and optionally add notes and a date. Names must be 1–128 characters without control characters; dates must fall in years 1000–9999. The form explains invalid entries. Releases are planned, released or cancelled; their names do not have to follow semantic versioning.

    You can open a project’s releases from the command palette and create a release from within that project. The list and details show a status badge and a localized target date.

    If you can manage a release, you can search issues in its project, add several at once, or remove an issue from a planned release’s detail. Issues assigned to another planned release are not offered. You can still assign or clear a target from issue creation, issue details, embedded Inbox details or bulk actions. An issue has at most one current target and can only be newly assigned to a planned release in the same project. Release display in lists and boards is off by default and can be enabled in display settings.

    Confirm publication

    The project creator, lead or a workspace administrator can edit, publish or cancel a planned release, provided they can access every associated team. Workspace administrators do not bypass private-team membership. Other members can create releases and manage associations for issues they can edit, but cannot edit or publish a release on that basis alone.

    1. Open a planned release and inspect its scope and unfinished work.
    2. Read the preview and confirm explicitly. Unfinished issues are highlighted but do not prevent an explicit confirmation.
    3. If the release or issue set changed, reload the preview and confirm again rather than reusing an outdated confirmation.

    Publishing does not change issue statuses, run a build, deploy code or prove a production deployment succeeded.

    History and cancellation

    Publication freezes issue IDs, visible identifiers, titles, status categories and source teams. It does not copy descriptions, comments or attachments. Reassigning an issue later does not rewrite an earlier publication snapshot.

    History checks current project, issue and original-team access. Deleted or unreadable issues do not expose historical titles or contribute to the visible counts. Different members may therefore see different counts.

    Cancellation clears current associations without deleting issues or changing their status. Released and cancelled versions are read-only. Unpublishing, reopening and independent release deletion are not supported.

    Association changes

    Clearing or changing a project, soft-deleting an issue or invalidating team relationships clears an invalid current target. Restoring an issue does not recreate cleared associations, and copies do not inherit releases. Re-read current issue state before explicitly scheduling it again.