• Type: Bug
• Resolution: Unresolved
• Priority: Low
• Component/s: Administration - Workflows and Statuses, Issue View - Field Format and Display
• Labels:

  None

[JRACLOUD-93370] Date compare validator error for Custom fields with Date Time picker failing comparison with or without the Include time part option enabled

Abhishek Chauhan made changes - 27/Feb/2025 5:38 PM

Status

Original: Needs Triage [ 10030 ]

New: Gathering Impact [ 12072 ]

Roger B. made changes - 27/Feb/2025 1:40 PM

Component/s

New: Administration - Workflows and Statuses [ 66293 ]

SET Analytics Bot made changes - 26/Feb/2025 4:00 AM

Support reference count

New: 1

Roger B. made changes - 24/Feb/2025 7:17 PM

Description

Original: h3. Issue Summary Date compare validator error for Custom fields with Date Time picker failing comparison with or without Include time part option enabled h3. Steps to Reproduce  # On a workflow transition add a Date Compare Validator  # Select a Date time custom field a condition great ">" or great equal ">=" to an expression like *now* or *>= 1d* h3. Expected Results When the transition is triggered the validator respects the time and expression configured. h3. Actual Results The date and time are not respected with several hours of difference, with or without the Include time part option enabled. \With the Include time part option enabled, it should respect a 24h difference, considering the hours the transition is triggered and the [user timezone|https://id.atlassian.com/manage-profile/account-preferences?ref=jira&src=personalsettings]. With the Include time part option disabled, it should respect the start of the next date 00:00:00, considering the date the transition is triggered and the [user timezone|https://id.atlassian.com/manage-profile/account-preferences?ref=jira&src=personalsettings]. h3. Workaround The user in this case can use a *date type* custom field, so the start of day will be considered in the comparison.

New: h3. Issue Summary Date compare validator error for Custom fields with Date Time picker failing comparison with or without Include time part option enabled h3. Steps to Reproduce  # On a workflow transition add a Date Compare Validator  # Select a Date time custom field a condition great ">" or great equal ">=" to an expression like *now* or *>= 1d* h3. Expected Results When the transition is triggered the validator respects the time and expression configured. h3. Actual Results The date and time are not respected with several hours of difference, with or without the Include time part option enabled. With the Include time part option enabled, it should respect a 24h difference, considering the hours the transition is triggered and the [user timezone|https://id.atlassian.com/manage-profile/account-preferences?ref=jira&src=personalsettings]. With the Include time part option disabled, it should respect the start of the next date 00:00:00, considering the date the transition is triggered and the [user timezone|https://id.atlassian.com/manage-profile/account-preferences?ref=jira&src=personalsettings]. h3. Workaround The user in this case can use a *date type* custom field, so the start of day will be considered in the comparison.

Roger B. made changes - 24/Feb/2025 7:16 PM

Description

Original: h3. Issue Summary Date compare validator error for Custom fields with Date Time picker failing comparison with or without Include time part option enabled This is reproducible on Data Center: (yes) / (no) h3. Steps to Reproduce  # On a workflow transition add a Date Compare Validator  # Select a Date time custom field a condition great ">" or great equal ">=" to an expression like *now* or *>= 1d* h3. Expected Results When the transition is triggered the validator respects the time and expression configured. The date and time are not respected with several hours of difference, with or without the Include time part option enabled. h3. Actual Results With the Include time part option enabled, it should respect a 24h difference, considering the hours the transition is triggered and the [user timezone|https://id.atlassian.com/manage-profile/account-preferences?ref=jira&src=personalsettings]. With the Include time part option disabled, it should respect the start of the next date 00:00:00, considering the date the transition is triggered and the [user timezone|https://id.atlassian.com/manage-profile/account-preferences?ref=jira&src=personalsettings]. h3. Workaround The user in this case can use a *date type* custom field, so the start of day will be considered in the comparison.

New: h3. Issue Summary Date compare validator error for Custom fields with Date Time picker failing comparison with or without Include time part option enabled h3. Steps to Reproduce  # On a workflow transition add a Date Compare Validator  # Select a Date time custom field a condition great ">" or great equal ">=" to an expression like *now* or *>= 1d* h3. Expected Results When the transition is triggered the validator respects the time and expression configured. h3. Actual Results The date and time are not respected with several hours of difference, with or without the Include time part option enabled. \With the Include time part option enabled, it should respect a 24h difference, considering the hours the transition is triggered and the [user timezone|https://id.atlassian.com/manage-profile/account-preferences?ref=jira&src=personalsettings]. With the Include time part option disabled, it should respect the start of the next date 00:00:00, considering the date the transition is triggered and the [user timezone|https://id.atlassian.com/manage-profile/account-preferences?ref=jira&src=personalsettings]. h3. Workaround The user in this case can use a *date type* custom field, so the start of day will be considered in the comparison.

Roger B. created issue - 24/Feb/2025 7:15 PM