Skip to main content

Verified program status for GitLab

Tarivra reads the issues and tasks your teams already track in GitLab, on any plan, checks each program's reported status against them and adds GitLab programs to one verified portfolio view.

Connecting GitLab

Your GitLab admin creates a project access token on each project in scope, not a personal token across every project.

  • read_api to read; the api scope only if decisions should be written back
  • Reporter role, or Developer if the project restricts who creates issues
  • Scoped by the token to that one project

What becomes a program

A team adds the tarivra-program label to an issue. Its child items, two levels deep, are the program's work. Epics need a paid plan, so a labeled issue plays that part on every plan.

  • Closed is done; an open item is in progress from its GitLab status or a workflow::in progress style label
  • Due date, else the milestone's, is the target; the first assignee is the owner
  • A rag-green, rag-amber or rag-red label gives the declared status

What Tarivra reads

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

  • Issue and task titles, states and status labels, and when each was opened, updated and closed
  • Assignees, due dates, start dates and milestones
  • A blocked label; cancelled items are left out
  • Links in other tools that point to a GitLab issue, for dependencies across tools

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

An approved decision becomes a task under the program issue, with its due date, labeled tarivra-decision and assigned to the action owner when exactly one project member matches. The decision closes in Tarivra when the task is closed.

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 need a paid GitLab plan?

No. A labeled issue with child tasks works on the Free plan. On paid plans Tarivra also reads GitLab's own work item status.

Can Tarivra read our code?

No. It reads issues and tasks only, through a token limited to the projects you choose.

Why a project access token?

It can only reach the one project it was made in, and it is not tied to a person who might leave. A personal token with the api scope would reach every project that person can.