Introduction

For every Jira project added to Agile Hive, the app offers a set of project settings in order to configure the project for its intended use. The settings in Agile Hive can be accessed by navigating to the respective project and clicking ‘Project Settings’ in the project navigation bar.

Open

Prerequisites

Users need to hold at least one of the following Permissions in order to access ‘Project Settings’ in Agile Hive for a given project:

• Manage Agile Hive Project Members (can only access ‘Members’ subsection)

• Administer Agile Hive Projects

• Administer Projects

• Agile Hive Administrator

• Jira / Site Administrator

Project Configuration

In a project’s settings view, Agile Hive Administrators can edit various configurations of a project in Agile Hive.

Members

In the ‘Members’ section of project settings, you can define people working in this project as well as their respective roles. People added to a project here will be displayed in the header section of Agile Hive Reports for this Jira project.

Open

To add new members simply click the ‘Add Members’ button in the top right corner of the screen. In the modal window you can select one or more Jira users that should be added as project member.

After adding one or more members, you can set their respective role in the project, change the order via Drag&Drop, and remove members by clicking 'x'.

Please note:

• There’s a limit of 25 members that can be added to a project.

• Every project member’s role is limited to 100 characters.

• Configuring project members in Agile Hive does not change any Jira project settings or permissions.

• Agile Hive project member configuration is not (yet) integrated with Atlassian’s team feature.

Issue Types

In the ‘Issue Types’ section of project settings, you can configure Jira issue types that Agile Hive uses to provide specific app functionality.

Open

Issue Type settings are available for every project added to Agile Hive on any SAFe® layer:

Agile Hive will try to populate the issue type mappings automatically by detecting if the built-in issue types are in use. If no matching issue type is found for a project the corresponding field will be empty initially. Issue type mappings explicitly set by an Agile Hive Administrator won’t be overwritten by the automatic detection mechanism.

Primary Board

In the ‘Primary Board’ section of project settings, you can configure the Jira board that Agile Hive uses to offer quick filters in its own board views (e.g., Roadmap Boards, Team Planning Boards) as well as create new Sprints in (status:Team-level projects only).

Open

Sprints

In the ‘Sprints’ section of Team-level project settings, you can view and edit the mapping of Jira Sprints with iterations of current and planned PIs for the respective Team. In order to access this section of a projects' settings, users need to hold ‘Manage Sprints’ permission in addition to the ones listed in Agile Hive Project Settings | Prerequisites.

Open

In this settings view, users can edit the mapping of existing PI iterations with Jira Sprints, or even create new Sprints for any of the iterations not yet running.