nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Reporter and creator is different

Mohammed Rashid2

Hi,

A Customer has created a ticket and mentioned the reporter of the ticket to different user.

Is there any way to find out which user has logged in and created the ticket.

Please let me know if you need any more info.

Regards,

Rash

Accepted answers

Nic Brough -Adaptavist-

Not really. When you create an issue, Jira creates it with whatever reporter the user enters. That's it, the first time the issue exists as an entity, it has the reporter on it. If the user changed it from themselves to someone else, you're a bit stuck, because the person doing the typing doesn't actually commit that into the issue.

There's two easy workarounds to prevent the loss of information, but neither will help you for older issues:

1. Use a post-function to set a custom field (I call it "creator") to %Currentuser% on the create transition

2. Remove reporter from the "create issue" screen, so it always logs the current person (and if they need to change it later, leave it on the edit screen)

You can try to work it out from watchers and project activity etc, but that's not always clean enough.

All comments

Vidic Florjan

Do you have system configured to automaticaly add "real reporter" as a watcher?

Nic Brough -Adaptavist-

There's two easy workarounds to prevent the loss of information, but neither will help you for older issues:

1. Use a post-function to set a custom field (I call it "creator") to %Currentuser% on the create transition

2. Remove reporter from the "create issue" screen, so it always logs the current person (and if they need to change it later, leave it on the edit screen)

You can try to work it out from watchers and project activity etc, but that's not always clean enough.

Mohammed Rashid2

Yes.. How will we find the watchersof an issues

Mohammed Rashid2

Yes.. This can be done for future issues...

Mohammed Rashid2

Yes..but how do we find the watchers of an issue?

AmandaA

Also, there is an Improvement ticket regarding to this feature.

https://jira.atlassian.com/browse/JRA-4618

You can vote it for furture Implementation.

Vidic Florjan

User is automaticaly added to the watchers list (click on the number of watchers to see the Watchers list).

Sometimes (if jira is configured to send notifications to watchers on creation and if there is no other postfunction to add additional users to watchers list on create transition) is possible to find the user in log file of the mail server. Search to whom of the watchers email has been sent (with Issue created event).

Trent Larson

Unfortunately, solution #2 still causes confusion in the Activity section: even after creating an issue with myself as the reporter by default, if I change to another reporter then that new person suddenly shows in the Activity section as the person who created it.

Nic Brough -Adaptavist-

Yes, that's correct behaviour, given that Jira doesn't log creator correctly. I prefer solution 1 as it's perfectly clear

Kalen Brown

https://jira.atlassian.com/browse/JRA-4618 is closed and they have done something due to this problem.

Konrad Siejka

Next workaround. Use Script runner plugin:

Add Scripted field

import com.atlassian.jira.user.ApplicationUsers;
import com.atlassian.jira.user.ApplicationUser;
ApplicationUser CreatorUsr = ApplicationUsers.from(issue.getCreator());
return CreatorUsr

choose User picker (single user) template

Nic Brough -Adaptavist-

You don't need any workarounds any more - Atlassian fixed it a couple of years back.