bug #7979
closed
Registration date and time, display
Added by Wolf-Henning Kusber over 5 years ago.
Updated over 2 years ago.
Description
Test porta: Registration date is fine,
but registration time displays the system time of the computer.
Registration on 2019-01-11 17:36:56 in
Registration on 2019-01-11 17:39:01 in
Solution: get time of registration of omit time.
- Subject changed from Registration time, display to Registration date and time, display
- Priority changed from New to Highest
Corrected description: Test and Production portal:
Registration date and registration time displays the system time of the user's computer.
Observation: between 2019-01-11 17:36:56 and 2019-01-11 17:39:01
Registration on 2019-01-11 17:36:56 in
F5
Registration on 2019-01-11 17:39:01 in
Solution: get date of registration (and time) as stored in the CDM database.
- Status changed from New to In Progress
This happens always when the Registration.registrationDate is null. The date should also be null in the json response but the DateTimeJSONValueProcessor produces now in case of null.
- Status changed from In Progress to Resolved
- % Done changed from 0 to 50
- Assignee changed from Andreas Kohlbecker to Wolf-Henning Kusber
can be reviewed once the test server is up to date
- Status changed from Resolved to Closed
- Assignee changed from Wolf-Henning Kusber to Andreas Kohlbecker
- % Done changed from 50 to 100
Test portal and Release Portal (checked 2019-04-12):
Displayed dates are correct.
Registrations made in Vaadin are displayed correctly as datetime, such as:
Registration on 2018-07-12 18:31:51
Variant 1 (not many registrations) Registration made in TaxEditor:
Registration on 2018-06-08 00:00:00 in PhycoBank Berlin
This is acceptable
Variant 2 (c. 1000 registration) Registrations made 1998/1999 by IAPT:
Registration on 1998-03-13 00:00:00 in Berlin
This is acceptable
Can we adapt milestone or remove it?
Andreas Müller wrote:
Can we adapt milestone or remove it?
??
Also available in: Atom
PDF