Bug 1322312 - JobExecutor, TaskList: DueOn time is displayed in 12-hours format without AM/PM info
Summary: JobExecutor, TaskList: DueOn time is displayed in 12-hours format without AM/...
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: Business Central
Version: 6.3.0
Hardware: All
OS: All
unspecified
high
Target Milestone: ER3
: 6.3.0
Assignee: Neus Miras
QA Contact: Lukáš Petrovický
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-30 09:38 UTC by Pavel Kralik
Modified: 2020-03-27 19:33 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-27 19:33:28 UTC
Type: Bug


Attachments (Terms of Use)

Description Pavel Kralik 2016-03-30 09:38:23 UTC
Description of problem:
Creating new Job or Task with DueOn time in 24-hour format is displayed in 12-hour format, but without info about AM/PM.

Eg. DueOn time set to: 30-Mar-2016 00:00 and 30-Mar-2016 12:00 is displayed as 30-Mar-2016 12:00:00

Version-Release number of selected component (if applicable):
BPMS 6.3.0.ER2

How reproducible:
Always

Steps to Reproduce:
1. Create 2 new tasks or jobs and set DueOn time to 00:00 and 12:00
2. Task or jobs are both listed with 12:00:00

Actual results:
12-hour time format

Expected results:
24-hour time format

Additional info:

Comment 2 Neus Miras 2016-03-31 12:36:14 UTC
The date representation depends now on the drools.datetimeformat general configuration property.

I changed the default value of the distribution to show 24-hour time format in this PRs but it will be overwritten by the app general configuration in future installations.

Here the PR
6.4.x
https://github.com/droolsjbpm/kie-wb-distributions/pull/253
master
https://github.com/droolsjbpm/kie-wb-distributions/pull/254 

I'll change the bz status to modified when they are merged

Comment 3 Neus Miras 2016-03-31 13:01:20 UTC
merged!

Comment 4 Pavel Kralik 2016-04-18 10:36:40 UTC
BPMS 6.3.0.ER3


Note You need to log in before you can comment on or make changes to this bug.