It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

The different between Project Lead, Assignee, and Reporter?

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.

2 answers

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.

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"... 

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

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

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?

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)

Like # people like this

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. 

@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?

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

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

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

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted in Jira

Demo Den Ep. 7: New Jira Cloud Reports

Learn how to use two new reports for next-gen projects in Jira Cloud:  Cumulative flow diagram and Sprint burndown chart. Ivan Teong, Product Manager, Jira Software, demos the Cumulative ...

261 views 1 2
Join discussion

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you