Premising that I like the implementation but I think it's not the desired solution.

It can be counter-intuitive to change the default view, just because in a specific view the fact that it's "Archived" is more prominent than others.

For example, some people then may ask "why my default view was changed?" and they will start manually "rollbacking" this to their desired view (e.g. showing closed tasks, from the Workboard, with a filter "Show all tasks").

So I may understand if we may want to decline this, and rename this to:

It is difficult to tell if a Workboard is archived or not

Or something like this

For example, some people then may ask "why my default view was changed?" and they will start manually "rollbacking" this to their desired view (e.g. showing closed tasks, from the Workboard, with a filter "Show all tasks").

That problem already exists anyway whenever someone changes the workboard view in the upper right corner and clicks "Save as Default" after, so I'm afraid I cannot follow the argumentation.

What's the use case ending up on an all empty workboard (assuming the default open tasks view and assuming folks cleaned up when archiving so no open tasks are left) of an archived project? Who does that help, compared to ending up on the Project Details page which at least gives you a hint why it's abandoned and empty?

I mean. See this archived Project (archived Milestone), that is linked from our changelogs:

https://gitpull.it/project/view/248/

When users archive projects or milestones, they don't necessarily want to change the default view to hide their Workboard.

That's why I'm saying that the root problem is probably just that the Workboard does not clearly says if it's archived or not.

We might come from different user journeys.
Your users might be aware what the project means, and that the project (and its workboard) is archived, and they do have an initial reason to look at this archived workboard (e.g. default view is not "open tasks" but "all tasks")?
My users clicked an external link to some project tag in something called Phorge, and that project has been archived in the meantime, and that project is set to show the workboard by default, and that is now just empty columns (as the default view of workboards is "open tasks"), and that is confusing and unhelpful.

OK. If you are partially mentioning nonsenses in we.phorge.it itself, you are indeed right.

Helping in cleanup:

• ✅ Change default view to "Description" (not to the empty menu "Workboard"); and also disabled unuseful menu "Subprojects", in:
  • ✅ "Almanac (archived)" https://we.phorge.it/project/18/item/configure/global/
  • ✅ "Harbormaster (archived)" https://we.phorge.it/project/28/item/configure/global/
  • ✅ "Mail (deprecated)" https://we.phorge.it/project/44/item/configure/global/
  • ✅ "Macro (deprecated)" https://we.phorge.it/project/view/31/ (also added the suffix "deprecated")
  • ✅ "Arcanist (depreacated)" https://we.phorge.it/project/54/item/configure/global/
  • 🔶 TODO: still need to write a useful description in the above!
  • 🔶 still help welcome.. they are many... https://we.phorge.it/project/subprojects/1/

So, premising that the mentioned feature unfortunately will not help us in cleaning the above thing,

But I understand that it would be an interesting default for our situation (if we only had a time machine to apply this idea before),

I still thing that our situation was not a normal situation, and the "Archive" feature was not designed to fix our specific situation, and it's not designed to change the default view.

I still think this new default may be an in-tuitive thing: some might believe it is a bug, and would try to troubleshoot it and disable it.

Moreover, even with this new default, people may still arrive on these "confusing Workboards" by visiting links like this one, that are fixed on the Workboard:

https://we.phorge.it/project/board/31/

So, we should really manage the UX root problem first, about the Workboard page:

T15890: Workboard: better clarify if it's Archived