Jon Anders
My feedback
1 result found
-
14 votes
Hi,
Thanks for the feedback.
Due to security and simplification reasons, we isolated projects, meaning each project has it’s own backlog and sprints.
Now adding the possibility of sharing sprint would essentially means that, users from one project could be responsible of items from other project. We have to analyze impacts on UI etc of opening up the sharing.
As a work around for now, perhaps you can add members from one project to another and vice versa, then they would be able to see both projects and perhaps need of duplication of sprint goes away.
Meanwhile, as said, we will analyze the impact of possibility of sharing sprints between projects.
Best Regards,
Yodiz Support Team
FinlandAn error occurred while saving the comment Jon Anders supported this idea ·
Adding members to both projects still doesn't make it possible to add user stories from more than one backlog into one single sprint, which is what we need.
Our use case:
We are developing a software product which always need extensions and customizations when delivered to one of our customers. We want to maintain one backlog for our product and one separate backlog for each customer. When implementing a new feature for a customer, this usually involves some items from the product backlog and some items for the customers backlog, but we want all this in one sprint.