Reviews and quality
Keep your tools in step with Yavaren
Synchronise Yavaren Boards, Requirements and Knowledge with Jira, Azure Boards, GitHub Issues, GitLab or Confluence — each field owned by one side, a preview before any write, every conflict decided by a person.
Settings › Synchronisation (admins set it up; members see its health).
Set up
On Set up, choose:
- the project
- the connection (its tracker, or a knowledge source)
- what to synchronise: planning, requirements or knowledge
- a mode:
| Mode | What happens |
|---|---|
| Linked by reference | outside items are linked and shown; nothing is copied or written |
| Imported once | copied into Yavaren once |
| Follow the outside tool | its changes update Yavaren; nothing is written outside |
| Publish from Yavaren | Yavaren's changes are written outside |
| Controlled two-way | each field is owned by one side or shared |
A new synchronisation is a draft: nothing has been read or written yet.
Preview, then allow writes
Preview reads your tool and shows every item that would be created or changed, and every conflict, without changing anything. Only after the preview of the current version can an admin choose Allow the previewed writes. Changing the mapping makes a new version, which needs a new preview and a new approval.
Conflicts
When both sides changed the same field, or a change touched a field the other side owns, Yavaren does not pick a winner. The conflict waits under the synchronisation, and an admin chooses one of these:
- keep Yavaren's value
- keep the outside value
- defer
- unlink
An approved requirement is never changed in place. Taking an outside change makes a new version that must be approved again.
Deleted items are never deleted on the other side: they are shown for a decision. Archive the item in its own tool, then choose unlink.
What each tool supports
The What each tool supports tab lists, for each tool:
- what Yavaren reads and writes
- whether it protects concurrent edits
- how far it has been proven
No tool has been verified against a live instance yet. A repository host alone (Bitbucket, Azure Repos) is not a planning or knowledge tool.