XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • Plans - Timeline
    • None
    • 6
    • 20
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

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

      Hi, I can understand why the Team field is locked to stop someone deleting it, but it restricts how it can be used.
      Firstly, I can't setup any value, unless I go to Portfolio and set them up first. Common practise when you have multiple teams is to have a Teams common field which you then assign Stories to. I can't do this with the Portfolio field.
      Secondly in an enterprise there will be a lot of Teams, and I don't really want the entire list available to all project. I usually setup a field context applied to projects which then has options on which are the available teams who can work on those projects. That way there is a restricted list available in each project and its very difficult to choose an incorrect team.

              Unassigned Unassigned
              31e6ff6af09c Nigel Budd (CV)
              Votes:
              60 Vote for this issue
              Watchers:
              48 Start watching this issue

                Created:
                Updated: