nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How can I make the Atlas Date work for Published Views?

John McDonald_b6k8yh

We use JPD for all of our product planning and roadmapping, and I've been creating published views for stakeholders. We use the Atlas Date field as the Target Date for our projects, but it looks like that view does not come through for Timeline views, or any views for that matter. Ummm, what? This is a major issue for us as we basically cannot provide accurate views for stakeholders. Is there a workaround that doesn't involve us having to manually update a secondary date field specific to publish views? (This is a pretty big deal for us, and we are a major enterprise customer of Atlassian)

Accepted answers

Tanguy Crusson

@John McDonald that's an oversight on our part: the Atlas project field is not yet supported in published views, so you shouldn't have been able to publish this view in the first place. We'll start by fixing that.

We'll add support for Atlas project fields in a subsequent change.

Thank you for reporting this!

All comments

Tanguy Crusson

We'll add support for Atlas project fields in a subsequent change.

Thank you for reporting this!

John McDonald_b6k8yh

Thanks Tanguy - I appreciate the response. I'm curious if you have any estimate for when you think Atlas fields will be supported in published views? This will help determine what changes we make to our published views in the interim. Thanks!

John McDonald_b6k8yh

@Tanguy Crusson Just circling back on this - do you have any recommendations for how to manage published roadmaps, when we are heavily leveraging Atlas for the management of the Target Dates? Is the solution to manually duplicate the Atlas Target Date into a field that the Timeline View will accept in the meantime?