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

"Owner" field is not syncing from Jira Align to Jira

XMLWordPrintable

    • 2
    • Severity 1 - Critical
    • No

      Issue Summary

       

      The syncing of the "Owner" field from Jira Align to Jira Assignee field works only if the email ID is the same in both JA and Jira - which is the expected behavior.

      However, the "Assignee" field in Jira syncs to the "Owner" field in JA even when the email IDs of the user are different in Jira and JA.

      Steps to Reproduce

      1. Jira Align owner to Jira assignee sync:
        • Created a test user in Jira with email ID (eg. test@something.com), and set it as "assignee" to a Feature(Epic) in Jira.
        • Syncs it with JA.
        • When the sync is done, modified the user email ID in Jira Align.
          • Example: From test@something.com to test@somethingdifferent.com
        • Remove the Feature Assignee from Jira.
        • Force the sync from JA to Jira by updating the Feature description in Jira Align
        • The Owner field from JA did not sync over to Jira as expected.
          • Note that the reason is that the user with email ID test@somethingdifferent.com does not exist in Jira.

               2.Jira Assignee to Jira Align owner sync:

        • Modify the user email ID in JA.
          • Example: from test@something.com to test@somethingdifferent.com
        • Remove the "Owner" field in Jira Align Feature.
        • Update the description of the Jira Feature and wait for a sync
          • Even though the user email ID was different in Jira(test@somethingdifferent.com) and Jira Align(test@somethingdifferent.com), the Assignee field from Jira synced over to Jira Align and got assigned to test@somethingdifferent.com.

      Expected Results

      The Owner field is synced from Jira Align to Jira.if you

      Actual Results

      It is not possible to sync the Owner field from Jira Align to Jira.

       

      Workaround

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

              fea1a6ef3355 Yannick Genin
              f9fc804f30c6 Luiz Felipe Arruda
              Votes:
              2 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: