We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.

    • 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.

      Background: For those of us that either practice scrumban or happen to have a large backlog of stories, planning view is starting to become a very nice tool for keeping the backlog in order with it version and epic views (components missing btw). Plain kanban board forces you to use plain JIRA for planning, involving several workflow states and even several projects if you have several kanban teams.

      Possible way to implement: Use the exact same approach as done for scrum, as it allows two different teams to work on same issue pools thanks to sprint assignment. However dates can be skipped as the sprint will basically never end, instead a normal kanban mode deploy is done from time to time, while people still continue to work on issues in progress.

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.

              • 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.

                Background: For those of us that either practice scrumban or happen to have a large backlog of stories, planning view is starting to become a very nice tool for keeping the backlog in order with it version and epic views (components missing btw). Plain kanban board forces you to use plain JIRA for planning, involving several workflow states and even several projects if you have several kanban teams.

                Possible way to implement: Use the exact same approach as done for scrum, as it allows two different teams to work on same issue pools thanks to sprint assignment. However dates can be skipped as the sprint will basically never end, instead a normal kanban mode deploy is done from time to time, while people still continue to work on issues in progress.

                        Unassigned Unassigned
                        137aeec33fee André R.
                        Votes:
                        0 Vote for this issue
                        Watchers:
                        1 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                              Unassigned Unassigned
                              137aeec33fee André R.
                              Votes:
                              0 Vote for this issue
                              Watchers:
                              1 Start watching this issue

                                Created:
                                Updated:
                                Resolved: