Mingle’s Dependency Tracker
You can find the official documentation here
Why should I use the dependency tracker?
The Dependency Tracker is for either one or several projects that have cards whose development depends on each other. It can be difficult to keep track of these dependencies using card properties or trees especially if they are scattered across several projects. The Dependency Tracker gives you a visual representation of the cards that have dependencies as well as any detail you would like to know about the card.
The dependency tracker is best used to keep track of those dependencies, and signifies with the colors red (for no) and green (for yes) whether or not the more “parent” card’s dependent cards have met basic criteria to transition.
What are the dependency tracker’s limitations?
The Dependency Tracker’s main limitation is that it doesn’t perform card manipulations for you - it is meant solely to keep track of card dependencies.
What is standalone vs program mode and when would I use each?
In standalone mode, the Dependency Tracker uses the free text field of Dependee and Depender properties to create relationships between cards within and between projects. These relationships are embodied by new cards of the type Dependency (as we created before). Once you set up the macro, you will see that the macro creates these cards as you create the dependencies.
In program mode, the Dependency Tracker uses these card properties/types to create cards and dependencies using data from the specified projects within its own project.
What are the three types of dependency trackers and when would I use each?
dependency-tracker-card
Displays any and all dependencies related to the card it is in.
dependency-tracker-project
Displays any and all dependencies related to the project it is in. Project Dependency Tracker can either operate in In Project Dependency Mode or Cross Project Dependency Mode by toggling the Projects parameter.
dependency-tracker-program
Displays any and all dependencies related to the projects specified within the Projects parameter. Note that these projects must have Dependee, Depender and Dependency in order to appear (see below).
How do I set up each level of dependency tracker?
In every project you would like to use this macro in, you must set up two card properties and one card type in that order :
- An “any text” Property called Depender
- An “any text” Property called Dependee
- A Card Type called “Dependency” has Depender and Dependee available to it
- This applies to standalone and program mode
The parameters that all dependency trackers can take are as follows:
met - REQUIRED - this criteria takes a card property and value and is compared to the “depender” cards. If these criteria are met, the dependee card will show green. If not, they will show red.
properties - other properties to be displayed in the table
card-type - types to be displayed in the tool
filter - this parameter is often used filter out cards by release, sprint, etc.
project - to be used both in the project (standalone mode) and program (standalone and program mode) trackers. this identifies the projects across which
dependency-project - (program mode) this identifies the project where the dependencies are stored
In Standalone Mode:
You can then initiate the macro as you would with any other macro. The configurations below are just basic examples of parameters necessary within each macro however, the parameters outlined above are all available to each macro.
In Project Card Dependency Tracker
dependency-tracker-card
met: Status = Accepted
properties: [Status, Owner]
In Project Dependency Tracker
dependency-tracker-project
met: Status = Accepted
card-type: [Story, Defect]
properties: [Type, Status]
Cross Project Dependency Tracker in Standalone mode
dependency-tracker-project
met: Status = Accepted
card-type: [Story, Defect]
properties: [Type, Status]
project: [example_project_1, example_project_2]
In Program Mode:
Cross Project Dependency Tracker in Program Mode
dependency-tracker-project
met: Status = Accepted
card-type: [Story, Defect]
properties: [Type, Status]
project: [example_project_1, example_project_2]
dependency-project: dependency_project
Dependency Project Program Configuration
dependency-tracker-program
met: Status = Accepted
properties: [Status, Owner]
project: [project_1, project_2]
dependency-project: dependency_project
Comments
1 comment
Not too helpful. I'm looking for instructions / example of how to use the UI to create intercard dependencies in a project.
Please sign in to leave a comment.