• 21
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Currently, it is not possible to include the Reporter field in an Advanced Roadmaps plan, as a Jira Administrator, we would like to be able to do so.

            [JSWSERVER-25159] Ability to include the Reporter field in a plan.

            Morten Stensgaard added a comment - - edited

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

            Morten Stensgaard added a comment - - edited 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: Create new custom field(User Picker - Single) called "Requestor" or similar(Need a Jira Admin here ) Add "Requestor" field to your screens Create Automation rule that sets the Requester = Reporter whenever the Reporter field is changed(Trigger) Add the "Requestor" custom field to your Advanced Roadmaps plan under "Manage custom fields" 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).

            Mónica added a comment -

            Hi, 

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

            I kindly suggest to consider it.

            Thank you very much.

             

            Mónica added a comment - 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!

            László Horváth added a comment - 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

            Aakrity Tibrewal added a comment - 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.

            Suneel Kumar added a comment - It should be available on Data centre version as well.

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

            Thayne Munson added a comment - My company just migrated to Jira Cloud.  Reporter is available now.  

            +1 need this

            Leon Chadwick added a comment - +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?

            Nilay Muley added a comment - 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.

            Stijn Dekker added a comment - 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.

            Need this please. Why isn't it available already? Seems odd that available fields are not accessible in Plans.

            Andrew Watson added a comment - Need this please. Why isn't it available already? Seems odd that available fields are not accessible in Plans.

              Unassigned Unassigned
              gperes@atlassian.com Gregory Peres (Inactive)
              Votes:
              232 Vote for this issue
              Watchers:
              124 Start watching this issue

                Created:
                Updated: