Uploaded image for project: 'Jira Software Cloud'
  1. Jira Software Cloud
  2. JSWCLOUD-9113

How do we configure estimation and time tracking

    XMLWordPrintable

Details

    • Suggestion
    • Resolution: Answered
    • None
    • None
    • Using Jira demand
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

    Description

      We are a small publishing company and new to JIRA. We aim to use it for running a small in-house web development team, and also some company processes like IT.

      We want to use agile boards to plan an execute work.
      We have many and varied requirements and have found the best way for us is to put them in as stories describing the need/benefit of meeting; then attaching subtasks with detailed time estimates.
      This works well until we get to reporting. When we look at Agile reports, all the lines are flat.

      We are using time estimation, not story points.

      What do we need to do to set ourselves correctly?

      Attachments

      1. Grab - screenshot of a typical story with sub tasks
      2. Grab1.jpg The issues in agile view. Our sub task time estimates show up. But there is no figure at story level
      3. Grab2.jpg - our burnt-out burn down chart!

      Attachments

        1. grab.jpg
          376 kB
          David Nunn
        2. grab1.jpg
          261 kB
          David Nunn
        3. grab1.jpg.pdf
          1.26 MB
          David Nunn
        4. grab1.jpg.pdf
          1.26 MB
          David Nunn
        5. grab2.jpg
          175 kB
          David Nunn

        Issue Links

          Activity

            People

              Unassigned Unassigned
              c914a2265111 David Nunn
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: