Verified program status for Jira
Your teams keep working in Jira. Tarivra reads the epics and issues they already track, checks the status each program reports against that work, and gives leaders one verified portfolio view with the evidence cited.
Connecting Jira
Your Jira admin creates a dedicated Jira Cloud user for Tarivra with its own API token, limited to the projects in scope.
- Browse projects to read the work
- Create, edit and transition issues only if you want leadership decisions written back as Jira work items
- No Jira admin rights, no other projects, and never a person's own token
What becomes a program
A team adds the tarivra-program label to the issue its work rolls up to. That issue is the program's source of truth for its name, owner and target date.
- Usually an Epic, but an Initiative, a Feature or any other issue type works too
- Its work is the issues whose Parent is that item
- A rag-green, rag-amber or rag-red label gives the status the team declares
- Removing the label stops new reads; the program's history stays
What Tarivra reads
Tarivra never reads source code, attachments or anything outside the projects, repositories and tables you grant.
- Status and the full status history, grouped by Jira's own To do, In progress and Done categories
- Assignees, due dates and story points
- The Flagged field, blocked statuses and a blocked label
- Issue links, and web links to work in other tools marked blocked by or blocks
- When each issue was created, so work added after the start shows as scope growth
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.
- ScheduleIs the work finishing fast enough to make the target date?
- Scope growthHow much work was added after the start?
- ThroughputIs the team finishing work at a steady pace?
- Overdue workHow much is past its due date?
- Blocked workHow much is flagged or marked blocked?
- Stale workIs in-progress work sitting untouched?
Connect ServiceNow as well to add change health: whether recent changes failed or caused incidents.
Decisions that stick
When leaders approve a decision or ask a question, Tarivra creates a Jira work item in the program's project, assigned to the action owner when exactly one person matches. The decision closes in Tarivra when that item is done in Jira.
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
Does Tarivra work with Jira Data Center or Server?
Tarivra connects to Jira Cloud today. If you run Jira Data Center, tell us when you request a demo.
Do my teams need new fields or workflows?
No. A label on the item the work rolls up to is all Tarivra needs. Custom statuses are mapped by Jira's own status categories, and your admin can adjust the mapping.
Can Tarivra change our Jira issues?
It reads only. The one thing it creates, if you allow it, is a work item for each decision your leaders approve, so follow-through is tracked where the team works.