Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-6175

As a Kanban PO I would like the Plan mode so that I may order and groom a large backlog

    XMLWordPrintable

Details

    • Hide

      Atlassian Status as at November 2016

      The Kanban Backlog feature is now available for JIRA Software Cloud. The release of Kanban Backlog for JIRA Software Server will be tracked at https://jira.atlassian.com/browse/JSW-15236 - please add your votes and comments on that issue and continue to watch it for further updates.

      The Epics panel is available for the Kanban Backlog but is not enabled by default. This is because the epic issue type has historically been available for display as a card. To change the epics to display in the Epics panel there is an option in the board configuration once the Kanban Backlog is enabled i.e. has a status mapped to it.

      The addition of estimates for Kanban is tracked elsewhere at https://jira.atlassian.com/browse/JSW-7265
      and there are a number of related Suggestions and improvements for Kanban planning which are tracked separately.

      Kind regards,
      Martin
      JIRA Software

      Show
      Atlassian Status as at November 2016 The Kanban Backlog feature is now available for JIRA Software Cloud. The release of Kanban Backlog for JIRA Software Server will be tracked at https://jira.atlassian.com/browse/JSW-15236 - please add your votes and comments on that issue and continue to watch it for further updates. The Epics panel is available for the Kanban Backlog but is not enabled by default. This is because the epic issue type has historically been available for display as a card. To change the epics to display in the Epics panel there is an option in the board configuration once the Kanban Backlog is enabled i.e. has a status mapped to it. The addition of estimates for Kanban is tracked elsewhere at https://jira.atlassian.com/browse/JSW-7265 and there are a number of related Suggestions and improvements for Kanban planning which are tracked separately. Kind regards, Martin JIRA Software
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

    Description

      This should offer similar functionality to the planning mode for the Scrum Boards as in Using Plan Mode. For example:

      • Display and estimate.
      • Organising via Epics.
      • Column Done status.
      • Swim lane and cell constraints.

      Attachments

        1. agile board filter.png
          agile board filter.png
          210 kB
        2. create.png
          create.png
          28 kB
        3. feedback-icon.png
          feedback-icon.png
          8 kB
        4. feedback-icon.png
          feedback-icon.png
          7 kB
        5. flaimo_1.png
          flaimo_1.png
          118 kB
        6. flaimo_2.png
          flaimo_2.png
          5 kB
        7. flaimo_3.png
          flaimo_3.png
          33 kB
        8. kanban-plan.jpg
          kanban-plan.jpg
          108 kB
        9. mj-backlog.png
          mj-backlog.png
          213 kB
        10. mj-config.png
          mj-config.png
          127 kB
        11. mj-getready.png
          mj-getready.png
          131 kB
        12. screenshot-1.png
          screenshot-1.png
          18 kB
        13. screenshot-2.png
          screenshot-2.png
          22 kB
        14. screenshot-3.png
          screenshot-3.png
          114 kB
        15. screenshot-4.png
          screenshot-4.png
          165 kB
        16. screenshot-5.png
          screenshot-5.png
          115 kB

        Issue Links

          Activity

            People

              Unassigned Unassigned
              nmuldoon Nicholas Muldoon [Atlassian]
              Votes:
              1079 Vote for this issue
              Watchers:
              655 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: