-
Suggestion
-
Resolution: Duplicate
-
None
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.
- duplicates
-
- Closed
- is related to
-
- Closed
- relates to
-
- Gathering Interest
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSWSERVER-9875] As a Kanban user I want planning view
| Workflow | Original: JAC Suggestion Workflow [ 3069483 ] | New: JAC Suggestion Workflow 3 [ 3662558 ] |
| Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
| Workflow | Original: Confluence Workflow - Public Facing v4 [ 2626767 ] | New: JAC Suggestion Workflow [ 3069483 ] |
| Workflow | Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2327998 ] | New: Confluence Workflow - Public Facing v4 [ 2626767 ] |
| Status | Original: Closed [ 6 ] | New: Resolved [ 5 ] |
| Workflow | Original: JIRA PM Feature Request Workflow v2 [ 2044868 ] | New: JIRA PM Feature Request Workflow v2 - TEMP [ 2327998 ] |
| Workflow | Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2033228 ] | New: JIRA PM Feature Request Workflow v2 [ 2044868 ] |
| Workflow | Original: JIRA PM Feature Request Workflow v2 [ 736087 ] | New: JIRA PM Feature Request Workflow v2 - TEMP [ 2033228 ] |
| Labels | New: affects-server |
| Workflow | Original: GreenHopper Kanban Workflow v2 [ 559171 ] | New: JIRA PM Feature Request Workflow v2 [ 736087 ] |
| Issue Type | Original: Story [ 16 ] | New: Suggestion [ 10000 ] |
| Priority | Original: Major [ 3 ] | |
| Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
André R.
made changes -
| Description |
Original:
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 (component 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. |
New:
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. |
