Is it correct that youtrack has both the sets (issues as well as sub-issues) ~ and ~ (tasks as well as sub-tasks)? In other words 4 total things that have the same paralell where there is the thing as well as the "sub" thing (task or issue)? Or is that wrong? What is time tracking (in youtrack) come from? Is it coming from tasks? From issues? From both? What are the basis? What is the functional difference between an issue and a task (both conceptually as well as how implemented in youtrack)? I do (will) have questions about the best way/s to use youtrack for my scenario/s but for right now I often find myself having to 'step-back' and address core concepts I'm confused about. I'm not sure if this is the place to ask that or not. I'm trying to understand both youtrack as well as certain concepts in project management that have been ambiguous to me. Would there be a way or relating those back to the high level Epics and ensuring that changes to the backlog priorities were reflected? If we went for per-discipline projects instead. It could be filtered by something else but we feel some filtering is needed as organising the work for 30+ people in one go from one large work-board feels like it would be unmanageable. How can the top level priorities, that is to say the order of Epics and Stories in the "top level project" view be reflected in "sub-projects" for the team? From playing around with the tool for a while I came up with: Single project, tag issues based on team or discipline, generate work-boards filtered by discipline. Most of the work (at least at the task or ~<4 ideal week story size level) could be separated quite easily by team or the task level work could be. It will involve a few dozen people who currently work as several distinct teams based on their general technical area (software, electronic hardware, mechanical, etc). We have a large project, partially planned that we expect to take several months to complete. This sounds rather like the situation I now find myself in so I am interested in hearing what the suggested workflow was.
0 kommentar(er)
