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

Blocked Reason field not getting cleared/overwritten

XMLWordPrintable

      Issue Summary

      The Blocked Reason field is not getting cleared or overwritten.

      This is reproducible on Data Center: yes

      Steps to Reproduce

      Steps to Reproduce without the connector synching the field to Jira:

      1. In Jira Align, on a feature, set blocked = yes and add a blocked reason and click on Save.
      2. In Jira Align, on same feature, set blocked = no and click on Save.
      3. In Jira Align, on same feature, set blocked = yes - look at the Blocked Reason field. It will show the value from the previous blocked reason. When I set the value to no in Step 2, the blocked reason should also be cleared. It should not be in the field when I mark it yes again.

      Steps to Reproduce with the connector synching the field to Jira:

      1. Setup the connector to use the Jira Flagged field on Field Management tab.
      2. In Jira Align, on same feature, set blocked = yes and add a blocked reason and click on Save.
      3. In Jira Align, on same feature, set blocked = no and click on Save.
      4. In Jira, on same feature, set the flag.
      5. In Jira Align, look at the blocked reason for the feature. It should say “Marked as flagged in Jira Software” but instead it shows the blocked reason you put in step 2. When I set the value to no in Step 3, the blocked reason should also be cleared. It should not be in the field when I mark it yes again.

      Expected Results

      When I set the value to no, the blocked reason should also be cleared

      Actual Results

      It will show the value from the previous blocked reason.

      Workaround

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

              5ed8ef87d2cd Karen Bradshaw (Inactive)
              121fc1e6b3d8 Andre Deme
              Votes:
              2 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: