Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-25129

Advanced Roadmaps - Ability to add Jira fields such as the description field to the plan view

    • 13
    • 11
    • 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.

      NOTE: This suggestion is for JIRA Portfolio Server. Using JIRA Portfolio Cloud? See the corresponding suggestion.

      As a Portfolio user, it would be handy if I could add JIRA fields (assignee, reporter, description, etc..) and even custom fields to the Plan view.

          Form Name

            [JSWSERVER-25129] Advanced Roadmaps - Ability to add Jira fields such as the description field to the plan view

            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

            +1 to this request! Really missing filtering capabilities for custom fields. 

            Christina_Naumova added a comment - +1 to this request! Really missing filtering capabilities for custom fields. 

            By when is this planned for closure? We are in need of this soon.

            Shrinivas patil added a comment - By when is this planned for closure? We are in need of this soon.

            This is very important to our business. The current filtering capabilities are far too limiting. Please advance this!

            Drew Wiseman added a comment - This is very important to our business. The current filtering capabilities are far too limiting. Please advance this!

            javier sabino added a comment - - edited

            Following up on Jan Denny comment, we use labels to achieve the same, but because we are grouping several projects we want to have a custom field called program or initiative. You can filter by project, but when your portfolio is based on one single project, for example, the projects filter has no meaning and you need a custom field to be able to separate different (sub-projects?) contained in the same project.

            You can force the model and use components for that, but then you lose the main purpose of components that is the ability to identify the touch points a particular issue has on you system.

            javier sabino added a comment - - edited Following up on Jan Denny comment, we use labels to achieve the same, but because we are grouping several projects we want to have a custom field called program or initiative. You can filter by project, but when your portfolio is based on one single project, for example, the projects filter has no meaning and you need a custom field to be able to separate different (sub-projects?) contained in the same project. You can force the model and use components for that, but then you lose the main purpose of components that is the ability to identify the touch points a particular issue has on you system.

            Jan Denny added a comment - - edited

            While I can add a custom Jira field to the legacy Portfolio view, it appears that I cannot add a custom Jira field to the Portfolio Filters dropdown. The closest filtering option is the Label field, which can be used for anything - and can have widely inconsistent contents. 

            It would be hugely helpful for Portfolio to support filtering by other prebuilt or custom Jira fields.

            Jan Denny added a comment - - edited While I can add a custom Jira field to the legacy Portfolio view, it appears that I cannot add a custom Jira field to the Portfolio Filters dropdown. The closest filtering option is the Label field, which can be used for anything - and can have widely inconsistent contents.  It would be hugely helpful for Portfolio to support filtering by other prebuilt or custom Jira fields.

            Time logging related fields such as original estimate, remaining estimate, and time logged, would be great additions.

            Jason Kemp added a comment - Time logging related fields such as original estimate, remaining estimate, and time logged, would be great additions.

            I agree that it would be good to be able to customize reports with more fields (priority for instance but also potential custom fields). Any update on this task?

            Estelle Bardon added a comment - I agree that it would be good to be able to customize reports with more fields (priority for instance but also potential custom fields). Any update on this task?

            This would make cross department prioritisation so much easier using the same Priority screen shown in Portfolio rather than using boards back in JIRA

            Darren Broadhead added a comment - This would make cross department prioritisation so much easier using the same Priority screen shown in Portfolio rather than using boards back in JIRA

            We were able to accomplish this (custom and calculated fields in JIRA, showing and editable in Portfolio) on Cloud using the Abacus add-on.  I'm pretty sure it could also be done with EasyBI, ProFields, or Custom Fields add-ons.

            Bruce Cannon added a comment - We were able to accomplish this (custom and calculated fields in JIRA, showing and editable in Portfolio) on Cloud using the Abacus add-on.  I'm pretty sure it could also be done with EasyBI, ProFields, or Custom Fields add-ons.

              Unassigned Unassigned
              psouza Pedro Souza
              Votes:
              138 Vote for this issue
              Watchers:
              79 Start watching this issue

                Created:
                Updated: