Uploaded image for project: 'SR for Jira - Development'
  1. SR for Jira - Development
  2. SRJIRA-3215

DurationSearcher shouldn't always convert duration strings as though they were time-tracking

    Details

    • Type: Bug
    • Status: To Do (View Workflow)
    • Priority: Medium
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Scripted Fields
    • Labels:
      None
    • Critical Points:
      1

      Description

      To reproduce:

      • Set up a Duration scripted field (non-time-tracking) such that it evaluates to 2 days for some issue (call it ISSUE-123).
      • Ensure your time tracking configuration is set to 8 hours per day.
      • Perform a JQL search for issues where the scripted field's value is
        > 4d.

      Expected: ISSUE-123 is not included in the results.

      Actual: ISSUE-123 is included.

      This happens because the "4d" in the query gets indiscriminately converted in accordance with time tracking, and thus ends up representing a duration of 4*8 = 32 hours, which is less than 2 days.

      We don't do the conversion ourselves, we delegate to JqlTimetrackingDurationSupport which as the name suggests is primarily for use with time-tracking queries.

        Attachments

          Structure

            Activity

              People

              Assignee:
              Unassigned
              Reporter:
              jchoules Joanna Choules
              Votes:
              1 Vote for this issue
              Watchers:
              7 Start watching this issue

                Dates

                Created:
                Updated:

                  Structure Helper Panel