Docs · Using Iskue
Working together: live updates and conflict review
Several people often have the same ticket or page open. Iskue keeps what each of them sees up to date, and it does not let one person's save silently overwrite another's. This page covers what you see when that happens, and the two switches an administrator can use.
Live updates
You do not need to refresh. Open tickets, boards and pages follow the changes other people make.
- Tickets and boards. Boards redraw when a ticket changes. An open ticket shows the change with a brief tint on its header, and a screen reader announces it.
- Pages. An open page in a docs space or project wiki refreshes within a second or two when someone publishes it. The header flashes and a screen reader announces the update. The page tree follows pages created, moved, archived or deleted elsewhere, and the comments panel follows new and edited comments. If the page was deleted, or you can no longer see it, the page says so.
- Bursts of changes. An automation chain or a bulk edit refreshes an open ticket once, not once per change.
- Lost connections. The browser reconnects by itself and re-reads what it missed. An open ticket also checks in every 15 seconds, so it catches up even when the live stream is blocked. If updates stop until you refresh, a proxy in front of Iskue is the usual cause: see Troubleshooting.
Seeing who else is there
An open ticket shows who else is viewing it and what they are working on: editing the title, editing the description or writing a comment. Someone counts as present for 30 seconds after their browser last checked in.
Conflict review on saves
When you start editing a page, or a ticket's title or description, Iskue remembers the version you started from. If someone else publishes a change to it while you type, a banner tells you who, for example "Alex Morgan changed the description while you were editing". Your draft stays as it is, and the banner offers three ways forward.
| Choice | What it does |
|---|---|
| Review | Merges their change into your draft, block by block. Whatever does not overlap merges on its own. For each block you both changed, you see the two versions side by side and pick one; yours is selected to begin with. If you both changed the title, you pick a title too. Nothing is saved until you save. |
| Take theirs | Replaces your draft with their version. |
| Keep mine | Asks you to confirm, then keeps your draft. Your next save replaces their change, and their version stays in the history. |
If your save reaches the server before the banner reaches you, the save is refused and nothing is written. On a page the same review opens straight away. On a ticket the same banner appears.
On a ticket the check is per field, so two people who edit different fields both get through. Only the title and description are reviewed in the app. For other fields, such as priority or assignee, the latest change wins.
The banner does not appear on imported HTML artifacts.
Transitions and comments
- Transitions. If a ticket's status moves while a transition dialog is open, the dialog checks again. It tells you whether the transition is still possible or no longer available.
- Editing a ticket comment. If the comment changed in the meantime, the save is refused. The current text is shown and yours stays in the editor.
- Editing a page comment. If the comment changed in the meantime, the save is refused with an error message and the comment keeps its current text.
- A comment deleted under you. The editor closes and your text moves to the comment box.
Not there yet
Two people cannot type in one page together and watch each other's changes appear. Each person works on their own draft, and the review brings the drafts together when they collide. Pages do not show who else is viewing them yet; only tickets do.
Instance switches
Both switches are under Administration → Instance settings, apply to the whole instance and are on by default.
| Switch | When it is off |
|---|---|
| Pages update live | Open pages, their tree and their comments no longer follow other people's changes. Tickets and boards keep their live updates. |
| Conflict review on saves | No banners, and saves overwrite. A version named by an API client is ignored too. |
For scripts and API clients
The same check is open to anything that uses the API. Naming a version is optional, so existing scripts keep working. The request, the 409 STALE answer and its fields are in Conflict-safe saves.
The live updates are Server-Sent Events: GET /api/v1/projects/{projectKey}/live for a project's tickets, boards and wiki pages, and GET /api/v1/docs/spaces/{key}/live for a docs space. Events name what changed, and you read the content through the normal endpoints.
Feature overview: Tickets with real structure · Confluence-style pages with live ticket blocks