Opened 20 years ago
Closed 20 years ago
#878 closed defect (fixed)
Field "resolution" is disabled incorrectly on Advanced Query screen
| Reported by: | pkou <pkou at ua.fm> | Owned by: | Christopher Lenz |
|---|---|---|---|
| Priority: | low | Milestone: | 0.8 |
| Component: | ticket system | Version: | devel |
| Severity: | minor | Keywords: | query |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
Filtering tickets by field Resolution depends on the statuses that are selected by user in field Status. This is because field resolution is empty when a ticket has status new, assigned, or reopened.
Current implementation enables field Resolution if no statuses are selected or when status closed is selected. This is incorrect because when user selects closed and other status like new, the field Resolution is still enabled, and using it leads to empty screens.
Proposed implementation: Enable field Resolution if no statuses are selected or statuses new, assigned, and reopened are not selected.
Patch attached.
Attachments (1)
Change History (3)
by , 20 years ago
| Attachment: | patch-queryres-r1014.diff added |
|---|
comment:1 by , 20 years ago
| Component: | report system → ticket system |
|---|---|
| Keywords: | query added |
| Milestone: | → 0.8 |
| Owner: | changed from to |
| Priority: | normal → low |
| Severity: | normal → minor |
| Status: | new → assigned |
Good catch.
I'd like to avoid hardcoding the resolution names in the script. If we can depend on the order of the status values (which pretty much is a given in the current codebase), a simple check for selectedIndex >= 3 should be enough, and more compact.
Patch for the defect