Bulk Submit Listing Multiple User Accounts As The Reporter

[siberian-devsky]

Summary

Hi. I notice that when I use the Python-Jira library’s client.create_issues() method that the first issue lists User A as the reporter but all subsequent entries are submitted by our Generic Jira Admin account (henceforth User B).

The library documentation makes no mention of this behavior. Is this to be expected?

Expected Behavior

I would assume that all issues submitted as part of a bulk operation would record as the reporter the user account used to initialize the Jira Client connection (see below steps to reproduce) i.e. all issues list the reporter as User A

Actual Behavior

The first issue created lists the reporter as User A but all subsequent issues list the reporter as User B

Steps to replicate:

1. Initialize the Jira Client using token_auth and my API key - User A
2. Gather data and build a list of objects to send to create_issues()
3. Send the data
4. Navigate to Jira and note that only the first of the bulk issues lists User A as the reporter. All the subsequent issues list User B

Versions

Python Interpreter: 3.10.4
jira-python: 3.1.1
OS: WIn 10 64-bit

[adehad]

Hi @jmartin111, thanks for this.

This sounds like it could be a subtlety in the Jira API.

I wonder if the reporter needs to be passed in explicitly to get this to work?

Don't suppose you could tell me if this is Jira Server or Cloud (FYI we have a bug report template here: https://github.com/pycontribs/jira/blob/main/.github/ISSUE_TEMPLATE/bug_report.yml)

[siberian-devsky]

Hi Adel, This is Jura server Best, Jeff

…

On Sat, Apr 16, 2022, 05:19 Adel Haddad ***@***.***> wrote: Hi @jmartin111 <https://github.com/jmartin111>, thanks for this. This sounds like it could be a subtlety in the Jira API. I wonder if the reporter needs to be passed in explicitly to get this to work? Don't suppose you could tell me if this is Jira Server or Cloud (FYI we have a bug report template here: ) https://github.com/pycontribs/jira/blob/main/.github/ISSUE_TEMPLATE/bug_report.yml — Reply to this email directly, view it on GitHub <#1357 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AB72CEUO4DJBMJLTAXLS3SDVFKV4FANCNFSM5TOSEIDA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[siberian-devsky]

Also, I wouldn't think that the submitter should be to be passed in. It's not even a field one can fill out when creating a ticket. Jira simply uses the current user logged in. Or, in this case, the user who initialized the API. Best, Jeff

…

On Tue, Apr 19, 2022, 10:01 Jeff Martin ***@***.***> wrote: Hi Adel, This is Jura server Best, Jeff On Sat, Apr 16, 2022, 05:19 Adel Haddad ***@***.***> wrote: > Hi @jmartin111 <https://github.com/jmartin111>, thanks for this. > > This sounds like it could be a subtlety in the Jira API. > > I wonder if the reporter needs to be passed in explicitly to get this to > work? > > Don't suppose you could tell me if this is Jira Server or Cloud (FYI we > have a bug report template here: ) > https://github.com/pycontribs/jira/blob/main/.github/ISSUE_TEMPLATE/bug_report.yml > > — > Reply to this email directly, view it on GitHub > <#1357 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AB72CEUO4DJBMJLTAXLS3SDVFKV4FANCNFSM5TOSEIDA> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> >