Design /approveUpdate

License and Copyright Notice

By submitting this issue or commenting on this issue, or contributing any content to this issue, you certify under the Developer Certificate of Origin that the content you post may be licensed under GPLv3 (for code) or CC-BY-SA 4.0 International (for non-code content).

Pre-checklist

• I have searched for, and did not find, an existing issue at the top-level.

Stories

Story 1: As a developer I want to be able to post data to my database so that we can store information relevant to our service.

Ready checklist

• Independent (of other issues in flow)
• Negotiable (and negotiated)
• Valuable (the value to an identified role has been identified)
• Estimable (the size of this story has been estimated using /weight value or the menu on the right)
• Small (can be completed in 50% or less of a single iteration)
• Testable (has testable acceptance criteria)

Also

• Appropriate role labels have been applied (e.g., role:*).
• Relevant activity labels have been applied (e.g., activity:*).
• Linked to related issues, epics, and milestones.

Diagrams

Acceptance Criteria

Scenario: [3-5 word description of scenario]
  Given you understand APIs
  When you look at the api design for this call
  Then you will understand how the api call works and what it does

Template Version 2.0.0