-
Suggestion
-
Resolution: Fixed
-
None
Testing Notes
Q: What happens in the case with an issue that has a subtask not captured by the filter?
A: Nothing - the count is for parent issues and not sub-tasks, so the count will not be affected.
Q: Test to see this works with Stories Swimlane config, as well as Queries.
A: Still works, though it is less clear what the issue count refers to given that you do not see the parent issue in the column it is in.
Q: What about negative numbers?
A: They continue to not be allowed - same input controls for constraints as before.
Q: Is this customizable for individual constraints, or globally for all constraints?
A: For the whole board, not individual columns
Q: What if the last parent is removed from that column but it's subtasks remain?
A: The count drops to zero.
Q: What happens if there is no subtask issuetype?
A: Nothing - the count should not be affected by issues which do not exist
Q: What happens when there are quick filters active that filter out parent issues? What happens when there are quick filters active that filter out sub-task issues?
A: The count should still display the appropriate number of issues - so if column constraint excludes sub tasks then filtering out parents should set all visible counts to 0.
- is duplicated by
-
JSWCLOUD-4243 As a user I want subtasks not to be included in my Kanban WIP limits
- Closed
- is related to
-
JSWCLOUD-2245 As a GH user I would like my column constraints on the TB to provide a sub-task count
- Closed
-
JSWCLOUD-4010 Ability to set column constraints separately for each column (and by other fields, not just item count)
- Closed