Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Product Q&A
See all
Community resources
Top groups
Explore all groups
Community resources
Learn
Community resources
Events
Community resources

Migrating creation of worklogs from v3 to v4

CHAPIT Nicolas
CHAPIT Nicolas
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Get involved
January 28, 2025

Hi there!

So since 2025, we can't use the apiv3 to create worklogs. We have to migrate to v4.
But now, to create a worklog, we can't pass the issueKey but the issueId. So to get it a simple query on v3 and that's it.

But, before migrating to v4, I was using the api token and it was working fine. After reading the v3 documentation, it seems that the api token is not used and I would need to use oauth instead. Is that right?

I changed a bit my code to get the issueId but I get 403 forbidden every time...

Answer
Watch
Like Be the first to like this
183 views

1 answer

1 accepted

Suggest an answer

Log in or Sign up to answer
0 votes
Answer accepted
CHAPIT Nicolas
CHAPIT Nicolas
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Get involved
January 28, 2025

Well nevermind....
I was using tempo api token instead jira's...

Seems to work properly now.

Sorry for the post...

Reply
groups-icon
App Central
TAGS
AUG Leaders

Atlassian Community Events

    See all events