Agile Hive Project Settings
- Daniel Roller
Introduction
For every Jira project added to Agile Hive, the app offers a set of project settings. Agile Hive Administrators can make use of those settings in order to configure the project in Agile Hive for its intended use.
Project Settings in Agile Hive can be accessed by Jira users with Agile Hive Administrator permission by navigating to the respective project and clicking ‘Settings’ in the project navigation bar.
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.
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.
Issue Type settings are available for every project added to Agile Hive on any SAFe® layer:
Agile Hive Feature | Available SAFe® layers | Description |
|---|---|---|
Milestone | portfolio solution train ART Team | Issues of the type mapped to the ‘Milestone’ functionality will be visualized in Roadmap Boards (requires Custom Field ‘Milestone Date’) as well as displayed in the ‘Milestone Overview’ widget of the Reports. |
Risk | solution train ART Team | Issues of the type mapped to the ‘Risk’ functionality will be displayed in the ‘Risks’ widget of the Reports. |
Objective | solution train ART Team | Issues of the type mapped to the ‘Objective’ functionality will be displayed in the ‘PI Objectives’ widget of the Reports. |
Improvement | solution train ART Team | This mapping is not yet in use to provide dedicated functionality in Agile Hive but will be added in the future. Stay tuned! |
Strategic Theme | portfolio | This mapping is not yet in use to provide dedicated functionality in Agile Hive but will be added in the future. Stay tuned! |
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.
Make sure that the Jira Screens assigned to an issue type that is mapped with one of Agile Hive’s features are configured correctly and that all required custom fields are included. Also check that the correct Issue Type Screen Scheme is assigned to the project.
Ask your Jira Administrator for support if you do not know whether all the requirements for your project have been met.
Link to this page: https://seibert.biz/ahc-projectsettings