Order Entry UI Sprint 4

Owned by Fredrick Mgbeoma
Last updated: Jun 10, 2018 by Lanre Lawal
2 min read

General Information

Team Lead: Daniel Kayiwa

Sprint Lead: Fredrick Mgbeoma



Timeline

Start Date: 7th May 2018

End Date: 21st May 2018

Participants

  • Flavia Nshemerirwe

  • Fredrick Mgbeoma

  • Lanre Lawal

  • Geoffrey Asiimwe

  • Osaze Edo-Osagie

  • Betty Kebenei

Sprint Goals

The main goal of this sprint is to complete the remaining functionalities of the Order Entry UI using React/Redux.

The goal has been sub divided into several tasks:

  1. Checking the existence of encounter role

  2. Update and optimise application tests

  3. Fix Linter and prop type validation issues

  4. Implement pagination for active drug orders

  5. Consume Api to discontinue/delete an active order

  6. Make a POST request to actually add orders.

  7. Consume Api to edit an existing order



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:

  3.  

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

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

  5. 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.

  6. 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