Feature #19171
"any open / none open" filter for ( follows / blocked ) relationships
| Status: | Closed | Start date: | ||
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | Issues | |||
| Target version: | - | |||
| Resolution: | Duplicate |
Description
Currently you can filter issues with related issues.
| is |
| any issues in project |
| any issues not in project |
| no issues in project |
| none |
| all |
Propose that adding
| any open |
| none open |
Would improve the software
- You could then construct issue queries that only return issues that can actually be progressed
- This reduces your cognitive load having to think about whether a given task can be done or not
- Can also construct queries that return issues that are blocked by something
- This allows you to troubleshoot their dependencies
Related issues
History
#1
Updated by Matteo Bonaker over 7 years ago
#2
Updated by Adrian Wilkins over 7 years ago
Agree that this is a dupe of #15029, but not #3265
#3265 was the creation of the relationship-filtering feature, this ticket and #15029 refer to improving that filter so that you can use it to find issues with and without active blockers.
There's also a patch #16621 which seems to implement this ; I couldn't get this to apply against 3.0.3 - I've asked the original author which revision he patched in #16621#note-2
#3
Updated by Mischa The Evil over 7 years ago
- Duplicates Feature #15029: When filter by "blocked by" = "any", take into account if blocking issue is already closed (so no really blocking) added
#4
Updated by Mischa The Evil over 7 years ago
- Status changed from New to Closed
- Resolution set to Duplicate