Landscape

Landscape is the first screen of the Integration Hub for an organisation administrator. It draws your whole estate in three bands:

• Repositories: traceunified itself, and each tool you have connected.
• Collections: the groups of artifacts written against those tools.
• Integrations: what runs each collection.

Four figures above the drawing count the repositories, collections and integrations, and say how many integrations are in error.

Isolate a chain

Every list in the Hub is complete on its own, and none of them says what is wired to what. Landscape does. Click any node and its chain is isolated: everything connected to it stays lit, and everything else dims.

That is impact analysis in one click. Before you rotate a Jira credential, click its connection and you see exactly which collections and integrations will stop, and which will not. A repository you reach while following a chain is where the effect stops, because its own credential is not the one being changed.

From an isolated node you can open it: the Hub goes to that connection, collection or integration with its record already open, so you never have to find it again by name.

When it is empty

On a new organisation there is nothing to draw, so Landscape shows the setup chain instead: add a connection, then a collection, then an integration.

Who can open it

Landscape reads organisation-wide integration configuration, so it is available to organisation administrators.