update_requirement

Change a requirement by requirement_id with any of title, category (a non-functional requirement's quality), statement and rationale (HTML), source_stakeholder_id, source (where it came from, in words), priority, measure, verification_method (test, inspection, analysis or demonstration), owner_id and status. The kind, functional or non-functional, never changes: it picked the sequence the requirement was numbered from. A field left out keeps its value; a field sent as null is cleared. The fields go through the same action the Requirements page runs and write a version; requirement.updated goes out. A status goes through its own move: deprecated, baselined or back to draft are moves a person may make by hand, and requirement.status_changed goes out. in_review and approved are reached through submit_for_review and the approvers, and any move is refused while an approval request is open. A staff token with requirement:update on the project is needed.