| Reporter |
Doug Mayer (dougebp)
|
|---|---|
| Created | Mar 20, 2013 12:18:13 AM |
| Updated | Jun 17, 2013 10:04:47 PM |
| Priority | Major |
| Type | Usability Problem |
| State | Open |
| Assignee | Vadim Gurov (vgurov) |
| Subsystem | Agile Board |
| Fix versions | 5.0 |
| Fixed in builds | No Fixed in build |
| Affected versions | 4.2 |
| Browser | Any Browser |
| OS | Any OS |
| Verified in build | Not verified |
| Verified by | Nobody |
| Reviewed by | No reviewed by |
| Severity | Routine |
What steps will reproduce the problem?
1. Create a project and enable agile
2. Set the project's "Field to identify sprints" to a version[1] or version[*] field with no records
3. Fill the project with 1010 issues
4. Move the first 1000 issues to a state that doesn't show up on the board (i.e. Fixed, in our case). Leave the last 10 issues in a state that will show up on the board.
5. Agile board will NEVER show anything after the first 1000 issues
What is the expected result?
The last 10 issues should show up on the board
What happens instead?
The board is completely empty and contains the message: This sprint contains more than 1000 issues. Only first 1000 are processed.
You boast that you support Kanban workflows by just not using any sprints, yet this suggests either we're using it wrong or no one has ever tried to use YouTrack in Kanban mode with more than 1000 issues?
1. Create a project and enable agile
2. Set the project's "Field to identify sprints" to a version[1] or version[*] field with no records
3. Fill the project with 1010 issues
4. Move the first 1000 issues to a state that doesn't show up on the board (i.e. Fixed, in our case). Leave the last 10 issues in a state that will show up on the board.
5. Agile board will NEVER show anything after the first 1000 issues
What is the expected result?
The last 10 issues should show up on the board
What happens instead?
The board is completely empty and contains the message: This sprint contains more than 1000 issues. Only first 1000 are processed.
You boast that you support Kanban workflows by just not using any sprints, yet this suggests either we're using it wrong or no one has ever tried to use YouTrack in Kanban mode with more than 1000 issues?