Emergency Requisitions Redesign: Model & API changes

Description

As a part of this ticket we should decide what model & API changes are necessary to support the new emergency requisition workflow described in

Acceptance criteria:

  • Start a discussion on the dev group to decide on questions from (seprarate model/REST resource)

  • Design changes in the database model & REST APIs

  • Push model & RAML changes to a dev branch for review and someone else to pick from there on implementation start

  • Update with info on necessary changes and create new tickets if necessary and add to epic

Assignee

Sebastian Brudziński

Reporter

Sebastian Brudziński

Labels

None

Story Points

3

Time tracking

10h

Components

Sprint

None

Fix versions

Priority

Major
Configure