Otherwise, the dependencies are always in conflict, as we have several activities per day with different start and end times in the schedule. (Datums-/Zeitauswahl).
For example, start today at 08:00 end at 10:00.
The next activity start right at 10:00, but only if the other one is completed.
Hi @Alan Abosowitsch ,
Thanks for sharing this use case. The primary use case for Advanced Roadmaps is expected to be agile planning (e.g. scrum / kanban) and typically the issues would only be planned at most to the day, and most commonly to the sprint.
We haven't had many calls for more precision on the start / end dates. At the moment we don't have any plans to increase the precision but it would be really helpful to understand your use case and the type of work that you're doing that requires this level of precision.
It sounds like you're using the dependencies feature, and I'm wondering if you're experimented with setting the plan configuration to use concurrent rather than sequential dependency scheduling (if you are using sprints then this would stop the scheduling showing as in conflict).
Atlassian's marketplace partners have had a very productive start to 2021! Since our last roundup, our developer community has added over 160 new cloud apps to the Atlassian Marketplace to help you...
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