Configuring the backlog dependencies
Adding and editing initiatives, epics and stories
このページの内容
関連コンテンツ
- Error and warning messages
- Importing
- Data Center Migration
- Exporting
- How to optimize migration (export and import) of large number of projects from one Bitbucket Server and Data Center instance to another
- LFS Migration
- Bitbucket Data Center Migration export failed with command timed out exception
- Troubleshooting fork not syncing
- Recommended action plan if a repository becomes corrupted in Bitbucket Data Center
- Understanding pull requests in Bitbucket Server
This page refers to Portfolio classic plans. If you are currently running Portfolio 2.0, please check this link to access the latest page version.
How to add and edit dependencies
Dependencies can be set in the details view for epics or stories as follows:
- Go to Backlog > Epics/Initiatives and choose the item you want to configure.
- Click details, which is located next to the item's name.
- Select Edit.
A new window pops up showing the searchable backlog list, allowing you to configure the dependencies. - Select OK once you've finished configuring the the dependencies.
Once you confirm the settings, a compact summary of the defined dependencies is shown directly in the details view. From there, you can also directly remove an item by clicking the X next to the item's name.
Dependencies in the graphical schedule
Dependencies can be displayed in the graphical schedule allowing you to easily identify dependent tasks. See Dependencies in the Graphical Schedule for more information on enabling and using this feature. 
The table below shows some possible dependencies.
| Item Type | Requires item of type | 依存関係 |
|---|---|---|
| ストーリー | ストーリー | Single story depends on the full completion of another single story. |
| ストーリー | エピック | Story depends on completion of an epic, meaning that an epic and all it's child stories need to be completed before this story can be started. |
| エピック | ストーリー | Epic, and with that all stories in that epic, depend on the completion of a single story. |
| エピック | エピック | All stories in an epic depend on the completion of another epic. |
最終更新日: 2019 年 2 月 25 日
関連コンテンツ
- Error and warning messages
- Importing
- Data Center Migration
- Exporting
- How to optimize migration (export and import) of large number of projects from one Bitbucket Server and Data Center instance to another
- LFS Migration
- Bitbucket Data Center Migration export failed with command timed out exception
- Troubleshooting fork not syncing
- Recommended action plan if a repository becomes corrupted in Bitbucket Data Center
- Understanding pull requests in Bitbucket Server
Powered by Confluence and Scroll Viewport.