Page tree
Skip to end of metadata
Go to start of metadata





8 - Team Level

8.1 - Creating issues at the Team level

So that the Program level views can display content, issues must be created first. Use the Create button in the top navigation bar to go to the Create Issue screen. Select the Program project. If you have more than one Agile Release Trains (ARTs), select the specific "ART" project you want to work with.

The default issue types are as follows:

  1. Story
  2. Enabler (Team)
  3. Bug
  4. Impediment (Team)
  5. Risk
  6. Objective (Team)


8.1.1 - Story, Enabler (Team), Bug, Impediment (Team) issue types

The dialog has been made as simple as possible, so that you can create issues quickly:

  • Summary (enter a short description of the issue)
  • Description (detailed description)
  • Linked Issues (link issues directly)

Additional fields can be configured by an administrator to meet your requirements.

Available link types include:

  1. relates to
    1. is always available.
    2. has no influence on the SAFe hierarchy.
    3. can link to any issue.
  1. TEAM TO ART LINK
    1. is only available at the Team level
    2. affects the SAFe hierarchy
    3. can only be linked to issues at the Program level

Links that affect the hierarchy are always displayed in uppercase letters.

Enter or search for the issues you want to link to. You can add links to several issues at the same time.

Note: Only valid issues can be linked to in the hierarchy, for example the issue "Epic (Portfolio)" cannot be linked with a story at the Team level. This is indicated with a red error message.

Common error: Trying to link several processes that are on different levels. This is not possible. You need to add links level by level!


8.1.2 - Risk issue type

The following fields are available by default when you create an issue of this type:

  • Summary (short description of the issue)
  • Description (detailed description)
  • Impact (consequences should the risk come to pass)
  • Probability (probability that the risk will occur)
  • Residual Impact (Impact of the risk after all measures have been taken)
  • Residual Probability (probability of occurrence of the risk after all measures have been taken)
  • Linked Issues (link issues directly)
  • Fix Version/s

Additional fields can be configured by an administrator to meet your requirements.


8.1.3 - Objective (Team) issue type



8.2 - Editing issues at the Team level


8.2.1 - Story, Enabler (Team), Bug, Impediment (Team) issue types

Once you have created the issue, click the Edit button to add more information to the respective fields. An administrator can configure additional or different fields to meet your requirements.

  • Summary (short description of the issue)
  • Definition of ready (checklist for specific criteria)
  • Story Points
  • Description (detailed description)
  • Sprint
  • Assignee
  • Reporter
  • Component/s
  • Labels
  • Affects Version/s
  • Fix Versions/s
  • Linked Issues (link issues directly)



8.2.2 - Risk issue type

The following fields are available:

  • Summary (short description of the issue)
  • Description (detailed description)
  • Impact (consequences should the risk come to pass)
  • Probability (probability that the risk will occur)
  • Residual Impact (Impact of the risk after all measures have been taken)
  • Residual Probability (probability of occurrence of the risk after all measures have been taken)
  • Linked Issues (link issues directly)
  • Fix Version/s

8.2.3 - Objective (Team) issue type

The following fields are available:

  • Summary (short description of the issue)
  • SMART PI Objectives (checklist to make sure the SMART criteria are met)
  • Description (detailed description)
  • Objective Business Value (A product manager enters a number between 1 and 10 in PI Planning.)
  • Stretch Objective (Determines whether the issue is a stretch objective. Yes / None)
  • Linked Issues (link issues directly)
  • Fix Version/s



8.3 - Viewing issues at the Team level


8.3.1 - Story, Enabler (Team), Bug, Impediment (Team) issue types

In addition to the information described above, that you entered when creating or editing an issue, the hierarchy is displayed in the Structure panel.

This panel can be expanded or minimized as required. This functions similarly for all issue types.

8.3.2 - Risk issue type

In addition to the information described above, that you entered when creating or editing an issue, you will see a "Risk assessment" panel where the following information is visualized: Impact, Probability, Residual Impact and Residual Probability.

8.3.3 - Objective (Team) issue type



8.4 - Team Board

The "Backlog" view shows all tasks that are not in an active sprint. Typically you will see several planned and thus still inactive sprints preceding the backlog. Via the "Features" panel on the left side (below Versions) you can drag and drop hierarchical links to issues at the higher level. The linked processes are then shown as in ACE-12, as colored circles on the right of the issue cards. If there are several links, these are summarized in grey circles indicating the number of links. Hover over the grey circle to see the issue keys of the linked issues.


Generally, sprint planning for a PI should be performed as described in section 7.8 at the Program level.

All issues in the sprint, including status information (in columns), are displayed in the "Active Sprint" view.

Access all of the reports provided by Jira, which are important for teams, via the "Reports" view.





  • No labels