Details
-
Bug
-
Resolution: Fixed
-
Low
-
10.66, 10.93
-
3
-
Severity 2 - Major
-
No
Description
Issue Summary
Currently all sprints coming into Jira Align from Jira are treated as standard Sprints, regardless of whether or not an anchor Sprint is set to an IP-type Sprint
Steps to Reproduce
- Create standard team Sprints and IP team Sprints in Jira
- Sync the Sprints with Jira Align
Expected Results
The connector should recognize IP sprints accordingly and treat them differently when syncing them in from Jira. For example, these type of sprints should not be considered in Velocity Calculations.
Actual Results
Jira connector does not recognize / treat IP Sprints differently. This means that IP sprints end up getting factored into Velocity Calculations
Workaround
It is possible to create team Sprints in Jira Align and sync them down to Jira to help avoid this situation.
Attachments
Issue Links
- is related to
-
JIRAALIGN-3146 Azure DevOps (ADO) Connector - synced sprints are all labelled as Type Standard
-
- Closed
-
-
ALIGNSP-9207 Loading...
-
ALIGNSP-9346 Loading...
- was cloned as
-
JIRAALIGN-3146 Azure DevOps (ADO) Connector - synced sprints are all labelled as Type Standard
-
- Closed
-
- resolves
-
ALIGNSP-2342 Loading...