Wiki Spaces


Get Help from Others

Q&A: Ask OpenMRS
Discussion: OpenMRS Talk
Real-Time: IRC Chat | Slack


Page tree

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.

General Sprint Information: 

Lead (Product Owner): OpenMRS community Jonathan TeichShasha Liu

Developer Lead: Kaweesi Joseph Daniel Kayiwa
Known Testers and Developers Assigned: OpenMRS community
Key Contributors: SolDevelo 

Sprint Start Date: 1001/1108/14
Sprint End Date:  14 15/1108/14
Kick Off
 - Friday, 1st August, 2014. Time: 9am EDT

Sprint dashboard




Source Code:

User Name: admin

Password: Admin123/openmrs-module-allergyui 

Sprint Goals: 

The overarching goal of this sprint is to make sure that we release a stable OpenMRS Platform 1.11the Allergies project is for caretakers to be aware of any allergies a patient has and any possible interactions with treatments and medications it may cause.  
For further information see Allergy Project Overview Page here: Allergies Project Ver. 2 

With that in perspective, the focus of the current sprint is to:

  1. Manually test all known functionality to ensure that it works as expected
  2. Fix any bugs that we come accross  



  1. Create Allergy API module
  2. Update and create needed allergies data tables and API  
  3. Create short list of preset allergens and reactions for patients 
  4. Allow users to add and display new allergies for patients 

KickOff Meeting: 

Widget Connector


  1. Daniel Kayiwa
  2. Shasha Liu
  3. Jonathan Teich 
  4. Krzysztof Kaczmarczyk

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.


  1. New to OpenMRS sprints? Want help getting started? Join IRC and say "???": I'd like to participate in the sprint!"
  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

Tasks To Be Completed Prior To Design


During Project Notes for the sprint: 

To be added while the project progresses 

Sprint Retrospective:  

To be added after the end of each sprint. 

See Also