Actions
Bug #6847
closedBug #6846: alerts: wrongly using tx id 0 when there is no tx
alerts: wrongly using tx id 0 when there is no tx (6.0.x backport)
Status:
Rejected
Priority:
Normal
Assignee:
-
Target version:
-
Affected Versions:
Effort:
Difficulty:
Label:
Updated by Victor Julien 8 months ago
- Tracker changed from Security to Bug
- Severity deleted (
MODERATE)
Updated by Victor Julien 8 months ago
- Target version changed from 6.0.17 to 6.0.18
Wondering if we should address this in 6 at all.
Updated by Philippe Antoine 8 months ago
Victor Julien wrote in #note-2:
Wondering if we should address this in 6 at all.
I think we can skip this "bug" and leave the behavior as is for 6
Updated by Victor Julien 8 months ago
- Target version changed from 6.0.18 to 6.0.19
Updated by Victor Julien 7 months ago
- Status changed from Assigned to Rejected
- Assignee deleted (
Philippe Antoine) - Target version deleted (
6.0.19)
6 branch is too close to EOL to address this issue.
Actions