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

Canceling a Synced Feature in Jira hides it in Jira Align instead of putting it in Canceled Bin

    • Icon: Bug Bug
    • Resolution: Not a bug
    • Icon: Low Low
    • None
    • 10.97.2
    • Jira Connector
    • None
    • Severity 3 - Minor
    • No
    • None

      Issue Summary

      Canceling a Synced Feature in Jira hides it in Jira Align instead of putting it in Canceled Bin

      Steps to Reproduce

      1. Have a Feature mapped to Jira Epic
      2. Have Canceled state mapped
      3. Move the Jira Epic to Canceled state on Jira side
      4. Check Canceled Items for Features
        • Selecting the same program or all programs or any other options doesn't seem to find it

      Expected Results

      In Jira Align the Feature should show in Canceled bin, per documentation, and also based on Stories behaviour in same scenario

      Actual Results

      The Feature cannot be found in Canceled bin, Recycle bin, Deleted items report.

      When the Jira Epic is moved back out of canceled state on Jira side, the Feature is reinstated in Jira Align and Audit log continues correctly.

      So it continues to be the same Database item.

      Workaround

      Can see and reinstate the Feature on Jira Software side, however there doesn't appear to be a workaround for tracking the canceled Features on Jira Align side.

            [JIRAALIGN-3457] Canceling a Synced Feature in Jira hides it in Jira Align instead of putting it in Canceled Bin

            Was able to reproduce if Administration → Connectors → Jira Settings → Jira Setup, Custom Fields → Default User is not set to an existing user ID.

            Will open up another issue if we can reproduce in a different way. 

            Kirill Duplyakin added a comment - Was able to reproduce if  Administration → Connectors → Jira Settings → Jira Setup, Custom Fields → Default User  is not set to an existing user ID. Will open up another issue if we can reproduce in a different way. 

              kforeman@atlassian.com Kyle Foreman
              c7f2a2ebc58e Kirill Duplyakin
              Affected customers:
              1 This affects my team
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: