Skip to main content

One verified portfolio across Jira and Azure DevOps

Many organizations run some teams in Jira and others in Azure DevOps, and leadership gets two kinds of status that never quite line up. Tarivra reads both, scores every program the same way and puts them in one portfolio view and one weekly brief.

Connecting Jira and Azure DevOps

Connect each tool with its own least-privilege account: a dedicated Jira Cloud user and an Azure DevOps personal access token, each limited to the projects in scope.

  • Teams keep their tool, their process and their statuses
  • Each tool's statuses map to the same To do, In progress and Done, so scores compare fairly
  • Add ServiceNow, GitHub or GitLab later in the same way

What becomes a program

Each program is anchored to one labeled item in the tool where its team works: a Jira issue with the tarivra-program label or an Azure DevOps work item with the tarivra-program tag.

  • The same seven checks and the same score for every program, whichever tool it lives in
  • One brief, one dependency map and one decision log for the whole portfolio
  • Decisions are written back to the program's own tool

What Tarivra reads

Tarivra never reads source code, attachments or anything outside the projects, repositories and tables you grant.

  • Everything Tarivra reads from Jira and from Azure DevOps on their own pages
  • Dependencies across the two tools: a web link in Jira, or a hyperlink in Azure DevOps, to the other item, with link text starting blocked by or blocks
  • Who owns the work on each side, so a slipping dependency is traced to the program it holds up

How the status is checked

Tarivra compares the status the team reports with what the work shows, runs these checks and scores how well the two agree.

  • Schedule
    Is the work finishing fast enough to make the target date?
  • Scope growth
    How much work was added after the start?
  • Throughput
    Is the team finishing work at a steady pace?
  • Overdue work
    How much is past its due date?
  • Blocked work
    How much is flagged or marked blocked?
  • Stale work
    Is in-progress work sitting untouched?

Connect ServiceNow as well to add change health: whether recent changes failed or caused incidents.

Decisions that stick

A decision about a Jira program becomes a Jira work item; one about an Azure DevOps program becomes an Azure DevOps Task. Each closes in Tarivra when the work is done in its own tool.

This is the only thing Tarivra writes, and only if you allow it. Every decision is also kept in an audit log nobody can edit.

Questions

Do we have to move teams onto one tool first?

No. That is the point: each team stays where it works, and leaders get one consistent view.

How are dependencies between the tools tracked?

Jira and Azure DevOps cannot link to each other's items, so a team adds a web link to the other item with link text starting blocked by or blocks. Tarivra reads the address and the direction and shows the dependency on the map.

Are the scores comparable?

Yes. Both tools' statuses map to the same three categories and every program runs the same checks, so a 70 in Jira means the same as a 70 in Azure DevOps.