Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add_worklog doesn't respect the "user" argument. #1181

Open
2 of 4 tasks
reformstudios opened this issue Oct 13, 2021 · 2 comments
Open
2 of 4 tasks

add_worklog doesn't respect the "user" argument. #1181

reformstudios opened this issue Oct 13, 2021 · 2 comments
Labels
bug good first issue New contributors welcome !

Comments

@reformstudios
Copy link

Bug summary

As noted in the code, there's a bug where the add_worklog method only creates a worklog for the currently logged in user (eg an api user) rather than a user specified by name or id. This renders api updates of worklogs rather broken.

Is there an existing issue for this?

  • I have searched the existing issues

Jira Instance type

Jira Cloud (Hosted by Atlassian)

Jira instance version

No response

jira-python version

main

Python Interpreter version

2.7, 3.8

Which operating systems have you used?

  • Linux
  • macOS
  • Windows

Reproduction steps

# 1. Given a Jira client instance
jira: JIRA_
# 2. When I call the function with argument x
jira.add_worklog(user=some_user_id)
# 3.
A worklog is created but assigned to the api user, not the user supplied as an argument in the call.

Stack trace

n/a

Expected behaviour

Worklogs should be given the "Author" defined in the add_worklog "user" argument.

Additional Context

No response

@guodh1
Copy link

guodh1 commented Dec 2, 2021

Yes, I also encountered this problem. Is there any way to deal with it

@adehad adehad added bug good first issue New contributors welcome ! labels Aug 6, 2022
@jeffreywu1996
Copy link

jeffreywu1996 commented Mar 15, 2023

same for me, any workarounds?

Issue seems acknowledged on source code:

# report bug to Atlassian: author and updateAuthor parameters are ignored.

edit: Seems like this parameter is not available on official v2 API

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug good first issue New contributors welcome !
Projects
None yet
Development

No branches or pull requests

4 participants