Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

In addition to loading your Azure DevOps data, you can load external data via a .csv file.

...

  • The first row of any file must be the column names for each of the data fields. Column titles cannot have new lines, unclosed quotes, or special characters.

  • The first column must be an item ID field and must have uppercase “ID” somewhere in the column name.

  • The second column is optional, but if included, it must be called “link” and must contain a hyperlink. This hyperlink could be to the item’s location in your Agile tool. If you don’t have this information in your data, add an empty column with the name “link”.

  • The third column is optional, but if included, it must be the item’s title (or name or description) field and must have the word “title” or “name” somewhere in the column name.

  • The next set of contiguous columns must be the sequential steps of your workflow. The contents of these columns are the date the item entered each workflow step. A backlog step is optional, but if you include it, it must be the first column of your workflow, and it must have the word “backlog” somewhere in the column title.

There must be a date present in all workflow stage columns. Even if an item skipped a stage, the column must be backfilled with the date of when they went to the next column.

  • 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)

The Blocked Column must be located after the workflow stage columns.

Here’s a tabular description of the instructions above:

ID

link

title

<workflow steps>

<additional columns>

required

optional

optional

required.
create one column for each workflow step in linear order. The name of the columns will be the name of the workflow stages.

optional
columns representing different attributes of your work. Each column will be a select list in your item filter global and chart controls.

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:

TO DO NOT STARTED

DOING

DONE

Additional Tips

Remove any unnecessary columns like these

...