Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-39509

Create date between should also consider the end date

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • JQL
    • 1
    • 5
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      When searching in JQL using the "Create Date Between" filter, JIRA is considering only the Start date, not the End date. It considers one day before the end date.

      Steps to replicate:

      Example 1:
      • Create one issue today (let's say today is Aug 9th);
      • Create a JQL (basic or advanced, doesn't matter) to search issues from Aug 7th to Aug 9th (created >= 2014-08-07 AND created <= 2014-08-09);
      • The issue will not appear in the results.
      Example 2:
      • Create one issue today (let's say today is Aug 9th);
      • Create a JQL (basic or advanced, doesn't matter) to search issues from Aug 7th to Aug 10th (created >= 2014-08-07 AND created <= 2014-08-10);
      • The issue will appear in the results.
      Example 3:
      • Create one issue today (let's say today is Aug 9th);
      • Create a JQL (basic or advanced, doesn't matter) to search issues from Aug 9th to Aug 10th (created >= 2014-08-09 AND created <= 2014-08-10);
      • The issue will appear in the results.

      Expected behavior:

      This should work in any of the scenarios above, including up to 23:59 on the date created. According to bugmaster in JRA-39465:

      created <= 2014-08-09 gets translated to 2014-08-09 at 00:00:00 (midnight) so any issues created after midnight will not be included.

      Recommended behavior

      Include through 23:59:59 that day. This seems more intuitive.

      Original text:

      I saw this created as a bug on JRA-39645 and as it was confirmed as a "by design" behavior, I think we could improve the code to make this more intuitive for our users.

      So the expected new behavior should be like this:

      • Create one issue today (12th August)
      • Create a JQL (basic or advanced, doesn't matter) to search issues from Aug 7th to Aug 12th (_created >= 2014-08-07 AND created <= 2014-08-12);
      • This issue should appear here.

      I really think that this is pretty much more intuitive as the customer will use the last day that it needs to see its issues.

      Best regards.
      Diego Zarpelon
      Atlassian JIRA Support Engineer

            [JRASERVER-39509] Create date between should also consider the end date

            George de Bouter added a comment -

            I have experienced a problem between a date selection in the Jira core, and the Timesheet Report. To select August, for example, in the core of Jira this needs to be done as:
            Start: August 1
            End: September 1

            while in the Timsheet Report, this needs to be:
            Start: August 1
            End August 31

            George de Bouter added a comment - I have experienced a problem between a date selection in the Jira core, and the Timesheet Report. To select August, for example, in the core of Jira this needs to be done as: Start: August 1 End: September 1 while in the Timsheet Report, this needs to be: Start: August 1 End August 31

            Rob Horan added a comment -

            This is a MAJOR bug that needs to be patched. My monthly reports for the past year have all been incorrect due to this issue, with issues from the last day of the month being omitted from reports. All those I have spoken to about this issue have the same feelings about how this should work.

            Rob Horan added a comment - This is a MAJOR bug that needs to be patched. My monthly reports for the past year have all been incorrect due to this issue, with issues from the last day of the month being omitted from reports. All those I have spoken to about this issue have the same feelings about how this should work.

            Sten Sundelin added a comment -

            I agree that the current functionality is counter-intuitive in the Basic search window using 'between' and calendar picker. I would certainly expect both the start and end dates to be 'all-inclusive', i.e. timestamp of day should have no impact (as I can't seem to enter it).

            Whether to include the midnight timestamps on each edge can be discussed, but as long as it is documented how it works in that regard, it matters little to me. (When converting to Advanced, I do suggest adding "23:59:59" to the end date (and keep as '<=') or add 1 to the date portion (and make it '<'.)

            Sten Sundelin added a comment - I agree that the current functionality is counter-intuitive in the Basic search window using 'between' and calendar picker. I would certainly expect both the start and end dates to be 'all-inclusive' , i.e. timestamp of day should have no impact (as I can't seem to enter it). Whether to include the midnight timestamps on each edge can be discussed, but as long as it is documented how it works in that regard, it matters little to me. (When converting to Advanced, I do suggest adding "23:59:59" to the end date (and keep as '<=') or add 1 to the date portion (and make it '<'.)

            Bert Ciccone added a comment -

            Hello,
            I am not sure how to reply to JRA-39465 because it is now marked Resolved and I can no longer comment, so I will reply here.
            The rationale for Oswaldo Hernandez [Atlassian] Bugmaster closing the issue this is:
            "This might not be intuitive but it's by design as in the first scenario, created <= 2014-08-09 gets translated to 2014-08-09 at 00:00:00 (midnight) so any issues created after midnight will not be included."
            Sorry to say, but I don't believe this analysis of the problem is correct. The defect report is not regarding Jira's date system, which is fine. It is regarding the user interface for the "Between" feature and that user interface does not make sense. The results of using the "Between" feature match one date of the range inclusively and the other date non-inclusively. No user will expect "Between" to mean that. This forces the user to enter tomorrow's date as the second date to see issues created today. (Typically, a UI will PREVENT the user from entering a future date such as "tomorrow" for a feature such as this.)
            The "Between" feature should not use the date directly input from the user; it should take that input date (today) and add one day to the date (resulting in tomorrow at 12:00 am) so that both input dates will be inclusive, and therefore returning issues created today.
            Another solution would be to change the user interface to read: "Starting from: <date>, up to but not including: <date>", if adding one day to the last date is for some reason not acceptable.
            Alternatively, it could subtract one day from the first date so that both dates are non-inclusive (but this is not the preferred solution).
            Thank you,
            Bert Ciccone

            Bert Ciccone added a comment - Hello, I am not sure how to reply to JRA-39465 because it is now marked Resolved and I can no longer comment, so I will reply here. The rationale for Oswaldo Hernandez [Atlassian] Bugmaster closing the issue this is: "This might not be intuitive but it's by design as in the first scenario, created <= 2014-08-09 gets translated to 2014-08-09 at 00:00:00 (midnight) so any issues created after midnight will not be included." Sorry to say, but I don't believe this analysis of the problem is correct. The defect report is not regarding Jira's date system, which is fine. It is regarding the user interface for the "Between" feature and that user interface does not make sense. The results of using the "Between" feature match one date of the range inclusively and the other date non-inclusively. No user will expect "Between" to mean that. This forces the user to enter tomorrow's date as the second date to see issues created today. (Typically, a UI will PREVENT the user from entering a future date such as "tomorrow" for a feature such as this.) The "Between" feature should not use the date directly input from the user; it should take that input date (today) and add one day to the date (resulting in tomorrow at 12:00 am) so that both input dates will be inclusive, and therefore returning issues created today. Another solution would be to change the user interface to read: "Starting from: <date>, up to but not including: <date>", if adding one day to the last date is for some reason not acceptable. Alternatively, it could subtract one day from the first date so that both dates are non-inclusive (but this is not the preferred solution). Thank you, Bert Ciccone

              Unassigned Unassigned
              dzarpelon Diego Zarpelon (Inactive)
              Votes:
              28 Vote for this issue
              Watchers:
              20 Start watching this issue

                Created:
                Updated: