Uploaded image for project: 'Jira Align'
  1. Jira Align
  2. JIRAALIGN-5369

Custom team mappings are being copied automatically when toggling the project dropdown to a project without existing mappings

    XMLWordPrintable

Details

    • 2
    • Severity 2 - Major
    • No

    Description

      Issue Summary

      Custom team mappings are being copied automatically when toggling the project dropdown to a project without existing mappings, in Jira Setttings → Manage Custom Fields → Sync Jira Team Values with Jira Align Teams.

      The new mapping entries clutter up DB and API, and have potential to cause issues syncing custom teams because the project-specific mappings don't get updated when the default mappings are changed.

      Steps to Reproduce

      1. Go to Jira Setttings → Manage Custom Fields → Sync Jira Team Values with Jira Align Teams
      2. Have/create some team mappings on the default page without selecting any project (save if create new ones)
      3. Optionally GET ALL team mappings using API (/align/api/2/Connectors/{connectorId}/customFields/teams)
        • and filter in your script by projectKey == null to see those mappings
      4. Select some project in Jira where you know you haven't created any mappings
        • it shouldn't come up in the API when filtering by projectKey
      5. Select that project in the UI dropdown, do not click save, all we do is load that page
      6. Now check the API and filter by that projectKey, you will see the new mappings being added
      7. Deleting some mappings from the default page doesn't propagate, the old mappings remain in the project-specific view


      Note: in this picture this project should not have any mappings, they are newly added when navigating to it.

      Expected Results

      It is expected that selecting a Jira project in the custom mapping dropdown will return an empty list unless it was configured by a user previously. It is expected that the new mappings will not be added unless the Update button is pressed.

      Actual Results

      Mappings are copied automatically, they clutter up DB and API, and have potential to cause issues because the project-specific mappings don't get updated when the default mappings are changed.

      Workaround

      Currently, there is no known workaround for this behavior. A workaround will be added here when available.

      If you're only using the default mappings, avoid selecting a Jira project in the custom team mapping menu.

      Attachments

        Issue Links

          Activity

            People

              fea1a6ef3355 Yannick Genin
              c7f2a2ebc58e Kirill Duplyakin
              Votes:
              3 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Backbone Issue Sync