Managing connected Backlog spaces

Each Chronigami workspace links to one or more Backlog spaces. One space can connect to only one workspace. Admins connect spaces; see Connecting your Backlog space.

#Add another space

When your plan allows more than one connection (spaceLimit on Billing is unset today, meaning unlimited):

1. Open Workspace settings → General.
2. Under Connected spaces, select Connect a Backlog space.
3. Complete Space id, Domain, and Continue, then approve access in Backlog.

The new URL appears in the list. Time entries, projects, and portal forms can target issues in that space when users and the ticket bot are set up for it.

#Disconnect a space

There is no Disconnect button in the Chronigami web app today.

To disconnect a space, contact support@chronigami.com. Include the space URL and workspace name. Only a workspace admin should request a disconnect.

#What disconnecting does

When support disconnects a space (or when an in-app control does the same in the future):

• Chronigami detaches every Backlog identity for that space host and deletes stored OAuth tokens for those identities.
• Users who had only that Backlog identity (no Chronigami email and no other Backlog space) are signed out everywhere and cannot call the API until they sign in again another way.
• Users who still have email sign-in, or Backlog on another connected space, keep their sessions.
• Time entries already stored for that space’s issues stay in Chronigami. Disconnect does not delete time data.
• Disconnect does not deactivate users who still have another identity.
• On the Portal product, if the ticket bot used that space, the bot configuration is removed. Forms remain, but readiness and submits that depended on that space fail until you connect a space and set the bot again. See Setting up the ticket bot.

Chronigami does not delete or change issues, hours, or attachments in Backlog when you disconnect.

#Actual Hours and linked entries

With Update Actual Hours in Backlog on, sync uses each person’s token for the space. After disconnect, new sync for that host stops. Existing Chronigami entries still reference stored issue rows; issue verification may show Not found in Backlog if the space is gone from your workspace while issues remain in the database.

See Actual Hours sync.

#Related articles

• Connecting your Backlog space
• Workspace settings and branding