Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

Relevant topics for this page:

  • Agile Hive comes with predefined issue type schemes for projects on all SAFe® layers

  • Agile Hive issue type schemes contain:

    • Agile Hive - Portfolio - Issue Type Scheme

      • Issue Type Scheme for Portfolio projects in Agile Hive

      • Default Issue Type: Portfolio Epic

      • Contains: Portfolio Epic, Strategic Theme, Enabler

    • Agile Hive - Large Solution - Issue Type Scheme

      • Issue Type Scheme for Large Solution projects in Agile Hive

      • Default Issue Type: Capability

      • Contains: Capability, Objective, Risk, Enabler, Milestone

    • Agile Hive - ART - Issue Type Scheme

      • Issue Type Scheme for Agile Release Train projects in Agile Hive

      • Default Issue Type: Feature

      • Contains: Feature, Objective, Risk, Enabler, Milestone

    • Agile Hive - Team - Issue Type Scheme

      • Issue Type Scheme for Team projects in Agile Hive

      • Default Issue Type: Story

      • Contains: Story, Bug, Objective, Risk, Enabler, (Sub-Task)

  • There’s no obligation to use the Agile Hive issue type schemes - you can use none, all, or a subset of them. You can also add / remove issue types from any of the schemes as needed.

  • Agile Hive issue type schemes can be recreated by a Jira administrator at any time if deleted.

  • Agile Hive issue type schemes require Agile Hive Issue Types in order to be fully available.

    • If not all Issue Types are available when creating an Issue Type Scheme, the scheme will be created with only the issue types available.

  • No labels