View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0023606 | mantisbt | administration | public | 2017-11-08 05:46 | 2017-12-30 18:36 |
Reporter | mokraemer | Assigned To | atrol | ||
Priority | normal | Severity | minor | Reproducibility | always |
Status | closed | Resolution | unable to reproduce | ||
Product Version | 2.8.0 | ||||
Summary | 0023606: editing an existing version corrupts date field | ||||
Description | if you edit an existing version the date field is shown in native format (dd.mm.yy) not the expected iso format (yyyy-mm-dd). | ||||
Steps To Reproduce | show mantisbt in e.g. german version. go to administration, select a project, add a version & edit. If you edit an existing entry, the date field is also corrupted. If you just save this entry, it is set to the current date! | ||||
Tags | No tags attached. | ||||
Attached Files | |||||
I am not able to reproduce the issue using the given information. |
|
I think this is exactly the issue. I didn't find this one. |
|
0023578 does not change any functionality, this is just a documentation change. |
|
Oh I see. This is common format in germany. I've attached you some screenshots, you can see the original date and what the dialog/selector looks like. |
|
I am not able to reproduce your issue, at least if I am following the documentation mentioned at 0023606:0058164 which tells you
I don't see any problem when setting |
|
But the dateformat is I've solved the problem by changing the format to "Y-m-d", which is easier for sorting. |
|
I am not sure if you read the documentation, especially the note
The picker date setting uses this format http://momentjs.com/docs/#/displaying/format/ Can I set the issue to resolved, or do you think there is something wrong in Mantis? |
|
I think it is still an issue, but since I was the only one, close it for now, I'm ok with it. |
|
What's wrong when using the following settings? |
|
if you use them, the datepicker doesn't work correctly, as shown in the picture. |
|
I tried again using Firefox 57, Chrome 63 and Safari 11 and was not able to reproduce the issue. Set to resolved as mentioned at 0023606:0058448 |
|