We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
Uploaded image for project: 'Jira Align'
  1. Jira Align
  2. JIRAALIGN-1998

[JIRAALIGN-1998] Feature Import Resets the Developmental Step back to its initial state

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: High High
    • 10.90
    • 10.77
    • Import|Export
    • None
    • 1
    • Severity 2 - Major
    • X-Men - VH3
    • No

      Issue Summary

      When a customer Exports features to perform a bulk update on the Program Increment Field of multiple features(and nothing else), saves the changes, and then re-imports, they noticed that the Developmental Step (which was never changed) gets reset back to the first step for the state.

      Steps to Reproduce

      1. Run an export of some features from Jira Align. Ensure that the exported features also have a Developmental step set.
      2. Make a bulk change to the exported spreadsheet. For example, update only the program increment of one or more features.
      3. Re-import the data into Jira Align using More Actions -> Import from the feature grid.

      Expected Results

      The Feature should only update what the customer changed. Imports should abide by the data file. Better yet, the import process should allow an updated mode where ONLY the columns that need modification can be included or selected, to avoid unintended changes.

      Actual Results

      The Program Increment changes to the intended value, but, for the development step, the import ignores the correct value in the export file and instead reset it to the first step for the state. See audit log screenshot:

      Workaround

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

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
            Uploaded image for project: 'Jira Align'
            1. Jira Align
            2. JIRAALIGN-1998

            [JIRAALIGN-1998] Feature Import Resets the Developmental Step back to its initial state

              • Icon: Bug Bug
              • Resolution: Fixed
              • Icon: High High
              • 10.90
              • 10.77
              • Import|Export
              • None
              • 1
              • Severity 2 - Major
              • X-Men - VH3
              • No

                Issue Summary

                When a customer Exports features to perform a bulk update on the Program Increment Field of multiple features(and nothing else), saves the changes, and then re-imports, they noticed that the Developmental Step (which was never changed) gets reset back to the first step for the state.

                Steps to Reproduce

                1. Run an export of some features from Jira Align. Ensure that the exported features also have a Developmental step set.
                2. Make a bulk change to the exported spreadsheet. For example, update only the program increment of one or more features.
                3. Re-import the data into Jira Align using More Actions -> Import from the feature grid.

                Expected Results

                The Feature should only update what the customer changed. Imports should abide by the data file. Better yet, the import process should allow an updated mode where ONLY the columns that need modification can be included or selected, to avoid unintended changes.

                Actual Results

                The Program Increment changes to the intended value, but, for the development step, the import ignores the correct value in the export file and instead reset it to the first step for the state. See audit log screenshot:

                Workaround

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

                        cgottlieb@atlassian.com Caz (Inactive)
                        kbaxley Kent Baxley
                        Votes:
                        1 Vote for this issue
                        Watchers:
                        6 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                            cgottlieb@atlassian.com Caz (Inactive)
                            kbaxley Kent Baxley
                            Affected customers:
                            1 This affects my team
                            Watchers:
                            6 Start watching this issue

                              Created:
                              Updated:
                              Resolved: