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

Updating the Team through a Plan fail if there are multiple Team custom fields with restricted context

XMLWordPrintable

      Issue Summary

      If having more than one Team type custom field, they all have to have the project's context (or global) in order to be able to update the Team through a Plan.

      Steps to Reproduce

      1. Create another Team type custom field "My Team"
      2. Reduce the scope of "My Team" to "Project A"
      3. Try to update the Team field through a "Project B" Plan
      4. See that Plans reports the updates were successful but the Team reloads empty and Jira's not updated
      5. Updating the Team through Jira (with shared teams) results in the Plan displaying the Team

      Expected Results

      Advanced Roadmaps should update just the Team fields that are in the context of the project.

      Actual Results

      Advanced Roadmaps fails to update the Team field if there's any other Team field outside the project's scope.

      Workaround

      • Don't have ay other Team type custom field aside from the Locked default one
        or
      • Make all Team custom fields global context. Advanced roadmaps will update all of them everytime the Team is updated.

          Form Name

            [JSWSERVER-25239] Updating the Team through a Plan fail if there are multiple Team custom fields with restricted context

            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

            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

              Unassigned Unassigned
              rmartinez3@atlassian.com Rodrigo Martinez
              Affected customers:
              3 This affects my team
              Watchers:
              7 Start watching this issue

                Created:
                Updated: