Page MenuHomePhabricator

Normalize the definition of "closed" revision statuses
ClosedPublic

Authored by epriestley on Nov 25 2013, 11:24 PM.
Tags
None
Referenced Files
Unknown Object (File)
Thu, Apr 18, 2:22 AM
Unknown Object (File)
Wed, Apr 10, 4:24 AM
Unknown Object (File)
Tue, Apr 9, 10:57 AM
Unknown Object (File)
Fri, Mar 29, 4:13 PM
Unknown Object (File)
Feb 14 2024, 12:35 AM
Unknown Object (File)
Feb 14 2024, 12:35 AM
Unknown Object (File)
Feb 6 2024, 10:34 PM
Unknown Object (File)
Feb 6 2024, 10:23 PM
Subscribers

Details

Summary

Currently, "Closed" and "Abandoned" are treated as "closed". I want to add a flag which treats "Accepted" as "Closed", too, for Asana and other companies who use an Asana-like workflow.

The background here is that their workflow is a bit weird. They basically do audits, but have a lot of things which Diffusion doesn't do well right now. This one change makes Differential fit their workflow fairly well, even though it's an audit workflow.

To prepare for this, normalize the definition of "closed" better. We have a few callsites which explicitly check for "ABANDONED || CLOSED", and normalizing this is cleaner anyway.

Also delete the very old COMMITTED status, which has been obsolete for over a year.

Test Plan

Browsed around most/all of the affected interfaces.

Diff Detail

Branch
asanaclosed
Lint
Lint Passed
Unit
Tests Passed