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

Jira Connector - Start date of sprint import not working with sprint logic: Map Sprints based on their end dates

    • 1
    • Severity 3 - Minor
    • No

      Issue Summary

      As per the Start date of sprint import documentation with a date set, no sprints after this date should be synced to Jira Align.

      However, sprints created in Jira before the specified date in Start Date of sprint Import are being synced when using the sprint logic that maps sprints based on their end dates.

      Steps to Reproduce

      1. Create a sprint on Jira (Day - 1)
      2. Now on your Connector set the Start date of sprint import to date after your Sprint creation date (day + 1)
      3. Map your Sprint's board in Administration > Jira Management > Jira Boards 
      4. Wait until the next Board sync cycle
      5. Note that your sprint will sync to Jira Align

      It was observed it doesn't happen using the old sprint logic

      Expected Results

      According to our documentation sprints created after the date configured in the Start date of sprint import should not be synced.

      Actual Results

      Using the sprint logic: Map Sprints based on their end dates sprints with creation date older than Start date of sprint import are syncing to Jira Align

      ...
      

      Workaround

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

            [JIRAALIGN-8102] Jira Connector - Start date of sprint import not working with sprint logic: Map Sprints based on their end dates

            Yannick Genin made changes -
            Labels New: bulldog
            Yannick Genin made changes -
            Development Effort New: L [ 13033 ]
            Status Original: Needs Triage [ 10030 ] New: Short Term Backlog [ 12074 ]
            SET Analytics Bot made changes -
            Support reference count New: 1
            Victor Fragoso made changes -
            Description Original: h3. Issue Summary

            As per the [Start date of sprint import documentation |https://help.jiraalign.com/hc/en-us/articles/115000088453-Jira-integration-setup#:~:text=Start%20date%20of,data%20collection]with a date set, no sprints after this date should be synced to Jira Align.

            prints created in Jira before the specified   *Start Date of sprint Import* are being synced when using the sprint logic that *maps sprints based on their end dates.*
            h3. Steps to Reproduce
             # Create a sprint on Jira (Day - 1)
             # Now on your Connector set the Start date of sprint import to date after your Sprint creation date (day + 1)
             # Map your Sprint's board in *Administration > Jira Management > Jira Boards* 
             # Wait until the next Board sync cycle
             # Note that your sprint will sync to Jira Align

            It was observed it doesn't happen using the old sprint logic
            h3. Expected Results

            According to our documentation sprints created after the date configured in the Start date of sprint import should not be synced.
            h3. Actual Results

            Using the sprint logic: *Map Sprints based on their end dates* sprints with creation date older than Start date of sprint import are syncing to Jira Align
            {noformat}
            ...
            {noformat}
            h3. Workaround

            Currently there is no known workaround for this behavior. A workaround will be added here when available
            New: h3. Issue Summary

            As per the [Start date of sprint import documentation |https://help.jiraalign.com/hc/en-us/articles/115000088453-Jira-integration-setup#:~:text=Start%20date%20of,data%20collection]with a date set, no sprints after this date should be synced to Jira Align.

            However, sprints created in Jira before the specified date in *Start Date of sprint Import* are being synced when using the sprint logic that *maps sprints based on their end dates.*
            h3. Steps to Reproduce
             # Create a sprint on Jira (Day - 1)
             # Now on your Connector set the Start date of sprint import to date after your Sprint creation date (day + 1)
             # Map your Sprint's board in *Administration > Jira Management > Jira Boards* 
             # Wait until the next Board sync cycle
             # Note that your sprint will sync to Jira Align

            It was observed it doesn't happen using the old sprint logic
            h3. Expected Results

            According to our documentation sprints created after the date configured in the Start date of sprint import should not be synced.
            h3. Actual Results

            Using the sprint logic: *Map Sprints based on their end dates* sprints with creation date older than Start date of sprint import are syncing to Jira Align
            {noformat}
            ...
            {noformat}
            h3. Workaround

            Currently there is no known workaround for this behavior. A workaround will be added here when available
            Victor Fragoso made changes -
            Description Original: h3. Issue Summary

            As per the [Start date of sprint import documentation |https://help.jiraalign.com/hc/en-us/articles/115000088453-Jira-integration-setup#:~:text=Start%20date%20of,data%20collection]with a date set no sprints after this date should be synced to Jira Align.

            However, if you use the sprint logic: *Map Sprints based on their end dates* sprints created after the configured date still sync to Jira Align Board mappings.
            h3. Steps to Reproduce
             # Create a sprint on Jira 
             # Now on your Connector set the Start date of sprint import to date after your Sprint creation date (day + 1)
             # Map your Sprint's board in *Administration > Jira Management > Jira Boards* 
             # Wait until the next Board sync cycle
             # Note that your sprint will sync to Jira Align

            It was observed it doesn't happen using the old sprint logic
            h3. Expected Results

            According to our documentation sprints created after the date configured in the Start date of sprint import should not be synced.
            h3. Actual Results

            Using the sprint logic: *Map Sprints based on their end dates* sprints with creation date older than Start date of sprint import are syncing to Jira Align
            {noformat}
            ...
            {noformat}
            h3. Workaround


            Currently there is no known workaround for this behavior. A workaround will be added here when available
            New: h3. Issue Summary

            As per the [Start date of sprint import documentation |https://help.jiraalign.com/hc/en-us/articles/115000088453-Jira-integration-setup#:~:text=Start%20date%20of,data%20collection]with a date set, no sprints after this date should be synced to Jira Align.

            prints created in Jira before the specified   *Start Date of sprint Import* are being synced when using the sprint logic that *maps sprints based on their end dates.*
            h3. Steps to Reproduce
             # Create a sprint on Jira (Day - 1)
             # Now on your Connector set the Start date of sprint import to date after your Sprint creation date (day + 1)
             # Map your Sprint's board in *Administration > Jira Management > Jira Boards* 
             # Wait until the next Board sync cycle
             # Note that your sprint will sync to Jira Align

            It was observed it doesn't happen using the old sprint logic
            h3. Expected Results

            According to our documentation sprints created after the date configured in the Start date of sprint import should not be synced.
            h3. Actual Results

            Using the sprint logic: *Map Sprints based on their end dates* sprints with creation date older than Start date of sprint import are syncing to Jira Align
            {noformat}
            ...
            {noformat}
            h3. Workaround

            Currently there is no known workaround for this behavior. A workaround will be added here when available
            Victor Fragoso created issue -

              fea1a6ef3355 Yannick Genin
              f58471712ff6 Victor Fragoso
              Affected customers:
              0 This affects my team
              Watchers:
              2 Start watching this issue

                Created:
                Updated: