Order Entry UI Sprint 1

Owned by Osaze Edo-Osagie
Last updated: Jun 10, 2018 by Lanre Lawal
2 min read

General Information

Team Lead: Daniel Kayiwa

Sprint Lead: Osaze Edo-Osagie

Timeline

Start Date: Mar 15, 2018 

End Date: Mar 29, 2018 

Participants

  • Flavia Nshemerirwe

  • Fredrick Mgbeoma

  • Betty Kebenei

  • Lanre Lawal

  • Geoffrey Asiimwe

  • Osaze Edo-Osagie

Sprint Goals

The main goal is to design and implement an Order Entry UI.

The goal has been sub divided into several tasks:

  1. UI implementation of the Order page

  2. Create a ticket to consume already existing Api to search for a drug

  3. Create a ticket to consume already existing Api to add a new order

  4. Create a ticket to consume  already existing Api to edit an existing order

  5. Create a ticket to consume already existing Api to discontinue/delete an active order

  6. Create a ticket to consume already existing Api to show all active orders

  7. Create a ticket to consume already existing Api to show all past orders

  8. Create ticket to setup base application



Sprint Dashboard 

key summary type created updated due assignee reporter priority status resolution

Unable to locate Jira server for this macro. It may be due to Application Link configuration.



How to Participate 

Add your name to the list on this wiki page (with any comments about your availability). If you want to join after the sprint has started just join the IRC channel mentioned above and say hello.

The general process:

  1. New to OpenMRS sprints? Want help getting started? Join IRC and say "???": I'd like to participate in the sprint!". If you get no response, just ping any of the above sprint participants as per the IRC tips at http://en.flossmanuals.net/openmrs-developers-guide/support/

  2. Pick a ticket from the available tickets in the top-left of the sprint dashboard page at:

    • Make sure it does not depend on a ticket that is incomplete.

  3. If you have any questions about the ticket, ask on the group chat

  4. Do the ticket. See our HOWTO for git. Sprint specific git HOWTO for devs with push rights: whatever works for you :-) If you don't like pull requests, don't send them. Commit and push directly to the main repo. If you do like pull requests, fork the main repo and send pull requests, but merge them right after. My favorite way is to work on the main repo, but create local branches (without pushing them to the main repo). Merge branches locally to the master and push to the main repo.

  5. Join the daily scrum to share your updates



During Project Notes for the sprint

To be added while the project progresses 

Sprint Retrospective:

To be added after the end of the sprint. 

Resources