Integration

Open to your tools.

Mirador keeps requirements in sync with Jira and Jama. Connect any other tool yourself – through the documented REST API or your own adapter.

At a glance.

  • 2 directions

    Sync with Jira and Jama.Inbound on a schedule or when notified; back with a click or through the REST API.

  • 15 minutes

    The shortest interval on the schedule.Or shortly after the tool reports a change.

  • 20,000 rows

    Per Excel workbook, out and back in.With a dry run that shows conflicts first.

  • 2 ways

    To build your own adapter: plugin or service.Write the service in any language, over HTTP and JSON.

In sync with Jira and Jama

Requirements, attachments and links sync in both directions, and with Jama the tree as well. Mapping profiles define which field goes where.

More in the documentation: Jira and Jama

On a schedule or when notified

Mirador fetches changes from Jira and Jama on a schedule – every 15 minutes up to once a day – or shortly after the tool reports them. It writes back when you say so: with a click or through the REST API.

Notifications arrive through a webhook that your operations team sets up.

More in the documentation: Jira and Jama

Your own adapters for further tools

An adapter runs as a plugin inside Mirador or as your own service in any language, over HTTP and JSON. A compatibility kit shows whether it honours the contract before it works with real data.

The adapter contract is not frozen yet and may change.

More in the documentation: REST API

REST API, ReqIF and Excel

Your scripts use the same REST API as the user interface, with tokens you can time-limit and revoke. Bring existing data in and pass it on via ReqIF, and work with Excel out and back in.

Links travel only when both ends are in the file; comments stay in Mirador.

More in the documentation: Import and export

Also in Mirador

  • ReqIF export profiles

    Save which attributes and attachments go into a ReqIF file as a profile per specification, and pick it when you export.

  • Tokens for scripts and services

    A token is valid for 1, 7 or 30 days or without expiry. Mirador shows when it was last used and stores it only as a hash.

See for yourself.

In a demo we show you Mirador on a sample project and answer your questions about integration, operations and data protection.