Decisions API

A decision is the record of a choice the project made: the context it was taken in, the options weighed with their pros and cons, what was decided, what follows, who decided and when, and the earlier decision it replaces. Decisions number on their own sequence (CRM-DEC-5), carry a kind (architecture, product, process, vendor or security) and move from proposed to accepted or rejected, and from accepted to superseded or deprecated. Accepting a decision that names an earlier one supersedes that one in the same move, so the log never holds two decisions in force on the same question.

Every save of a decision writes a version; the versions are read and put back through the endpoints below, under the decisions' own abilities.

The log is internal. A staff token sees the decisions of the projects it may see; a client guest's token sees none of them, and a decision it asks for is a 404 RESOURCE_NOT_FOUND, never a 403. Every write runs the same action the Decisions page runs, under the project permissions, and announces itself as a decision.* event.

EndpointsCopy Anchor Link

Related

RAID Log APIThe risks and dependencies a decision answers to.Activity APIWho changed a decision and when, beside the versions themselves.decision.* eventsThe lifecycle of a project's decisions: a decision added, changed, moved along its lifecycle, put back to an earlier version and deleted.