nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Jira API Rest - Get issue worklog using query parameter "startedAfter"

Lara Gonzalez Villanueva

Hi,

I have a problem when trying to use the API "GET rest/api/2/issue/{issueIdOrKey}/worklog" (I'm using Python). I would like to use the query parameter "startedAfter" but I'm finding some difficulties on using it, can you help me and tell me what I'm doing wrong?

The documentation says:

startedAfter
integer
The worklog start date and time, in UNIX timestamp format, after which worklogs are returned.
Format: int64

I converted the date ['2019', '12', '10', '00', '00'] to unix timestamp format using:

dt = datetime.datetime(2019, 12, 10, 00, 00)

unix_tm = (time.mktime(dt.timetuple()))

And then create the url:

https://{host}/rest/api/2/issue/{issue_key}/worklog?jql=startedAfter=1575932400

But I always get all the worklogs and not just those after that date...

I also tried:

https://{host}/rest/api/2/issue/{issue_key}/worklog?startedAfter=1575932400

Thank you so much in advance!

Lara

Accepted answers

Derek Fields _RightStar_

I tried it in my Cloud environment. It doesn't work correctly for me either. It appears that this is a bug that should be opened with Atlassian.

Derek Fields _RightStar_

I reported it to them.

All comments

Derek Fields _RightStar_

You don't specify whether you are on Cloud or Server. The APIs for each are different. I can see, though, from the documentation that you are using Cloud, which makes a different.

In any case, try using:

https://{host}/rest/api/2/issue/{issue_key}/worklog?startedAfter=1575932400

leave out the "jql=". That should return what you want.

Lara Gonzalez Villanueva

Hi Derek,

Thanks for your answer! I guess I'm using Cloud (anyway I'm not completely sure...). As I wrote on my comment I have already tried that option, without "jql=", but the response is the same, I get all the worklogs...

Derek Fields _RightStar_

Try multiplying the timestamp by 1000 to change it from seconds to milliseconds.

Lara Gonzalez Villanueva

What do you mean?

Using:

https://{host}/rest/api/2/issue/{issue_key}/worklog?startedAfter=1575932400000

Instead of:

https://{host}/rest/api/2/issue/{issue_key}/worklog?startedAfter=1575932400

I'm still getting all the worklogs...

Derek Fields _RightStar_

I tried it in my Cloud environment. It doesn't work correctly for me either. It appears that this is a bug that should be opened with Atlassian.

Lara Gonzalez Villanueva

Thank you so much Derek! Do you know how can I inform Atlassian about this bug?

Derek Fields _RightStar_

I reported it to them.

Lara Gonzalez Villanueva

Thank you Derek! Do you have any link or reference? It would be very useful to follow up the resolution!

Giuseppe D'Angelo

I am facing the same issue and I am using the postman collection provided in the "developer guideline pages" (v2 and v3).

Is it possible to have the reference link of the raised bug?

It will be very useful.

Rakesh15

Hi @Derek Fields _RightStar_ ,

Could you please let me know, how can I access JIRA Rest API by impersonating a user request. A request from user should go to a service. Service should use admin rights to access API and fetch the details.

Derek Fields _RightStar_

I don't understand the question. When you access a REST API, you need to authenticate, either through Basic authentication or by following the OAUTH flow, which requires a login sequence through a URL. The login credentials that you use will indicate the user that is making the REST call.

On server, you could write a custom REST call that would allow a user to make the call and then execute the request as an admin-privileged user. You can't do that on Cloud.

cfsfonseca

I'm having the same issue but I think the problem here is that we're using v2 of the API.

"startedAfter" seems to have only been introduced from v3..

Lara Gonzalez Villanueva

Have you tried with v3? Does it work?

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

rest

python

worklog