Opened 12 years ago
Closed 12 years ago
#10881 closed defect (worksforme)
referencing tickets in descending order in commit messages creates duplicate comment numbers
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | ticket system | Version: | 0.12.2 |
Severity: | critical | Keywords: | |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
How to reproduce:
1) have 2 tickets with numbers X and Y, where X < Y, Y having more comments than X 2) do a commit with message "refs #Y and #X"
Ticket X gets a new correctly numbered comment, but Y gets a comment with the same number that was added to X creating a duplicate comment number in ticket Y. "refs #X and #Y" seems to work correctly for both tickets.
This doesn't seem to occur with 0.12.4 or 1.0, but it's unclear if the underlying issue has actually been fixed.
System information:
lungs [1006] cat /etc/redhat-release Red Hat Enterprise Linux Server release 5.8 (Tikanga)
Trac | 0.12.2 |
Bitten | 0.6 |
Genshi | 0.6 (without speedups) |
Mercurial | 1.8.2 |
MySQL | server: "5.0.95", client: "5.0.95", thread-safe: 1 |
MySQLdb | 1.2.3 |
Python | 2.6.4 (r264:75706, Feb 23 2010, 12:33:58) [GCC 4.3.1] |
pytz | 2010h |
setuptools | 0.6c11 |
jQuery: | 1.4.2 |
We had some issues with comment numbering in early 0.12.x releases, which seem to have been fixed since (although I'm not sure which changeset actually fixed it, but we never saw the symptom again). I would advise upgrading to 0.12.4.