Page MenuHomePhabricator

Track closed date and closing user for tasks explicitly
ClosedPublic

Authored by epriestley on Feb 8 2018, 10:46 PM.
Tags
None
Referenced Files
F12825856: D19037.id45649.diff
Thu, Mar 28, 9:10 AM
F12819788: D19037.id45649.diff
Thu, Mar 28, 5:48 AM
Unknown Object (File)
Wed, Mar 13, 4:52 AM
Unknown Object (File)
Feb 6 2024, 6:47 PM
Unknown Object (File)
Feb 3 2024, 6:02 PM
Unknown Object (File)
Jan 12 2024, 10:53 AM
Unknown Object (File)
Jan 6 2024, 12:41 PM
Unknown Object (File)
Dec 26 2023, 7:46 PM
Subscribers
None

Details

Summary

Ref T4434. Although some of the use cases for this data are better fits for Facts, this data is reasonable to track separately.

I have an approximate view of it already ("closed, ordered by date modified") that's useful to review things that were fixed recently. This lets us make that view more effective.

This just adds (and populates) the storage. Followups will add Conduit, Export, Search, and UI support.

This is slightly tricky because merges work oddly (see T13020).

Test Plan
  • Ran migration, checked database for sensible results.
  • Created a task in open/closed status, got the right database values.
  • Modified a task to close/open it, got the right values.
  • Merged an open task, got updates.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable