Derrick
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 Derrick supported this idea ·
Hello. I came across this thread in a search and in the exact same situation. I divided up projects to cover off huge major initiatives from various dept heads. However some people will work in multiple project components in a single sprint. The current setup doesn't allow this to happen. Instead I need a different way to prioritize requests from different groups (while preserving where the request came from) and allow resources to be assigned to different initiatives in the same sprint. Ideas here?