Page MenuHomePhabricator
Create Task
Maniphest T134604

Decide how to handle tasks with archived projects only
Closed, ResolvedPublic
Actions

Description

Phabricator contains bunch of tasks, which are parts of archived project(s) only. It's recurring issue.

So the question is, what to do with those. Basically creating and documenting some generic procedure to follow would be nice.

See also

Related Objects
Search...

Event Timeline

Danny_B created this task.May 6 2016, 8:01 PM
Restricted Application added subscribers: Zppix, Aklapper. · View Herald TranscriptMay 6 2016, 8:01 PM
Danny_B triaged this task as Medium priority.May 6 2016, 8:48 PM
Danny_B moved this task from Incoming to Administration on the Project-Admins board.
Krenair subscribed.May 6 2016, 11:32 PM
Danny_B added a project: Documentation.May 6 2016, 11:37 PM
Danny_B updated the task description. (Show Details)
Danny_B moved this task from Backlog to Phabricator on the Documentation board.
Aklapper added a comment.May 7 2016, 3:03 PM

If a task is in no other project, try to contact (former) stakeholders of the archived project (and/or create a task about it) twice, and ask what to do about them / whether someone plans to re-triage those tasks.
If impossible to get a reply within a reasonable timeframe, mass-close as declined.

Qgil moved this task from To triage to Team radar on the Developer-Advocacy board.May 10 2016, 11:39 AM
Qgil added a subtask: T133649: Identify archived projects with tasks open that have no other projects assigned.Jun 1 2016, 6:47 PM
Dzahn subscribed.Jun 1 2016, 8:18 PM

or catch it at the archiving step and make sure that it doesnt happen for any project before all tasks are closed. like make it a (technical?) requirement that you cant archive them when tasks are open and they have to be moved or declined first for this to happen

Aklapper merged a task: T135493: Decide how to handle tasks of archived projects (or vice versa).Jun 9 2016, 12:55 PM
Aklapper mentioned this in T135493: Decide how to handle tasks of archived projects (or vice versa).

What is left to do here to get consensus?

In T135493#2301151, @Aklapper wrote:

IMO dead projects are dead and reactivating is a wrong signal, and removing projects from tasks removes information where a task "came from" and they'd get removed from the list of tasks associated to that (archived) project.

I recommend contacting project members and watchers and ask them what to do with the remaining tasks - e.g. decline those tasks if no other project is assigned, or triage those tasks by adding active projects to them.

• mmodell merged a task: T135493: Decide how to handle tasks of archived projects (or vice versa).Jul 15 2016, 11:26 PM
Aklapper closed this task as Resolved.Oct 23 2016, 6:15 PM
Aklapper claimed this task.
Aklapper edited projects, added Developer-Advocacy (Oct-Dec-2016); removed Developer-Advocacy.
Aklapper moved this task from Backlog to October on the Developer-Advocacy (Oct-Dec-2016) board.

Added "take care of open tasks" to https://www.mediawiki.org/wiki/Phabricator/Project_management#Archiving_a_project in this edit.

Closing task as resolved.

Qgil awarded a token.Oct 27 2016, 1:39 AM
Content licensed under Creative Commons Attribution-ShareAlike (CC BY-SA) 4.0 unless otherwise noted; code licensed under GNU General Public License (GPL) 2.0 or later and other open source licenses. By using this site, you agree to the Terms of Use, Privacy Policy, and Code of Conduct. · Wikimedia Foundation · Privacy Policy · Code of Conduct · Terms of Use · Disclaimer · CC-BY-SA · GPL · Credits