Creator of issue taking the administrator name not the one who raised it

[Zaldy Parian]

Hi all,

I got a very weird issue and I could not find out what causing it.

So we have TestRail and Jira integrated. It's working fine from the past until I created a new project in Jira for defect (bug) tracking.

The tester will do the usual "Push" from TestRail to raise a defect in Jira. However, when the defect is created in Jira, the Reporter field would have my name or another administrator's name. In other words, the Reporter name should carry the name of the user who raised the defect and not my name. And I know that Reporter field is a system field and read-only. As such, I could not even edit/change it.

Does anyone know why this is happening? Or how can I prevent it from happening again?

Regards,

Zaldy

[Zaldy Parian · Accepted solution]

I believe I found the root cause of the issue.

Some of our users failed to generate their own API token to integrate TestRail and Jira. When users without API token raise a defect using Push link in TestRail, the system takes the administration's API Token (which is my token) and thereby having the Reporter field of the issue with my name on it.

The fix it to get all users of TestRail and Jira to generate their own API token for authentication.

I hope this could help other Jira administrators having similar issue.

Regards,

Zaldy

[Sachin]

Nice find @Zaldy Parian !

[Sachin]

Hello @Zaldy Parian , can you check

- if there is any automation rule in place (Project settings --> Automation )
- if there is any postfunction configured on your workflow
- if the issues you are referring to has any components set, which would assign ticket to a component lead or project lead

[Zaldy Parian]

Hi Sachin,

Thanks for your prompt reply.

- no project automation

- it only have the default post function after creation, which are:

1. Creates the issue originally.
2. Move up Move down Edit DeleteRe-index an issue to keep indexes in sync with the database.
3. Move up Move down Edit DeleteFire a Issue Created event that can be processed by the listeners.

- there is no configured components. I created the project from scratch, modify the workflow a bit to suit the project.

[Sachin]

Thank you for that info Zaldy, I am not familiar with TestRail but I would check for anything that is automation related on your instance. Also, do you see anything weird in your issue history?

[Zaldy Parian]

Hi Sachin,

There's nothing unusual in the History tab. Only unusual is that the issue created last night again have my name on it as creator/Reporter.