Please deactivate: Project status removed after 13 weeks without update

English Forum Product Feedback
, ,
1

Hi, I have received some questions from our Asana Users regarding suddenly missing Project status updates. After some investigation I discovered that this is expected behaviour, which I think should be changed.

Current situation:
After 13 weeks without Project status update, Asana automatically switches the status to “no recent updates”.
The last status is neither visible in the Project, nor in Portfolios it is part of.
It is only visible in the Overview sheet.

Preferred:
Always show the last status, even if it is quite old.

Reasoning:

  • Some projects are not updated very often/only when necessary
  • Even older Projects might still be relevant as reference / for transparency / audits
2 Likes
2

Hi, it would be great to adjust this, or at least have the option of setting a longer time period to which the update won’t disappear (ex. longer than 13 weeks). Some projects are not fast moving, and it should preserve the update longer.

2 Likes
3

Couldn’t agree more - this is my ONLY gripe with Asana - please can we make it so that it always shows the last status update, and does not move to ‘No Recent Updates’

2 Likes
4

I fully agree and support your request @Christine_L !

1 Like
5

Thanks for flagging this! I’ve been wondering myself if it ever resets to “No recent update” since I noticed that you cannot manually set it to this status (or clear the status back to none set once you’ve selected one of the 5 status options).

Question: How were you able to determine the 13 week trigger?
I’d like to share this with my team and having a document I can link to would help, in addition to this forum post.

Thanks!

1 Like
6

We have a high number of projects. By comparing them I started suspecting that this behavior always occurs around the 12-week mark. After flagging this to the Asana support, they confirmed that this is an expected behavior after 13 weeks of status-stagnation. But they did not tell me the logic behind this decision.

7

Hi - was there any update with this? This feature is causing a bit of a pain for our reporting.

8

Hi, I have not heard of any changes. Please vote for it to push it up further :slight_smile:

1 Like
9

I’d previously voted in support of this, but coming back to it to note that even if Asana decides that they want to keep this behaviour in general for whatever reason, this is particularly egregious when the last-posted state of a project is “On Hold’“. By definition, projects that are on hold will often not be evolving in a way that requires providing updates, and obfuscating this status provides no value at all.