Settings and Configuration

How Hakkiri Works

A Board in Jira becomes a Team in Hakkiri.

Hakkiri is built on the principle that tracking work using time-series enables us to create unique and powerful metrics and predictive analytics.

Because organizations use boards for many purposes when setting up Hakkiri we advise customers to select the authoritative board for each team. This typically means:

• For Scrum Teams: Use the board they start and stop their sprints on
• For Kanban Teams: Use the primary Kanban board

For boards that are integrated Hakkiri will track:

• The Board
• Sprints
• Epics
• Issues
  • Tasks: Are converted to Stories in Hakkiri
  • Sub-tasks: Hakkiri ignores sub-tasks

Hakkiri listens to webhooks and tracks all activity in real-time. We also do a daily sync once a day of all updates just in case a webhook update lost it's way over the internet.

Configuration

• Pull Boards: Click the "Pull Boards" button to initialize the boards in your Jira with Hakkiri. This will enable you to select the boards you want to integrate with Hakkiri.
• Choose a Board and Add as Team: Use the selection control to find the board by name you want to integrate. Once selected click "Add as Team" and the board will populate into the table below to indicate it is been selected successfully.
• Currently Being Synced table: Review the boards you have integrated with Hakkiri. If you no longer want to integrate a board with Hakkiri simply click the delete button. Please know that all of it's data will be deleted and can not be recovered. You can re-add the board at any time and the time series collection will start from the new integration date.

Integration

Hakkiri's integration is setup under the context of the user who installs the integration. This user can be changed at any point but be aware that you need to utilize a user who has permissions to the boards you want to (or already are) integrate with Hakkiri.

Teams

Each board integrated with Hakkiri becomes a team in Hakkiri. Here you can customize the name to be different than the board and specify a color per team to distinguish them visually.

Deliverable Types

Deliverable Types let you create the release vehicles your organization uses. Common use cases are:

• Release (the default)
• Increment (for organizations using SAFe)
• Patch
• Quarterly Goal
• OKR

Team Groups

Use Team Groups to associate Team's together. You can create different types of Team Groups with different instances of each type. A common use case is to create a "Program" type and instances per program to different teams by the product they support.

Roadmap Hierarchy

Use the Roadmap Hierarchy to customize the names to how your organization describes it's roadmap. Using Roadmap Items and Team Items (Epics) is required when building a roadmap but Initiatives are optional.

Tag Groups

Use Tag Group Types and Tags to attribute Roadmap Items and Deliverables thematically. They help your organization see the thematic breakdown of work in your roadmap. You can create as many Tag Group Types as you want. You can associate 1 value per Type to any Roadmap Item.

Common use case are:

• Type of "Strategic Theme" with tags of "Tech Debt", "Required Maintenance", "Client Driven", "Innovation", "Strategic Initiative"
• Type of "Work Stream" with tags of "BAU", "Strategic Initiative", "Internal", "External", "Support Related"