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

Technical Tasks do not show up on the Planning tab of a rapid board

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Fixed
    • None
    • 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.

      Apptio Support Entitlement number (SEN): SEN-2019309

      Our developers like to use Technical Tasks to break down the work involved in a user story. Unfortunately we can't use them, because they don't show up on the planning tab of a rapid board. This doesn't make any sense to us - we should be able to see and pull a unit of work onto a sprint. It shouldn't be hidden by the parent user story.

      When we checked on this earlier we were told this was by design.
      https://answers.atlassian.com/questions/108172/planning-sprint-in-greenhopper-6-with-scrum-board-no-subtasks-shown?page=1#251048
      This response is not satisfactory and inconsistent with behavior for your JIRA OnDemand product (which does allow you to view Technical Tasks) in planning mode. Please address this.

      The suggestion that we repurpose Epics to provide this functionality is not a viable option for us. We already use Epics and it doesn't make sense for us to radically shift how we classify issues to work around what appears to be a bug in your downloadable product.
      Clearly from the above link we're not the only company who wants this fixed.

      Ideally (but not required):
      1) Tasks should be shown in an hierarchial view under their parent
      2) Task points should roll up to a story
      Internal reference: SCM-709, SCM-713

              Unassigned Unassigned
              406afdf67383 Peter Denniston
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: