要約

Jira Cloud supports customizable work hierarchies that fit your organization’s way of working. 

To configure Jira for a custom Agile framework or custom work hierarchy, you’ll need to make updates to:

• Work types

• Work hierarchy levels

• Work type schemes

ソリューション

Customize work hierarchy 

In this example, we'll update the issue hierarchy to:

• エピック
• Capability
• 機能
• ストーリー
• サブタスク

To view work type settings:

1. Select Settings > Issues

2. In the left column, go to Issue types

From the work type settings screen, you can rename the default Epic work type. To do this:

1. On the Epic issue type, select … > Edit

2. Update the Name field, and select Update

   1. For our example, we'll rename Epic to Feature

Next, we'll add a new work types named Epic and Capability. To do this:

1. Select Add issue type in the top right of the screen

2. In the Name field, enter the new work type name

   1. We'll create Epic first

3. Make sure the Type field is set to Standard Issue Type (Level 0), then select Update

4. Repeat steps 1-3 to add another new work type named Capability

Update your work type hierarchy levels

Next, navigate to the Issue type hierarchy settings in the left column.

1. Select the Epic level name, and change to Feature

2. Select + Create level at the bottom of the list of levels

   1. A new level will be created at the top of the work type hierarchy (level 2)

3. Name this new level Capability and select the corresponding work type that you created on the previous screen

4. Select + Create level to add another level to your hierarchy (level 3)

5. Name this level Epic and select the corresponding work type that you created

6. [変更を保存] を選択します。

Update your work type schemes

Next, navigate to the Issue type schemes settings in the left column.

1. Locate the scheme associated with the project you’d like to apply the new issue hierarchy to, and select … > Edit

2. Drag the Capability and Epic work types into the Issue Types for Current Scheme

3. [保存] を選択します。

Repeat this process to update the schemes for each project you'd like to use the new work hierarchy with.

Your Jira is now configured for your custom Agile framework. The changes you’ve made to your issue hierarchy will be reflected throughout Jira, such as in your plans and when editing an issue.

FAQ

Can I use an existing work type for my custom hierarchy instead of creating a new one?

Yes! However, moving issue types in your issue type hierarchy will break existing parent and child relationships between your work items. This is because work can only have parent and child relationships with work items that are adjacent to them in the hierarchy. For more information, see our documentation on work types.

If you are planning to modify your work type hierarchy, consider first performing a bulk update to update any work items that may be affected. By changing the work type of these items to one that will remain on the same level, you will preserve any relationships that would otherwise be broken.

To do this, select Filters > View all issues and search for the work you want to edit. You can use the following JQL syntaxes to help:

• parent to find all issues that have a particular parent issue ID

• issueType to find all issues of a particular issue type

• key in portfolioChildIssueOf(" ") to find all child issues and all descendant issues of a particular issue ID

Once you’ve found the issues to edit, select … > Bulk change all issues.

Select the issues to change, and choose the Edit Issues operation. In the fields list, select to either assign a new issue type, or assign a new parent.