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

[JIRAALIGN-1648] Jira Connector: Square brackets, newline characters in the Jira Sprint are causing the sync to fail

XMLWordPrintable

    • 8
    • Severity 2 - Major
    • A-Team - Usher1

      Issue Summary

      If the Sprint in Jira tool has square brackets in the name/goals ( e.g. - []) - the sync is failing.

      Steps to Reproduce

      There should be a board in Jira that contains a sprint with the square brackets in the name. The board should be synced with Jira Align

      1. Create a user story in Jira and wait until it is pushed to Jira Align
      2. Place the story to the sprint from preconditions in Jira
      3. Make changes to the story in Jira to trigger the sync, for example, change the description and the state
      4. Validate if the changes were pushed to Jira Align

      Expected Results

      Changes are pushed to Jira Align

      Actual Results

      Changes are not pushed. This is reproducible for Sprints, Epic, and Stories.

      Workaround

      The workaround for the issue is to rename the Sprint(s) in Jira and remove the square brackets and newline characters.

        1. Screen Shot 2020-09-24 at 10.10.08 AM.png
          Screen Shot 2020-09-24 at 10.10.08 AM.png
          79 kB

          Form Name

            [JIRAALIGN-1648] [JIRAALIGN-1648] Jira Connector: Square brackets, newline characters in the Jira Sprint are causing the sync to fail

            Tony D. added a comment -

            Hello, this has been resolved and included in our Supplement release notes for 10.79 . 
            Thank you,
            Jira Align Product Engineering Team

            Tony D. added a comment - Hello, this has been resolved and included in our  Supplement release notes for 10.79  .  Thank you, Jira Align Product Engineering Team

            Tony D. added a comment -

            Fixed in 10.77 being released to the Saas Test Environment per the release calendar.

            Tony D. added a comment - Fixed in 10.77 being released to the Saas Test Environment per the release calendar.

            Adam Voss added a comment -

            I find it extremely concerning that there has been no movement on this bug, when it is around data quality.  Surely the accuracy of data should be the highest of Align's priorities.  Issues like this make it next to impossible for me to champion adoption of Align internally as no-one trusts the data

            Adam Voss added a comment - I find it extremely concerning that there has been no movement on this bug, when it is around data quality.  Surely the accuracy of data should be the highest of Align's priorities.  Issues like this make it next to impossible for me to champion adoption of Align internally as no-one trusts the data

              tdavenport@atlassian.com Tony D.
              vvyhovskyi@atlassian.com Vitalii Vyhovskyi (Inactive)
              Affected customers:
              4 This affects my team
              Watchers:
              18 Start watching this issue

                Created:
                Updated:
                Resolved: