Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Current »

This document talks about how we identify and capture blocked work information from each type of data source.

Blocked data in ActionableAgile

ActionableAgile tracks expects two pieces of information in regards to blocked work.

  • Number of days a work item was blocked.

    • When pulling in via a wizard, we count full or partial days as blocked days except for when you block and unblock the item in the same day.

  • Whether or not the work item is currently blocked.

Identifying Blocked Items in Jira (via the Jira Wizard)

When you pull data in via the Jira wizard, blocked items will be identified by the “Flagged” field in Jira.

Identifying Blocked Items in Trello (via the Trello Wizard)

When you pull data in via the Trello wizard, blocked items will be identified by the use of a “blocked” label. This check is currently case-sensitive.

Identifying Blocked Items in Manually Imported Data

Include these two columns immediately following your workflow stages:

Blocked Days

Number of days and item has spent blocked

Blocked

TRUE or FALSE - is the item currently blocked?

Please see the following documentation for more details.


If you have any questions about this, please submit them to our help desk.


/wiki/spaces/AAS/pages/701727230

Cycle Time Scatterplot

Flow Efficiency

  • No labels