TRUNK-324:Go through the TODO items code and create tickets out of them

[janieken]

Description of what I changed

contains todos contains todo container

Issue I worked on

https://issues.openmrs.org/browse/TRUNK-324

Checklist: I completed these to help reviewers :)

• [ ] My IDE is configured to follow the code style of this project.

  No? Unsure? -> configure your IDE, format the code and add the changes with git add . && git commit --amend

• [ ] I have added tests to cover my changes. (If you refactored existing code that was well tested you do not have to add tests)

  No? -> write tests and add them to this commit git add . && git commit --amend

• [ ] I ran mvn clean package right before creating this pull request and added all formatting changes to my commit.

  No? -> execute above command

• [ ] All new and existing tests passed.

  No? -> figure out why and add the fix to your commit. It is your responsibility to make sure your code works.

• [ ] My pull request is based on the latest changes of the master branch.

  No? Unsure? -> execute command git pull --rebase upstream master

[jwnasambu]

@janieken I must admit I admire your resilience keep it up! Kindly basing on the ticket description this is not the anticipated output. You were meant to do a global search for the word "TODO" in the api and web projects and create ticket(s) with as much description as possible and link those tickets to this ticket. I believe some TODO tickets are already attached to this ticket for reference purposed. Kindly is my explanation making sense?

[tendomart]

I strongly agree with @jwnasambu