Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

×
Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Can you create a plan, where supports fields as date with time selection?

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.

Thanks!

1 answer

0 votes
Dave
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Mar 10, 2021

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).

Regards,

Dave

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events