Some dependency work is repetitive: one feature blocks five others, or twenty dependencies need the same new status. These two tools take the clicking out of it.
When to use these tools
Dragging between two cards is the quickest way to create a single dependency, as described in Dependencies. Two situations call for something else:
The receiver is far away on the board, on another ART, or one feature blocks several others. Use Create by Search.
After a sync meeting many dependencies need the same update, for example a new status or target date. Use Edit Selected on the Dependency Tracking page.
The dependency handle on a card
Hover the dependency handle at the top right of a feature card. Kendis shows the dependency counts of the card and a +.
The handle of Express checkout with Apple Pay on hover: the story-level count, the feature's own count and the + for a new dependency.
Click a count to open Item Dependencies, the list of that item's dependencies.
Click + (Create Dependency) and then the receiving card to link two cards directly.
Capability cards show three counts, one each for the capability, feature and story level.
Create a dependency with Create by Search
Click the count on the handle of the providing item to open Item Dependencies.
Click Create by Search at the top right. The Dependencies dialog opens with the providing item already filled in.
Under Receiver click Select Target.
In the picker choose the Board (any PI board of the solution), optionally a Sprint and the Item Type (Epic or Feature), or type in Search Items. The picker lists items that are planned in a sprint of that board.
Tick the receiving items and click Select. You can tick up to five each time you open the picker.
Back in the Dependencies dialog every chosen receiver is listed under Select Target. Remove takes one out again.
Choose the Link Type and fill in Summary, Description, Status, Target Resolution Date, Responsible and Reporter. Link Type, Receiver and Status are required.
Click Save.
Select Target for Express checkout with Apple Pay: Mobile App ART is chosen as the board and two of its features are ticked.
One providing feature and two receivers. The values entered below are used for both dependencies.
Kendis creates one dependency per receiver, all with the same link type, summary, status, dates and people. A pair that is already linked is skipped, and Kendis tells you that the link already exists. The new lines appear on the board straight away.
ⓘ Good to know
The picker accepts up to five receivers each time you open it, and tells you when you tick a sixth. To add more, click Select Target again; the new picks are added to the list. Do not pick an item twice: if the second selection contains a receiver that is already listed, that whole selection is dropped.
Edit several dependencies at once
Open More › Dependencies, or the Dependency Tracking tab of Analytics.
Tick the box in front of a group to select every dependency in it, or expand the group and tick single rows.
The Bulk Actions bar appears at the bottom and shows Dependencies Selected with the number. Click Edit Selected.
In Edit Dependencies each line reads Field – SET TO – New Value. The first line is Status.
Click Add Another for every further field you want to change. With more than one line, the red minus removes a line.
Click Execute Changes. Kendis shows how many changes were applied.
All four dependencies of the Web Store ART group are selected; the Bulk Actions bar offers Edit Selected.
Edit Dependencies for four selected dependencies, with Status and Target Resolution Date to be set.
Field | Use it to |
Status | Move all selected dependencies to one status, for example Accepted after the ART sync. |
Target Resolution Date | Give them a common date. |
Responsible / Reporter | Hand a set of dependencies to one person. |
Raised On | Correct the date they were raised. |
Comment | Add the same comment to each of them. |
Status, the two dates and Comment need a value. Responsible and Reporter may be left empty to clear them.
Feature and story dependencies follow the workflow of their PI board, and capability dependencies the workflow of the solution board. When the selection spans several workflows, Status shows one box per workflow and each needs a value.
Dependencies synced with Jira or Azure DevOps can be edited in bulk as well.
Cancel on the Bulk Actions bar asks for confirmation and then clears the selection.
With a Subgroup By set, every sub-group has its own tick box.
ⓘ Tip
Click a summary tile first, for example Overdue, to list only those dependencies, then tick the groups and edit them together.
Frequently asked questions
How many receivers can one dependency have?
How many receivers can one dependency have?
Each dependency has one receiver. Create by Search lets you pick up to five receivers each time you open the picker and creates one dependency for each.
I do not see Create by Search.
I do not see Create by Search.
The button is hidden when the board is locked or when your role may not create or edit dependencies.
The feature I need is not in the Select Target list.
The feature I need is not in the Select Target list.
Check the Board and Sprint boxes, and that Item Type is set to the right level. The picker lists only items that are planned in a sprint of the chosen PI board, so a feature that is still unplanned does not appear.
Can I set different values per receiver?
Can I set different values per receiver?
Not while creating. Save, then open a single dependency from Item Dependencies or Dependency Tracking and edit it.
More › Dependencies asks me to reset my filters.
More › Dependencies asks me to reset my filters.
Board filters would hide part of the list, so Kendis offers to reset them first. After the reset, choose More › Dependencies again to open Dependency Tracking.
Which dependencies can I edit in bulk?
Which dependencies can I edit in bulk?
Any that are listed on Dependency Tracking, across all PI boards of the solution.