Processing Flow chart

Processing flow is a sleek visualized timeline of state transitions which also includes miscellaneous User Story or Bug history info.

What's cool about this visual flow: it uncovers some unexposed details which nevertheless reveal if the trend is good or bad very quickly, and answers questions like:

  • How many days has this User Story been in this particular state?
  • Were there any delays?
  • Was there any re-work?
  • Who was responsible for the User Story?
  • When were Bugs and Tasks added and closed?
  • How much time was spent each day?
  • Were there any impediments?

Supported entities: User Stories, Tasks, Bugs, Features, Epics, Requests, Test Plan Runs. Not supported for Projects.

Here's the general idea:

Targetprocess Image

You can spot good or bad development trends with it:

Go to User Story or Bug view and click the Flow tab. Check out some real examples to get the best feel of how useful the Development Flow Chart can be:

Important:

Calculations of Lead and Cycle Time metrics are based on calendar days. All the metrics and reports are based on total number of days or hours an entity spent in a particular workflow state, including afterhours, weekends, and public holidays.

Reports

The reporting capabilities of Targetprocess are described in the dedicated article: Processing Time and Cycle Time Reports