Track object closed/completed date and actor
Closed, ResolvedPublic
Actions

Assigned To

None

Authored By

	epriestley
	Feb 14 2014, 10:02 PM

Description

Paraphrased request from @carl: Track who closed tasks in Maniphest, and the date they were closed, and surface those fields in ApplicationSearch. Motivation: Review progress made during weekly sprints.

Paraphrased request from @chad: Track when everything was closed, and expose "closed recently" as a global search filter. Motivation: in most searches, open and recently closed things are usually more interesting than just open things.

These are both fairly easy technically, although they tend to make already-complex interfaces more complex and the Maniphest flavor might bump into other things a bit (on the other hand, it might make them better/easier).

Revisions and Commits

rP Phabricator
	D19039	rPe26a784dcf3e Allow tasks to be filtered and ordered by closed date
	D19038	rP4c4707e46763 Provide task closed date via Conduit API, data export pipeline, and in list UI
	D19037	rPf028aa6f60dd Track closed date and closing user for tasks explicitly

Related Objects
Search...

Status	Assigned	Task
Resolved	None	T4434 Track object closed/completed date and actor
Resolved	epriestley	T4171 Building reporting and data systems
Duplicate	None	T6041 Metrics for Maniphest
Resolved	epriestley	T1562 Build "Facts", an ETL pipeline and charting application
Open	None	T12402 Report on team velocity
Open	None	T12403 Multi-category burnup charts
Open	None	T12410 Cycle Time and Lead Time Reports
Open	None	T12459 Provide evidence-based forecasting of projects

Event Timeline

epriestley created this task.Feb 14 2014, 10:02 PM

epriestley raised the priority of this task from to Normal.

epriestley updated the task description. (Show Details)

epriestley added projects: Projects, Maniphest.

epriestley added subscribers: epriestley, chad, carl.

To be clear, I'm less interested in who closed any given task (the task's owner is a very good approximation of this) and more interested in the close date.

gaspaio edited this Maniphest Task.Feb 15 2014, 3:53 PM

epriestley edited this Maniphest Task.Feb 15 2014, 3:54 PM

T5061 has some similar discussion about wanting to look at recent commits/revisions, but "updated" being a noisy ordering on that. In the commit case, Audit can do it now, but tracking these formally could improve things.

epriestley merged a task: T6514: View tasks closed within a time period.Nov 11 2014, 3:27 AM

epriestley added subscribers: michaeloa, qgil.

cburroughs added a subscriber: cburroughs.Nov 11 2014, 1:19 PM

epriestley merged a task: T6679: Support "dateResolved" field in Maniphest task JSON returned from maniphest.query.Dec 2 2014, 7:34 PM

epriestley merged a task: T6678: Support searching of a "last resolved after" in advanced search.

epriestley added a subscriber: jasondsmith.

T6821 is similar ("last assigned date" vs "last closed date"). I want to try doing "last X date" through Facts. Maybe some values of "X" are useful/general enough to make first-class, but it would be desirable for each value of X to prove its worth through a Facts implementation before promotion.

epriestley mentioned this in D11306: Maniphest - allow for searching for tasks based on dependency relationships.Jan 12 2015, 6:17 PM

epriestley mentioned this in D11419: Implement clock/trigger infrastructure for scheduling actions.Jan 16 2015, 8:05 PM

qgil mentioned this in T6491: Herald rules based on age.Jan 22 2015, 2:05 PM

epriestley mentioned this in T6771: Create index for transactionType in phabricator_maniphest.maniphest_transaction.Mar 26 2015, 5:36 PM

angie added a project: Restricted Project.May 20 2015, 5:07 PM

cburroughs mentioned this in T8280: email notifications appear to bypass some project visibility rules.May 20 2015, 6:22 PM

epriestley merged a task: T8523: Allow query for Maniphest tasks closed within a certain date range.Jun 12 2015, 12:09 PM

epriestley added a subscriber: joshuaspence.

edibiase added a subscriber: edibiase.Nov 9 2015, 2:51 PM

Herald added a subscriber: jhurwitz. · View Herald TranscriptNov 9 2015, 2:51 PM

epriestley mentioned this in D14670: Change/drop/reconcile some miscellaneous edit behaviors in Maniphest.Dec 4 2015, 6:59 PM

epriestley mentioned this in rPf1744ac6d9f8: Change/drop/reconcile some miscellaneous edit behaviors in Maniphest.Dec 5 2015, 12:31 AM

More use cases:

As a product manager/Product Owner/ScrumMaster, I want to identify all tasks closed in the last 1 or 2 weeks, so that I can learn about completed work I wasn't aware of in order to take followup actions. Some examples of followup actions include making announcements, coordinating with affected parties, or modifying release plans.

As a PM/PO/SM, I want to know of any tasks closed in the last 1-2 weeks, and their points value, so that I can make sure that points are set.

As a PM/PO/SM, I want to know of any tasks closed in the last 1-2 weeks, and their points value, so that I can evaluate the accuracy of current estimation.

An example of a Recently Closed report that satisfies these use cases.