• 60
    • 10
    • 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 Product Owner

      I want to assign stories to a Scrum Team from either Portfolio or JIRA and see it represented in both Portfolio and JIRA

      So that I can see the same changes in both tools, depending on who I am talking to and in what context.


      The following is currently possible with the Portfolio Team field:

      • you can create Shared teams in Portfolio and assign an issue to a team
      • It is also possible to Edit an issue in JIRA and change the Team field to one of the shared team.
      • It appears in the People section of the Browse Issue view.
      • You can add the Team field in the Card Layout on a specific board

      Therefore the functionality is almost there but the following is not possible:

      • Add the Team field in the Issue Detail View (right pane when you click on an issue in the board)
      • Chose the Team field in gadgets in the Dashboards
      • Filter board content by Team when using the Agile Board Filter plugin
      • Create filters using the Team full names (it substitutes values with IDs) although that's a minor inconvenience.

      My main issues are the Issue Detail View and the Dashboard.

       

            [JSWSERVER-25248] Portfolio Team field should be a fully supported JIRA field

            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

            Divya TV added a comment -

            The field Team- The Portfolio for Jira team that will work on this issue. – Can be shown on edit issue screen - when you pick All the fields.

            However when you pick Custom option on edit issue screen, this field doesn't appear in the list.

            Divya TV added a comment - The field Team- The Portfolio for Jira team that will work on this issue. – Can be shown on edit issue screen - when you pick All the fields. However when you pick Custom option on edit issue screen, this field doesn't appear in the list.

            SConlee added a comment -

            Agree with other voters, Admins need more control over form, fit and function of the Advanced Roadmaps "Team" field in Jira for it to be a reliable value add.  Specific examples include:

            *  Ability to display in Issue Detail view (as described by others)
            *  Ability to configure field contexts and other field specific workflow configuration 
            *  Better API/scripting enablement (right now - it is clunky to script any automation and as others have mentioned - it adds to a negative perception of the tool)

            Additionally - Advanced Roadmaps Shared Team management could really use some attention but I will post that in an more appropriate thread.

            SConlee added a comment - Agree with other voters, Admins need more control over form, fit and function of the Advanced Roadmaps "Team" field in Jira for it to be a reliable value add.  Specific examples include: *  Ability to display in Issue Detail view (as described by others) *  Ability to configure field contexts and other field specific workflow configuration  *  Better API/scripting enablement (right now - it is clunky to script any automation and as others have mentioned - it adds to a negative perception of the tool) Additionally - Advanced Roadmaps Shared Team management could really use some attention but I will post that in an more appropriate thread.

            This issue blocks us from using Plans. Is there an update on this @attlassian ?

            Automation does not work to copy Team field to Scrum team or visa versa.

            Sunita Nandy added a comment - This issue blocks us from using Plans. Is there an update on this @attlassian ? Automation does not work to copy Team field to Scrum team or visa versa.

            Agreed! How is this not already a feature? Seems like a straightforward request, with obvious benefits. Please add this !

            Matthew Davison added a comment - Agreed! How is this not already a feature? Seems like a straightforward request, with obvious benefits. Please add this !

            Diwakar Jagannathan added a comment - - edited

            I think for good user experience, the Team field should be in the Issue detail view. Otherwise, it becomes immediately obvious to a wide range of users viewing the screen when the work around is being done, and creates a negative perception of the tool.

            Diwakar Jagannathan added a comment - - edited I think for good user experience, the Team field should be in the Issue detail view. Otherwise, it becomes immediately obvious to a wide range of users viewing the screen when the work around is being done, and creates a negative perception of the tool.

            Apologies if this has already been mentioned, but it would also be ideal for the Portfolio Team field to be supported in Jira Project Automation and Structure. 

            • In Project Automation, Team is not a field that can be selected from the list of fields to update. Instead custom JSON must be used.
            • In Structure, the Team field can be added as a column but this column can not be used for sorting/grouping.  Instead a formula must be used to extract the Team name.

            Both are relatively minor inconveniences but, I believe, it is another barrier to entry for less skilled Jira users which prevents them from realizing the full value of add-ons like Portfolio.  Many users want to be self-sufficient and will not ask for help from power users so, they will try to find workarounds or, worse, abandon the use of the tools/add-ons.

            Jordan Janis added a comment - Apologies if this has already been mentioned, but it would also be ideal for the Portfolio Team field to be supported in Jira Project Automation and Structure.  In Project Automation, Team is not a field that can be selected from the list of fields to update. Instead custom JSON must be used. In Structure, the Team field can be added as a column but this column can not be used for sorting/grouping.  Instead a formula must be used to extract the Team name. Both are relatively minor inconveniences but, I believe, it is another barrier to entry for less skilled Jira users which prevents them from realizing the full value of add-ons like Portfolio.  Many users want to be self-sufficient and will not ask for help from power users so, they will try to find workarounds or, worse, abandon the use of the tools/add-ons.

            It should also be possible to:

            • Select Team field options in Basic search in the issue navigator
            • Set field as required in the Field configuration. See JPOSERVER-2328 for more info. 

            Björn Gullander added a comment - It should also be possible to: Select Team field options in Basic search in the issue navigator Set field as required in the Field configuration. See  JPOSERVER-2328  for more info. 

            Dave added a comment -

            omar.rashid - it's still not possible to:

            • Add the Team field in the Issue Detail View (i.e. in the right pane when you click on an issue in the board) 
            • Create filters using the Team full names (it substitutes values with IDs) 

            jand2 - it should be possible to sorting and ordering by the Team field now works following the release of Portfolio 3.10.0. Can you confirm you've tested that version please?

            Dave added a comment - omar.rashid  - it's still not possible to: Add the Team field in the Issue Detail View (i.e. in the right pane when you click on an issue in the board)  Create filters using the Team full names (it substitutes values with IDs)  jand2  - it should be possible to sorting and ordering by the Team field now works following the release of Portfolio 3.10.0. Can you confirm you've tested that version please?

            Jan Denny added a comment -

            One scenario: The Portfolio Team field displays on a Jira issue list (generated by JQL), but you cannot sort by the Team field by either clicking the field heading or adding "ORDER BY Team" to the JQL statement.

            Jan Denny added a comment - One scenario: The Portfolio Team field displays on a Jira issue list (generated by JQL), but you cannot sort by the Team field by either clicking the field heading or adding "ORDER BY Team" to the JQL statement.

              Unassigned Unassigned
              26a885aad10d Johann Moro
              Votes:
              274 Vote for this issue
              Watchers:
              159 Start watching this issue

                Created:
                Updated: