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; } } }

Updates due configuration?

Andy Johnston

Hey everyone, new here, setting up an Atlas site on a new Jira software instance.

I looked for this, but couldn't find it - and searched this board but also came up short.

Status Update Frequency? Atlas requires an update every Friday. Is there a way I can configure the status update frequency to align with the sprints? (every two weeks?) or even longer if I have a large program of work which is running all yeah the Program lead may only give a status update monthly to the SteerCo. (even if it was two weeks for everything we could manage that)

Comments

Jeff Hoover

From what I have seen, no. That isn't something Atlassian lets us configure.

Vernon L

Hey @Andy Johnston

Jeff is correct. Currently, there isn't any configurability around a custom update cadence, but this is a request and feedback we hear very often. We're looking into the best way to apply this customizability and all the implications of how it'd work with reminders, product functionality, etc. I've added your feedback to our ideas board, since knowing how many people are looking for this feature is helpful when it comes to prioritizing work.

While still not perfect, you may be able to model larger programs of work using a combination of goals and sub-goals since these are only updated once per month (reminders on the 1st of the month, updates shared a week later on the 8th). You can find out more in this article.

Thanks again for your feedback—hope this helps!

Andy Johnston

Hey @Vernon L - another quick question on this - do you know of a way to turn off the Status Updates component to Atlas if we are going to focus initially entirely on monthly Goals?

My assumption here is no, but I thought it worth asking if the individual components can be enabled or disabled depending on usecase?

Goals look like how we'll start at least, but everything focuses on the status updates.

christine_stpierre

In our organization, we appreciate the weekly updates. Still, the challenge arises after a solution's launch, when there are no updates to provide while we assess its performance against our goals.

The practice should not be to close a project and mark it complete simply because it was released/delivered ( box checking) - Thus, we keep our projects Open-On-Track until we can validate the outcomes, which can take weeks/months This results in continuous reminders and a timeline feed with no updates.

If related goals are updated, the goal update should be pushed to the specified project(s). This prevents the need for updates in multiple locations.

Welcome!

It looks like you're new here. Sign in or register to get started.