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

ETL job fails with a Sprint Short Name of 37 chars despite having Shortname datatype as nvarchar(50)

XMLWordPrintable

    • 1
    • Severity 2 - Major
    • No

      Issue Summary

      The ETL job fails for Sprint with a shortName of 37 chars even though the shortName is a nvarchar(50) on view [Sprints] in Enterprise Insights version 10.125.

      This is reproducible on Data Center: Yes

      Steps to Reproduce

      • Create an anchor on the PI, update the short of the anchor to have the maximum char

      • Set the Team Sprint Prefix (on the team slide out) to the maximum of 24 chars

      • Have a sprint on jira that matches the anchor
      • Wait for the conector to create the sprint

      • Notice that the EI ETL job fails with the below error-

      Expected Results

      EI ETL job should not fail having Sprint Short Name less than 50 chars for EI version 10.125

      Actual Results

      The ETL job fails with a Sprint with a shortName of 37 chars even though the shortName is a nvarchar(50) on view [Sprints] in Enterprise Insights version 10.125.

      Workaround

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

            dguimbellot@atlassian.com David Guimbellot
            935a1c2f5863 Arathi M S
            Votes:
            1 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: