JIRA Agile features are now available in the standalone application JIRA Software. Please upgrade to JIRA Software to get all the latest and greatest features. Visit the Migration Hub for more information, or see the Administering JIRA Applications documentation.

Cycle Time

Cycle time is the time spent working on an issue — typically, the time taken from when work begins on an issue to when work is completed, but also includes any other time spent working on the issue. For example, if an issue is reopened, worked on, and completed again, then the time for this extra work is added to the cycle time.

See Viewing the Control Chart for information about how the cycle time is calculated on the Control Chart.

Was this helpful?

Thanks for your feedback!

Why was this unhelpful?

12 Archived comments

  1. User avatar


    How is work Begun and Completed defined here? i.e what if my Workflow doesn't start with Open and end with Closed?

    29 Nov 2013
  2. User avatar

    Bryan Karsh

    I have the same question. I wish there was more information on how Cycle time is calculated. 

    16 Jan 2014
  3. User avatar

    TSO Logic Admin

    In JIRA land, "Completed" likely means "Resolved" (which also includes "Closed", unless you have somehow managed to mess with the workflows at a lower level).

    "Begins" is still ambiguous in general.  In terms of the Control Chart, cycle time would cover whatever statuses/columns you choose to include in the time calculation.


    06 Feb 2014
  4. User avatar

    Uri Abramson

    Do you have anywhere an option to see mean cycle time per story point? The issues are very different in size and having this option could really help estimations for kanban.

    07 Sep 2014
    1. User avatar

      Marcus Pfeiffer

      Hi Uri,


      I have asked myself the same question and adopted the way Dan Radigan [Atlassian] has described it in his article from earlier this year: http://blogs.atlassian.com/2014/04/6-key-ways-optimize-development-control-chart/


      Scroll down to section 3. - "Make better estimates" and you will (probably) find the answer you're looking for.  


      Hope this helps!

      04 Dec 2014
  5. User avatar

    Marcus Pfeiffer

    Hi y'all,


    Maybe asking a blatantly obvious question here - hope someone can answer this for me (perhaps Dan Radigan [Atlassian] knows? ;o):


    when I'm looking at - let's say - an average cycle time of 

    1w 1d 5h

    does this mean: 1w = 7d x 24h (i.e. 168h)

    or is it always referring to working days & hours: 1w = 5d x 8h (i.e. 40h)






    04 Dec 2014
    1. User avatar

      Andrew Lui [Atlassian Technical Writer]

      Hi Marcus,

      I've clarified this on the Control Chart documentation (see second last question). In summary, 1w represents 7 days and 1d represents 24 hours.

      Kind regards,

      05 Dec 2014
      1. User avatar

        Rina Sarkar

        But usually a work day is only 8 hours right? So isn't the cycle time in hours a bit over inflated?

        24 Mar 2015
  6. User avatar

    Rina Sarkar

    So how do I see cycle time by story size (averaging all stories regardless of size doesn't mean much if you are trying to get better with sizing) and also by assignee?

    24 Mar 2015
  7. User avatar

    Gabe Louet


    I have a Kanban board and reading your documentation, issues that aren't mapped to one of the columns of the board will not be included in the Control Chart.

    I do not want the last column of my board to grow and grow so I do not have a column for Closed calls. When a call has this status, it is off our radar and our board basically visualises next, in progress and resolved calls. It keeps the board relevant.

    Unfortunately the Kanban Reports do not include Closed calls in the cycle time graph which makes it practically useless.

    Is my only option to include all Closed calls on my JIRA kanban board?

    14 Sep 2015
  8. User avatar

    Martin Jopson [Atlassian]

    They need to be mapped for reporting. There is an additional filter for the work mode (Kanban board) which does not affect the reports, you could use this to hide the closed calls while retaining them for reporting.

    Please see Configuring Filters#AddingaSub-FilterforKanbanboards

    15 Sep 2015
    1. User avatar

      Gabe Louet

      Thanks, that worked

      15 Sep 2015
Powered by Confluence and Scroll Viewport