#5807 closed defect (duplicate)
tickets imported from bugzilla crash ticket system when closed if no milestone is set
Reported by: | Owned by: | Jonas Borgström | |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | ticket system | Version: | 0.10.3 |
Severity: | normal | Keywords: | |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
We used bugzilla2trac to move about 100 bugs over to trac. The milestone field didn't get set in the translation, so it was blank in trac. When we closed a bug without setting a milestone, the ticket system seemed to crash. We couldn't run any queries on the tickets. We got a page of error messages. Sorry, I didn't capture them, and I can't seem to reproduce them now that all the tickets have milestones set.
The only way we were able to recover from this was to follow the browser history back to the closed bug, set a milestone, and then submit the changes. If would have closed the browser I am not sure how we would have recovered.
I am guessing that this problem would only occur when someone is importing bugs into trac. This could create a very negative experience for new users who are just switching over to trac.
Attachments (0)
Change History (3)
comment:1 by , 17 years ago
comment:2 by , 17 years ago
Priority: | high → normal |
---|---|
Resolution: | → duplicate |
Severity: | blocker → normal |
Status: | new → closed |
Version: | → 0.10.3 |
Hi Jim,
It looks like you're still using Trac 0.10.3. This looks like a duplicate of #4218 which should be fixed in 0.10.4. Feel free to reopen if upgrading doesn't solve it for you.
comment:3 by , 17 years ago
Replying to thatch:
Feel free to reopen if upgrading doesn't solve it for you.
.. but not as a blocker ticket: bugzilla2trac script is located in the /contrib
directory. Please refer to the README file that is stored in the same directory
I was able to reproduce it.