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)
Fri, Feb 21, 3:53 PM
Unknown Object (File)
Fri, Feb 21, 12:10 PM
Unknown Object (File)
Thu, Feb 6, 9:09 AM
Unknown Object (File)
Thu, Feb 6, 8:30 AM
Unknown Object (File)
Jan 23 2025, 4:04 PM
Unknown Object (File)
Jan 15 2025, 12:02 AM
Unknown Object (File)
Jan 2 2025, 5:04 AM
Unknown Object (File)
Dec 29 2024, 10:55 AM
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

Lint
Lint Skipped
Unit
Tests Skipped