- Remove tag from open tasks to not confuse users.
- Reactivate the project (and possibly to rename it to something generic to avoid product-specific name, ie. #proxy, #cache or so...)
Although Varnish is archived and mentions it has been superseeded by Traffic, it is still in use.
I do not consider that a problem hence proposing to decline.
The project is archived and hence displayed greyed out and not offered in dropdown proposals. Has any confusion been reported?
If you think that tasks associated to archived tags are somehow a problem, please elaborate what you think is the problem.
You're right. Thanks for the correction. It is shown in dropdowns and it explicitly says "Archived".
However that seems to not be relevant for the rest of my comment, hence clarifications are welcome what is the actual underlying problem to solve in this task.
I'm not aware of users confused by archived projects left associated to tasks - if there are any such reports, links are welcome so potential approaches could be discussed (e.g. I could imagine to adjust the UI to strike-through a project name to make things clearer).
Proposing to decline this task until underlying reasons why archived projects create confusion are clearer.