Anonymous | Login | Signup for a new account | 2021-01-21 04:45 GMT | ![]() |
Main | My View | View Issues | Change Log | Roadmap |
View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||||||
0001206 | SiT! | feedback | public | 2010-03-30 17:02 | 2010-03-30 19:38 | ||||||||
Reporter | Tomse | ||||||||||||
Assigned To | |||||||||||||
Priority | normal | Severity | minor | Reproducibility | always | ||||||||
Status | confirmed | Resolution | open | ||||||||||
Platform | BSD | OS | FreeBSD | OS Version | 6.4+Later | ||||||||
Product Version | 3.60 LTS | ||||||||||||
Target Version | Fixed in Version | ||||||||||||
Summary | 0001206: Marking an incident for closure (and not close) - shows bad date in feedback form (user) | ||||||||||||
Description | the date that is shown as Closed is "1. Jan 1970" this shows the correct date once the incident is closed totally | ||||||||||||
Tags | No tags attached. | ||||||||||||
Attached Files | |||||||||||||
![]() |
|
paulh (administrator) 2010-03-30 19:33 |
yeap can repro this |
paulh (administrator) 2010-03-30 19:38 edited on: 2010-03-30 19:38 |
This is caused by reading the closed column from incidents which doesn't get set until proper closure, would could potentially set the closed time when marking for closure though not sure what this would break (and its not really closed yet) I think the better option would be as per Mantis 1207 and don't generate the feedback until proper closure. |
![]() |
|||
Date Modified | Username | Field | Change |
2010-03-30 17:02 | Tomse | New Issue | |
2010-03-30 19:33 | paulh | Note Added: 0002900 | |
2010-03-30 19:33 | paulh | Status | new => confirmed |
2010-03-30 19:36 | paulh | Relationship added | related to 0001207 |
2010-03-30 19:38 | paulh | Note Added: 0002901 | |
2010-03-30 19:38 | paulh | Note Edited: 0002901 | View Revisions |
Copyright © 2000 - 2021 MantisBT Team |