Jira

In LaunchCal, a launch can follow the Jira epic, or any issue, that tracks its work. Its status moves when the issue's does, it shows how many of an epic's child issues are done, and the issue's comments appear on the launch.

A whole Jira project has no status of its own, so a link to one is kept as a plain link: link one of its epics or issues to follow it.

Taktoria only reads from Jira (issues with their status, child issues and comments, and the names of the people who wrote them): it never creates, changes or comments on anything there.

Only a workspace owner or admin can connect Jira.

1. Open Settings → Integrations.
2. Under Ticketing systems, select Connect Jira.
3. Sign in to Atlassian, choose the Jira sites to connect, and approve it.

Taktoria reads Jira as the Atlassian account that connects it. Any issue that account can see can be linked to a launch, and its comments shown there, by anybody who can edit the launch, even somebody who cannot open the issue in Jira. So connect Jira with an account kept for Taktoria that can see only the projects your launches follow, rather than your own. A connection made with a person's account also stops syncing when they leave or lose access.

Anybody who can edit a launch can link it, sync it or unlink it.

1. Open the launch's Details tab.
2. Under Ticketing project, paste the address of the epic or issue into Project link: its own page, or a board or list with it open.
3. Select Link project.

The issue has to be on a connected Jira site, and one the connecting account can see. It syncs straight away. A link pasted before Jira is connected is kept as a plain link, and starts syncing once it is.

An AI assistant connected to LaunchCal, and the REST API, can link, sync and unlink a launch too, under the same rules.

A linked launch is synced once a day until it launches, and whenever somebody selects Sync now.

• Status: when the issue's status changes, the launch's follows: to do is Scoping, in progress is In development (a launch already in Design or Testing stays there), and an issue done as won't do or duplicate is On hold. A status you choose in LaunchCal stands until the issue's changes again.
• Progress: the share of the epic's child issues that are done.
• Comments: each of the issue's comments becomes a comment on the launch's Activity tab, marked From Jira with a link to it. A comment restricted to some people in Jira is never brought in. Edit one in Jira and the next sync brings the change.
• Completed: when the issue is done, the launch says it is ready and its owners are told.

What a sync changes is shown as Jira's, in the launch's history, in what its owners are sent and in the audit log. The audit log records that a comment came in or changed, never what it says or whom it names.

• It never launches anything. A done issue makes the launch ready; somebody still selects Press to launch! once its required reviews are decided.
• It never changes a launch that has launched.
• It never writes to Jira.
• It never brings in a comment restricted to some people.
• It never undoes a status you chose in LaunchCal, unless the issue's status changes again.

Unlink, on the launch's Details tab, stops that launch syncing; what was brought in stays.

Disconnect, in Settings → Integrations, stops every launch syncing from Jira. Launches keep what they link and everything synced so far, and pick up again once Jira is connected again. Disconnecting Jira also removes the names of Jira users from the comments it brought in, as Atlassian requires: a comment keeps its words but not its author's name, and a mention reads @someone. The same happens to one person's names when Atlassian says their account has closed.

Atlassian gives Taktoria no way to withdraw its own access to Jira: to remove it completely, also remove Taktoria from the connected apps in your Atlassian account.

• The issue could not be found: it was deleted, moved, or is somewhere the connecting account cannot see. Give that account access to its project, or link its current address.
• Jira turned the connection down: a workspace owner or admin connects Jira again in Settings → Integrations. This happens when the account that connected it leaves or loses access.
• Jira did not answer the last sync: the next sync tries again, or select Sync now later.
• A whole project is not synced: it has no status of its own. Link one of its epics or issues instead.
• A comment is missing: comments restricted to some people in Jira are never brought in.