"startedAfter" parameter doesn't work for the "/rest/api/3/issue/{issueIdOrKey}/worklog" endpoint

XMLWordPrintable

    • 3
    • Minor
    • 0

      Issue Summary

      When using the endpoint "/rest/api/3/issue/{issueIdOrKey}/worklog" with a value for the "startedAfter" parameter, users will have all the entries although informing a specific date to filter the worklogs out.

      Steps to Reproduce

      1. Create an issue, and log a couple of entries, preferably with different days;
      2. Specify a date and then convert to UNIX time, keep that value;
      3. Run the following URL in your browser:
        • "curl D -u <email>:<api-token> -X GET -H "Content-Type: application/json" https://<instance>.atlassian.net/rest/api/2/issue/<issue-key>/worklog?statedAfter=<unix-time>"

      Expected Results

      Worklogs only on the specified timestamp will return.

      Actual Results

      All worklogs will return.

      Workaround

      Currently, there is no known workaround for this behavior. A workaround will be added here when available

            Assignee:
            Unassigned
            Reporter:
            Fábio W. [Atlassian]
            Votes:
            16 Vote for this issue
            Watchers:
            22 Start watching this issue

              Created:
              Updated:
              Resolved: