Created a small application for creating worklogs using Jira rest api V2.
Case:
1. POST create worklog => 201
2. Get issue by id => see newly create worklog
3. Updated Jira UI
Expected: see created worklog
Actual: there is no worklog
Which jira-server security configuration are responsible for this feature ?
Welcome to the Atlassian Community !!
When you are running the REST API for worklog, you should get 200 for successful hit.
201 - means its failing. Can try to run that on POSTMAN tool and check what output you are getting.
Accept answer if it helps
Thanks,
Sachin
@Sachin Dhamale Hello!
Honestly, i don't remember the code. Used curl to post worklog. But 100% it has been created.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
How do you sure its been created if you are not able to see it on issue
Thanks,
Sachin
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
After POST creation curl request I send GET worklog curl request and see a new one there.
I saw in google, that it can be server security/visibility configurations. But haven't found any details about that
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.