Introduction

Agile Hive provides a set of predefined Jira Issue Types, Custom Fields, Screens, as well as various Schemes in order to get you started with the app as quickly and conveniently as possible.

While most of the built-in entities are optional to use, some of them are required for specific functionality of the app to work properly.

Prerequisites

Make sure you’re logged in with a Jira user holding at least Jira Administrator permission.

First Steps for Jira Administrators

In the sections below you can find information on the initial setup of Agile Hive.

The Configuration Checklist

To support you with the initial setup of Agile Hive we have prepared a checklist that guides you through the first steps with the app.

Open

You can easily access it by navigating to the ‘Apps’ section of global Jira Administration:

Open

Select ‘Agile Hive Administration’ from the left hand sidebar - you’ve successfully reached your destination!

Step-by-Step Guide for Initial Setup

The configuration checklist for Jira Administrators contains a bunch of tasks. While most of them are optional, there still are some of them that at least require your attention once. The list below will help you quickly identify the setup steps you should take a closer look at.

Also, it is recommended to work through the list from top to bottom, as some of the setup steps are based on previous steps.

1. Add Administrators for Agile Hive recommended

We recommend double-checking the Atlassian user groups configured for the Agile Hive Administrator permission.

You can find more information over at https://agilehive.atlassian.net/wiki/spaces/CLOUD/pages/510853259.

2. Add Agile Hive specific Issue Link Types Optional

It’s fully optional to create and use the built-in Agile Hive Issue Link Types for Dependencies, Objectives, and Risks.

You can also decide to use existing Issue Link Types and map them to the corresponding functionality in Agile Hive. More information is available at https://agilehive.atlassian.net/wiki/spaces/CLOUD/pages/512197033.

3. Issue Types specific to Agile Hive Optional

You can decide whether or not to use the built-in Agile Hive Issue Types for projects on all SAFe® layers. Agile Hive Issue Types are required to create Agile Hive Issue Type Schemes and Agile Hive Issue Type Screen Schemes.

You can find more information over at https://agilehive.atlassian.net/wiki/spaces/CLOUD/pages/518422529.

4. Issue Type Schemes specific to Agile Hive Optional

You can decide whether or not to use the built-in Agile Hive Issue Type Schemes for projects on all SAFe® layers.

You can find more information over at .

5. Statuses specific to Agile Hive Optional

You can decide whether or not to use the built-in Agile Hive Statuses for projects on all SAFe® layers. Agile Hive Statuses are required to create Agile Hive Workflows and Agile Hive Workflow Schemes.

You can find more information over at .

6. Add Agile Hive specific Custom Fields Required

Agile Hive provides a lot of SAFe® specific functionality that will enable your organization to use Jira in a scaled agile environment. In order for the users of this Jira instance to be able to use these features to their full extent, Agile Hive requires certain information as a data basis.

This information is collected and stored via a set of Custom Fields, which are essential for the provision of the associated functionality.

You can find more information over at .

7. Workflows specific to Agile Hive Optional

8. Add Agile Hive specific Workflow Schemes Optional

9. Screens Configuration specific to Agile Hive Optional

10. Add Agile Hive specific Screen Schemes Optional

11. Add Agile Hive specific Issue Type Screen Schemes Optional

12. Proceed to Agile Hive Configuration Required

The initial setup of entities required to use Agile Hive with your Jira site is now completed. To adapt Agile Hive to the needs of your organization, the app is configured accordingly in the next step.

You can find a step-by-step tutorial over at .