The different between Project Lead, Assignee, and Reporter?

[Tracy Logan]

I'd like to know the difference between Project Lead, Assignee, and Reporter? Like how does each work in the system as far as notifications or whatever. I just want to make sure I'm using these three fields correctly.

[Michael Partyka]

Reporter: person who created issue

Assignne: person who is responsible for issue

Project Lead: Person who is responsible for project, usually he is also a default assignee if user will not select another.

[Florian Rock]

Reporter IS NOT who created the issue.. its automatic preselected but can be changed... Think about an Service Desk and an agent is creating a ticket for someone who is calling.. Then the creator is the agent and reporter is the person who is calling...

In the change history you can see the "real" creator. Please don't spread the wrong Information that reporter = creator. Btw JIRA introduced (in search) a own field for "creator"... 

[Mike Sorensen]

For Jira, the id of the user creating the Jira issue is initially put into the Reporter field for that new issue. 

[Florian Rock]

@Mike Sorensen  thats not  really true ;) the reporter field can be on the create screen and can be set differently (which is in service desk setups very typical).

The creator can be seen in the history tab in your issue.. and it can be diffrent from the reporter.

[Nic Brough -Adaptavist-]

It used to be true in older versions of Jira, up until the creator field was added as a separate record.  The reporter has always been changeable (if you have the permission), with the intention to allow "report on behalf of".  Reporter defaults to current user, but you can change it.

The creator field was asked for because of that ability - people needed to know who entered the issue AND who was reporting the problem, when those two people are different!

[Florian Rock]

"it used to be true"  - "Reporter defaults to current user, but you can change it."

so it was never true :D even bevor the creator field was added the reporter  could be changed.. Even since jira 3..

and thats exactly what i wrote?!  

[Nic Brough -Adaptavist-]

Eh?

"For Jira, the id of the user creating the Jira issue is initially put into the Reporter field for that new issue. "

is the same as

"Reporter defaults to current user,"

So it used to be true.

[Florian Rock]

If i change the repoter in my create screen its not initial put in the reporter field.

"For Jira, the id of the user creating the Jira issue is initially put into the Reporter field for that new issue." 

is writen that the new issue (which only exist after a creation ;)) has in any case the creator id set in the repoter field.. which is not true

"Reporter defaults to current user," explains it right.

And still thats exactly what i wrote thats why i dont understand why it need to be corrected.

[GabrielleJ]

JIRA Project Lead is usually an account that belongs to a JIRA Project that can be a default assignee for that project. It does not have any special permissions other than that.

Reference: https://confluence.atlassian.com/jira/managing-project-roles-185729625.html

JIRA Assignee is typically the account that is working on the JIRA issue. 

JIRA Reporter is usually auto-poppulated for whoever created the JIRA issue.

JIRA Notifications (emails) are usually controlled on whatever JIRA Notification schemes it is configured to use.

Reference: https://confluence.atlassian.com/jira/configuring-email-notifications-185729575.html

[Tracy Logan]

So our team lead said he wants to be on every project to get comment notifications. I assume that would be the Project Lead. Then when the project given to someone to work on, that is the Assignee? But then the Reporter could be the same as the Assignee, right?

[Nic Brough -Adaptavist-]

Project lead, reporter and assignee are effectively fields - they point at a user.  They could all be the same person, could all be different, and during the lifecycle of an issue, the assignee is often changed (reporter can be changed, but it usually doesn't, and project lead has nothing to do with the issues directly)

You need to go over the notification schemes, and they can vary between project, so your "team lead" does not necessarily map on to the idea of a "project lead" as those could be different.

You probably want to think about adding something to the notifications to catch comments for him in an ad-hoc way.  A simple but flexible way to do it would be to create a new role called something like "comment watcher", then add "comments: notify comment watcher role" into all the notification schemes, then you can add whoever you want to the role in each project (including your team lead)

[GabrielleJ]

As mentioned, notifications are controlled by the notification scheme. If your team lead wants to receive notifications for all, he/she should be added on the notification scheme's recipient. You can also opt to add your team lead to specific roles which is also configured to receive emails based on the permission scheme again.

The Assignee and the Reporter can be the same if they reported an issue they wanted to work on. There are no limitations. 

[mike]

@Nic Brough -Adaptavist- Can more personnel fields be added?  Like could there be "assignee", "reporter", "tester", etc? Or is it limited to just the two fields?

[Nic Brough -Adaptavist-]

You can add both "user picker" and "multi-user picker" fields to issues.  As many as you would like.

[Mike Sorensen]

Is there a way to query where "assignee" is the same person as the "tester"?

[mike]

At a guess, if you had this "tester" field (which would likely be a custom field), you could do jql of

Assignee = person AND tester = person