In addition to loading your Azure DevOps data, you can load external data via a .csv file.
...
You can have any number of generic columns after the workflow steps. If included, each of these columns will be treated as an “attribute” field that can be filtered on (e.g., work item type, project id, team name, etc.).
Right now, to allow the app to differentiate between generic attributes and workflow steps, the first of these columns should NOT be a date column. We are looking to make this unnecessary in future.
If you include are adding a column that will contain an array of values like labels or components, please use a pipe separator. eg. “label1|label2|label3” so that we can properly separate them into individual values in the Item Filter.
Blocked time, for ActionableAgile to give you insights on your blocked time you need to make sure to add 2 columns:
Blocked days (only take in consideration full days, if an item was blocked and unblocked on the same day, it will not be taken into consideration in the calculations)
Blocked (yes if currently blocked, no if not currently blocked)
...
Here’s a tabular description of the instructions above:
ID | link | title | <workflow steps> | <additional columns> |
|---|---|---|---|---|
required | optional | optional | required. | optional Arrays should be pipe delimited (value|value) |
...
All other workflow stages will be considered as “In Progress”. ActionableAgile currently requires two or more of these workflow stages. For example:
TO DO | DOING | RELEASE READY | RELEASING | DONE |
If you only have three total workflow stages including a “Not Started” workflow stage and it doesn’t make sense to add another In Progress workflow stage, you’ll need to change the name of the 1st workflow to be something other than “Backlog” or “To do” as below:
| DOING | DONE |
Additional Tips
Remove any unnecessary columns like these
...