Back To Overview


Project Administration

Project settings


Introduction

Project Administrators can change several settings for their respective projects. However, only Jira or system administrators are authorized to trigger a PI-specific recalculation of Report properties.


ART level project


Team level project

Team level


Primary Board

A Team in Agile Hive needs a dedicated Primary Board to function properly. A Primary Board needs to be a Scrum Board. Agile Hive needs a Scrum Board to create and track the Sprints during your PIs. Without a Scrum Board the Breakout and Program Board will not work properly. Kanban Teams need to have a Scrum board additionally to their Kanban board, too.

If you don't have one, create a new Scrum Board in Jira’s Board Overview (Boards → View all Boards → Create Board) and choose “Create a Scrum Board”. Resolve this error by setting the Primary Board in the Project Settings → Agile Hive menu entry. Choose a Scrum Board from the boards associated with this project and save your setting.


If you changed your Primary Board, be sure  to recreate the Sprints for existing PIs in this board. 


Sprints

Agile Hive needs to know which Sprints in your Board are related to your ART’s Planning Intervals to determine where issues should be moved if you drag and drop or create them in the Breakout Board or in order to show the Team Reports. Normally, this connection is made when a PI is created and Sprints for all teams are automatically created in the teams' Primary Boards. The following cases might make it necessary to recreate this connection.


If your team has been added to another ART with existing PIs
If that is the case, you will have to (initially) create the Sprints so they are correctly connected to the PI iterations. 

If you switched your Primary Board
When switching boards, Agile Hive still holds references to your old board’s sprints. With “Recreate missing sprints“ those old references will be removed and new sprints will be created in your new Primary Board and connected to Agile Hive.

Sprints from other Boards can still appear in your backlog as long as issues that match your board’s filters are in those Sprints. To avoid having duplicate Sprints, rename the old ones before recreating the Sprints in the new Primary Board, then move your issues from the old ones to the new and delete the old Sprints.

If you deleted sprints
If you have deleted a future sprint from your board, you can simply recreate it and it will be connected to Agile Hive again by clicking “Recreate missing sprints”.


ART and higher levels


Primary Board

Like Teams, other projects can also choose a Primary Board. But unlike Teams, this is not a mandatory configuration. No sprints have to be connected to this board. This board will be used to get Quick Filters for the Backlogs in the Roadmap views and it will be used as the target of the Kanban Board link from the Agile Hive view switcher.


Recalculate Properties

Instead of triggering a system-wide recalculation of all Agile Hive properties, Jira or system administrators are the only ones authorized to recalculate Report, Planning Board, or Burn Up Chart data for a specific PI in ART (or higher level) projects. This recalculation will only consider issues that have the selected PI in the Planning Interval custom field. This approach uses fewer resources and should yield results more quickly than a full recalculation.

As with the system-wide recalculation, a lozenge will display the state of the process, showing either "Running" or "Not running".

Be aware, that only one recalculation can be processed simultaneously. So, if either a system-wide or another project specific calculation is already running, you cannot start one here.







  • No labels
This page was last edited on 09/04/2024.