Uploading a CSV file is just one of many options for loading data into ActionableAgile Analytics.
...
| Widget Connector | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Uploading the file
You begin by navigating to the Data icon in the top right of the gray navigation bar. When you click on the icon, the first option of the bottom section underneath the horizontal rule will be “Load External Data (.csv)”. Click on that.
...
File Format Requirements
| Info |
|---|
The best way to get the acceptable file format for your Jira data is to load a Jira project, board, or filter and then export the raw data via CSV format. That way you will know what format the tool expects. |
...
ID | link | title | <workflow steps> | <additional columns> |
|---|---|---|---|---|
required | optional | optional | required. | optional Arrays should be pipe delimited (value|value) |
Here is an example from a Jira extract:
...
Workflow states
Any workflow stages named “Backlog” & “To do” will be immediately identified as “Not started” stages (they will be unchecked by default in the global chart control Workflow Stages. If those are not found then it will not identify any “Not started” stage by default. You can override this default by unchecking the desired workflow stages in the Global Chart controls.
...
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
Long-form text fields like Descriptions, comments. These aren’t very usable in ActionableAgile and can break your file format easily.
Fields that you won’t use for filtering. They just add clutter and possibilities for breaking your file format.
Backward flow movement
The dates in the file should always increase to reflect a left to right movement in your flow. However, an item might have been moved prematurely and went back on your board, this is what is called “backward flow movement”. If an item is moved backwards in the flow, let’s say from step C to step B, it is considered never to have been in step C at all. All of the time in step C will be added to the time in step B. It will get a new timestamp for step C when it reenters that workflow stage.
...
In this case, you need to correct your file and change the dates, to reflect the last time it moved to each stage.
Sample Files
The tool’s demo sample data
...