Since only one PI can be selected for a feature, what is the proper way to handle work that carries over from one PI to another PI? Currently we are asked to change the PI once it carries over. Will this cause bad data?
@Tim Young Splitting features that don't complete within a PI is a good option for handling carryover work. When you split a feature in Jira Align the feature will be split into a part 1 and part 2. The part 1 of the feature will have all the accepted stories linked to it and the part 2 of the feature will have all the stories not accepted within the PI. During the splitting process you can target the PI to assign to part 2. After splitting the feature, a link between split part 1 and part 2 in the feature details panel will appear.
Targeting split part 2 for a future PI
Link to split part 2
The advantages of splitting features are vs. carrying over features:
(Or, What to expect when you’re expanding.) Once you've completed your Jumpstart, or your initial assessment of Jira Align, you'll start to think about how you can roll it out to the rest of your e...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events