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

Import- edit features via import corrupts Theme's assignment

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Low Low
    • 11.11.0
    • 10.125.2
    • Import|Export
    • 1
    • Severity 3 - Minor
    • No

      Issue Summary

      When a feature has a theme assignment changed via import, the change does not apply to all data in the feature's details.

      Steps to Reproduce

      1. Have a Feature A
        • Linked to Epic A
          • Linked to Theme A
      2. Have a Feature B
        • Linked to Epic B
          • Linked to Theme B
      3. Edit and Export Feature B so it links to the Theme A
      4. Import the feature to apply the change

      The new hierarchy should be:

      • Theme A
        • Epic A
          • Feature A
          • Feature B
      • Theme B
        • Epic B
          • none

      Expected Results

      The data should show the updated theme across the board, including

      • Grid columns
      • Feature's details
      • Filters
      • Requirement Hierarchy
      • Export
      • etc...

      Actual Results

      1.  In Feature grid, the column for Theme shows Epic the correct new assignment,
        • Feature A = Theme A
        • Feature B = Theme A
      2.  The export function shows the correct result
        • Theme A
          • Children : Epic A + Feature A + Feature B
        • Theme B
          • Children : Epic B
      3.  The filters also apply in the same fashion
        • Feature A and B shows if filter is set to Theme A
        • Feature B shows if filter is set to Theme B
      4.  The Feature's details panel show incorrect Theme assignment
        • Feature A show like to Theme A
        • Feature B show link to Theme B
      5.  Requirement Hierarchy Shows the incorrect Assignment as well
        • Theme A
          • Epic A
            • Feature A
        • Theme B
          • Epic B
            • Feature B

      Workaround

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

              dfuller@atlassian.com Don Fuller
              0ed961e27eb4 Erwann (Inactive)
              Votes:
              2 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: