Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

How Are You Using Target Date in Atlas?

Hi Community,

As we continue our sandbox testing of Atlas, great questions are being raised and I'm curious how other Atlas users are using the Target Date for projects.

Are you using it for the next milestone? A software release? Project completion?

Ultimately we will need to align on something and set and manage expectations across the business accordingly but keen to understand the experience from the community as to what this type of view tells you about dates.

2023-05-17 14 36 47.png

1 answer

1 accepted

0 votes
Answer accepted
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 21, 2023

Hi Sing,

I can't answer this for other Atlas users but I can answer it for Atlassian. Our view is that there's no right answer, and the best approach will depend on the nature of each project.

For instance, for smaller projects we might have a single Atlas project that runs from when the project kicks off and has a target date of when the code is delivered to production. You can still post updates for completed projects and these updates will appear in the digest email, so any clean up tasks etc. or measuring of the impact of a project could be captured against the completed project. If a project slips and you need to change the target date, we think that's fine, thought obviously if a project's target date keeps getting pushed back it's clearly At Risk or Off Track and should be marked as such.

However, for larger projects we might break it down by milestone, and then have a separate Atlas project either for each delivery milestone or for the development phase (e.g. discovery versus delivery). We've tried not to be too prescriptive, with the desire that the projects in Atlas are an accurate bottoms-up view of the work being done.

Got it. Thanks @mj.

Getting insights into good practice from others is always helpful!

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events