So stupid, this feature does not exist.....Not rocket science to add within Plans - The code is already there

Have given up on Atlassian for fixing these things........+3 years for something that takes 3 hours to develop!

My Workaround:

1. Create new custom field(User Picker - Single) called "Requestor" or similar(Need a Jira Admin here )
2. Add "Requestor" field to your screens
3. Create Automation rule that sets the Requester = Reporter whenever the Reporter field is changed(Trigger)
4. Add the "Requestor" custom field to your Advanced Roadmaps plan under "Manage custom fields"
5. Add "Requestor" as column to your Advanced Roadmaps plan under Fields

IMPORTANT NOTE:  Highly consider scoping this to only the projects/teams, that have these requirements - If you do this globally you will not only flood EVERY issue with duplicate data - but you will also trigger the automation for Jira at EVERY creation of an issue(not best practice compared to actual usage).

Hi, 

It would be a really useful feature for prioritizing within the plan.

I kindly suggest to consider it.

Thank you very much.

I definitely need  the ability to pull in reporter to my Plans too!

Without this possibility i am not able to filter and sort of my reporters.

Please DO it!

Thank you in advance!

Dear all,

I would like to inform you that this issue in the project JPOSERVER is being migrated to the new project JSWSERVER. Your votes and comments will remain unchanged.
Our team at Atlassian will continue to monitor this issue for further updates, so please feel free to share your thoughts or feedback in the comments.

Sincerely,
Aakrity Tibrewal
Jira DC

It should be available on Data centre version as well.

My company just migrated to Jira Cloud.  Reporter is available now.  

+1 need this

Really need some attention to this. Ask is very logical and seems missed during initial feature development. And Implementation should be straightforward. Can someone please take it further or provide feedback at least?

Tried to make a plan and needed this field in the overview. Because I'm preparing a meeting with a group of the 'reporters'. So that would be a nice way to sort all the issues in the plan.

Just received this request today.  We definitely need the ability to pull in reporter to Plans!

Adding the Reporter Field would be nice and a benefit to the reports that I am trying to pull into Roadmaps, It would help with prioritization as well as identifying teams of a very large organization. I vote for this as well. 

We really need to be able to see the reporter in the plan view!

When planning, it's often necessary to engage with the requestor, known as reporter in Jira, to discuss changes, timing and get clarifications if required.  Also, there are times when the reporter moves on, Jira Plan's bulk update function could be very helpful in reassigning the work to another reporter.  That being said, something needs to be done to make Jira Plan better handle pulling in multiple Jira projects, which is why Jira plan is needed in the first place.  Limiting data is not the best solution.  

Really need to see "Reporter" in advanced dashboard!

Apparently 8 fields is the limit now !!

Everything else in group by is not supported.

Aye aye! Yes to all above! Give us the reporter!

We can add Custom Fields but cannot add Reporter.... Disappointing.

Just a question: why??

I thought this would be a very very basic feature out of the box.

yes i vote for this as well. First if you go with the filter then you can not pick the sprint fields because for you have to assign a board as a source.

if you assign a board along side with the board then that is consider as an OR not AND (its ignores the filter and all JIRAS shows up).

then you have select the board and then apply the filter on the plan.

even after all:

1. this Reporter field is not visible for filter.
2. I can't group by Customer (customer field) or Reporter
3. .. and so on so on ..

is there a reason of blocking fields to be available for filtering or group by ..? 

I would like to vote for this as well, since its too difficult to filters many data, and this is one of the field from Jira, which can be picked up immediately. 

I want his too. I'm currently managing a project where multiple people open tasks and I need to solve duplicates, enlight people about their mistakes, callout responsibilities, etc. Not having this is making my life harder, for no reason, since this field is native to Jira. Just add all native fields to advanced roadmaps and let people decide what to add to their plans.

can't you just create a new filter (filtering for whatever you want), and set this filter as the single source for the plan? worked for me!

Darn.  I don't get those. Are you on Jira Cloud?  We are. In place of where you see Issue Sources I see Sprints, Projects, and Issue Types. Mine is 

Releases

Teams

Assignees

Sprints 

Projects

Issue types

Components

etc....

Thanks anyway.  I appreciate the help.

Hi Carolyn... here's what it looks like for me...  It seems to do the trick..

Oops.. it wouldnt accept my picture...

But I see filters, with the options of 

Releases

Teams 

Assignees

Issue Sources

     - boards
     -filters

Components

etc.

Good luck!!

Thanks Jackie. I created 2 filters to test it.  Added them to Issue Sources, but they do not show up in the list of filters to choose from.  I wonder if it has something to do with our setup of Jira.  

@carolyn.1.jones

There are 2 different filters in play here

1) the filters you create when searching for issues
2) the filter inside the plan that gives you a finite list of items you can filter on.  One of those is NOT the reporter, one is "Issue Sources"

Create filters where you manage filters in Jira or "search for issues".  the filters can be  "reporter = jklass"  or " reporter = carolyn.jones"  or "reporter = currentuser()"- you can make one for each of the reporters you wish to filter on in your plan.

Then .. go to your plan configuration.  Clear on the gear at the top to configure your plan.  
Go To "Issue Sources"
You likely have a board or filter or a project as your issues sources
Now You can add more sources.  add in your newly created filters.

Now when you are looking at your plan and the filters within the plan - you can choose to filter by "Issue Sources".  
Choose one of the filters you have added to your plan. 

It should work for you.

@Jackie can you share more about the filter?  I have a filter for the work on a roadmap, with Reporter in the output column.  But that didn't change anything on my roadmap. The field Reporter is not available to add in the roadmap.

Thanks.

essential feature +1

essential feature!

This is obviously needed..

Thanks for the workaround Jackie! I also managed to add to the Issue Sources a filter with "reporter = currentUser()", so anyone viewing it can see their reported issues.

i have somewhat of a work around for this (only if you dont have a lot of reporters).  If you create filters for the different reporters and add those filters as issues sources to your plan, you can filter on the different issue sources (created filters).   i.e. if you plan is base off of all issues for a project, and you add filter issue sources to your plan (filters where reporter = jane.doe; reporter = john.smith; reporter = bruce.wayne)  - you can filter on the issue source.   

We also need the Reporter Field.

This is a must for us to use JIRA! Please implement it.

We also need the Reporter Field.

I thought this should be the default function, for example, as a Project Manager, I want to see all tasks I created and to make the roadmap plan.

Obviously echoing all comments above.  I know this is a lot of hoops to jump through but couldn't I define a new custom field in Jira (like AR_Reporter) and then use a Jira Automated function to populate it from the current Reporter field and then bring that new custom field into roadmaps?  

Sounds like a bug. As if you would have exposed "Start Date" but not "To Date". Would be good to get it added soon.

Thanks

Really need this as right now we can't even filter by any User Picker fields. Really useful especially if the Plan is showing a long list of issues. 

Echoing the other comments. Inclusion of 'Reporter' seems a fairly fundamental requirement please. Thanks.

Agreed, I find it strange that assignee is included, when use cases for the roadmap are more likely to involve external stakeholders who want to see where their reported stories/tasks are on the roadmap.

Us Too!  I work with a group of BAs and PMs, and reviewing our plan would be significantly more usable if we could see and filter by Reporter.

Consider the interest generated!
I just had a usecase today for this. Any idea when you might be able to get this in the roadmap? Thanks

Same here. We would like to use this feature with our CFO, but she wants to see reporter...

This is pretty critical to our use of Advanced Roadmaps as we create plans for the team. We also want a reporter to be able to filter to only issues they are reporting.

Any update?

As PO I am using Advanced roadmap during Groomings. While I prepare (tickets) for a grooming session I often have to contact the developer created the ticket to complete its description, labeling etc.

Currently the following are not possible in Roadmaps:

1.  See the reporter of a ticket
2. Filter tickets by reporter
3. Colour tickets by reporters

Please pipe this info from Jira to Roadmaps.

Cheers

Could you please let us know when this filed can be visible on Advanced Roadmap?