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

Field Management: The setting 'Parent field Parent work item custom field on features (Jira epics) (read-only text field)' causes inconsistent behavior, as indicated by the Blocked (Flagged) field and custom field.

XMLWordPrintable

    • 1
    • Severity 2 - Major
    • No

      Issue Summary

      If the Parent Epic field is synced before the JA Blocked field is set, the JSW Parent work item field is filled, and then the JA Blocked sync fails.
      If the Parent Epic field is first synced at the same time as the JA Blocked field is set, the JSW Parent work item field is empty, and the JA Blocked sync succeeds.

      We tested with Blocked (Flagged), MMF, and custom field. We experienced sync failure if the Parent Epic field is filled in Jira.

       

      This is reproducible on Data Center: (yes)

      Steps to Reproduce

      1. Step 1. Configure the blocked field with a custom Jira field
      2. Step 2. Do not configure the setting 'Parent field Parent work item custom field on features (jira epics) (read-only text field)'
      3. Step 3. Create 3 features (2 without an owner and 1 with an owner)
      4. Step 4. Set the Jira project field accordingly to synchronize to Jira
      5. Step 5. For the first feature without an owner assigned, change the blocked field from 'no' to 'yes', set a blocked reason, and save.
      6. Step 6. For the second feature without an owner assigned, change the blocked field from 'no' to 'yes', set a blocked reason, modify the description, and save
      7. Step 7. For the third feature, with an owner, change the blocked field from 'no' to 'yes', set a blocked reason, and save.
      8. Step 8. Wait for synchronization to complete

      Expected Results

      The blocked field value should be synchronized in Jira regardless of whether the feature has an assigned owner or if the description was modified.

      Actual Results

      For the first feature, the blocked field value was not synchronized in Jira
      For the second feature, the blocked field value was synchronized in Jira
      For the third feature, the blocked field value was synchronized in Jira

      Additional Note

      1. The JA to Jira sync of the 'Blocked' field (and probably other ones such as the MMF) is not triggered if the feature does not have an owner and the connector setting 'Parent field Parent work item custom field on features (jira epics) (read-only text field)' is not configured.
        This is demoed with the Loom video: https://www.loom.com/share/ae80093cae8446fbb3a254aeb11e5286
      2. The JA to Jira sync of the 'Blocked' field (and probably other ones such as the MMF) is not triggered when the connector setting 'Parent field Parent work item custom field on features (jira epics) (read-only text field)' is configured but the corresponding field in Jira has the value 'None'.
        This is demoed with the Loom video: https://www.loom.com/share/d1d7b2d9836944a2b2c29de986c1ab99

      Workaround

      Assign the owner or update the description in JA, and then the Blocked field is synced.

            [JIRAALIGN-7124] Field Management: The setting 'Parent field Parent work item custom field on features (Jira epics) (read-only text field)' causes inconsistent behavior, as indicated by the Blocked (Flagged) field and custom field.

            Brandon Harris (Inactive) made changes -
            Remote Link New: This issue links to "PS-172711 (Atlassian Support System)" [ 949830 ]
            backbone-sync-bot made changes -
            Resolution New: Fixed [ 1 ]
            Status Original: In Review [ 10051 ] New: Closed [ 6 ]
            backbone-sync-bot made changes -
            Fix Version/s New: 11.2.0 [ 108194 ]
            backbone-sync-bot made changes -
            Status Original: In Progress [ 3 ] New: In Review [ 10051 ]
            backbone-sync-bot made changes -
            Status Original: Short Term Backlog [ 12074 ] New: In Progress [ 3 ]
            SET Analytics Bot made changes -
            Support reference count New: 1
            Rachel Kim made changes -
            Affects Version/s New: 10.132.2 [ 107305 ]
            Rachel Kim made changes -
            Description Original: h3. Issue Summary

            If the Parent Epic field is synced before the JA Blocked field is set, the JSW Parent work item field is filled, and then the JA Blocked sync fails.
            If the Parent Epic field is synced at the same time as the JA Blocked field is set, the JSW Parent work item field is empty, and the JA Blocked sync succeeds.

            We tested with Blocked (Flagged), MMF, and custom field. We experienced sync failure if the Parent Epic field is filled in Jira.

             

            This is reproducible on Data Center: (yes)
            h3. Steps to Reproduce
             # Step 1. Configure the blocked field with a custom Jira field
             # Step 2. Do not configure the setting 'Parent field Parent work item custom field on features (jira epics) (read-only text field)'
             # Step 3. Create 3 features (2 without an owner and 1 with an owner)
             # Step 4. Set the Jira project field accordingly to synchronize to Jira
             # Step 5. For the first feature without an owner assigned, change the blocked field from 'no' to 'yes', set a blocked reason, and save.
             # Step 6. For the second feature without an owner assigned, change the blocked field from 'no' to 'yes', set a blocked reason, modify the description, and save
             # Step 7. For the third feature, with an owner, change the blocked field from 'no' to 'yes', set a blocked reason, and save.
             # Step 8. Wait for synchronization to complete

            h3. Expected Results

            The blocked field value should be synchronized in Jira regardless of whether the feature has an assigned owner or if the description was modified.
            h3. Actual Results

            For the first feature, the blocked field value was not synchronized in Jira
            For the second feature, the blocked field value was synchronized in Jira
            For the third feature, the blocked field value was synchronized in Jira

            *Additional Note*
             # The JA to Jira sync of the 'Blocked' field (and probably other ones such as the MMF) is not triggered if the feature does not have an owner and the connector setting 'Parent field Parent work item custom field on features (jira epics) (read-only text field)' is not configured.
            This is demoed with the Loom video: [https://www.loom.com/share/ae80093cae8446fbb3a254aeb11e5286]
             # The JA to Jira sync of the 'Blocked' field (and probably other ones such as the MMF) is not triggered when the connector setting 'Parent field Parent work item custom field on features (jira epics) (read-only text field)' is configured but the corresponding field in Jira has the value 'None'.
            This is demoed with the Loom video: [https://www.loom.com/share/d1d7b2d9836944a2b2c29de986c1ab99]

            h3. Workaround

            Assign the owner or update the description in JA, and then the Blocked field is synced.             		New: h3. Issue Summary

            If the Parent Epic field is synced before the JA Blocked field is set, the JSW Parent work item field is filled, and then the JA Blocked sync fails.
            If the Parent Epic field is first synced at the same time as the JA Blocked field is set, the JSW Parent work item field is empty, and the JA Blocked sync succeeds.

            We tested with Blocked (Flagged), MMF, and custom field. We experienced sync failure if the Parent Epic field is filled in Jira.

             

            This is reproducible on Data Center: (yes)
            h3. Steps to Reproduce
             # Step 1. Configure the blocked field with a custom Jira field
             # Step 2. Do not configure the setting 'Parent field Parent work item custom field on features (jira epics) (read-only text field)'
             # Step 3. Create 3 features (2 without an owner and 1 with an owner)
             # Step 4. Set the Jira project field accordingly to synchronize to Jira
             # Step 5. For the first feature without an owner assigned, change the blocked field from 'no' to 'yes', set a blocked reason, and save.
             # Step 6. For the second feature without an owner assigned, change the blocked field from 'no' to 'yes', set a blocked reason, modify the description, and save
             # Step 7. For the third feature, with an owner, change the blocked field from 'no' to 'yes', set a blocked reason, and save.
             # Step 8. Wait for synchronization to complete

            h3. Expected Results

            The blocked field value should be synchronized in Jira regardless of whether the feature has an assigned owner or if the description was modified.
            h3. Actual Results

            For the first feature, the blocked field value was not synchronized in Jira
            For the second feature, the blocked field value was synchronized in Jira
            For the third feature, the blocked field value was synchronized in Jira

            *Additional Note*
             # The JA to Jira sync of the 'Blocked' field (and probably other ones such as the MMF) is not triggered if the feature does not have an owner and the connector setting 'Parent field Parent work item custom field on features (jira epics) (read-only text field)' is not configured.
            This is demoed with the Loom video: [https://www.loom.com/share/ae80093cae8446fbb3a254aeb11e5286]
             # The JA to Jira sync of the 'Blocked' field (and probably other ones such as the MMF) is not triggered when the connector setting 'Parent field Parent work item custom field on features (jira epics) (read-only text field)' is configured but the corresponding field in Jira has the value 'None'.
            This is demoed with the Loom video: [https://www.loom.com/share/d1d7b2d9836944a2b2c29de986c1ab99]

            h3. Workaround

            Assign the owner or update the description in JA, and then the Blocked field is synced.
            Yannick Genin made changes -
            Labels New: bulldog
            Yannick Genin made changes -
            Development Effort New: M [ 13032 ]
            Status Original: Needs Triage [ 10030 ] New: Short Term Backlog [ 12074 ]

              fea1a6ef3355 Yannick Genin
              965b37518492 Rachel Kim
              Affected customers:
              1 This affects my team
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: