## Self-service App

Thank you for contributing! Please take a moment to review our [**contributing guidelines**](TBD)
to make the process easy and effective for everyone involved.

**Please open an issue** before embarking on any significant pull request, especially those that
add a new library or change existing tests, otherwise you risk spending a lot of time working
on something that might not end up being merged into the project.

Before opening a pull request, please ensure:

- [ ] You have followed our [**contributing guidelines**](TBD)
- [ ] Double-check your branch is based on `develop` and targets `develop` 
- [ ] Pull request has tests (we are going for 100% coverage!)
- [ ] Code is well-commented, linted and follows project conventions
- [ ] Documentation is updated (if necessary)
- [ ] Internal code generators and templates are updated (if necessary)
- [ ] Description explains the issue/use-case resolved and auto-closes related issues
- [ ] Please set the PR title in this format: `<type: feat/fix/bug/chore/etc>(<scope>): [<issue-number>] <description>` (See [commit message conventions](https://gist.github.com/stephenparish/9941e89d80e2bc58a153))

Be kind to code reviewers, please try to keep pull requests as small and focused as possible :)

----------

### What problem does this PR solve?
(Please summarize what's in the JIRA ticket or specification.)


### How does this PR solve it?
(What is the approach? What tools are used?)


### What Documentation/References will help understand the problem and solution?
(Please be sure to include links to any libraries, conversations, SO posts, etc.)


### Screenshots or GIFs (if not already on Confluence/JIRA):
(Taking a few seconds to provide images will likely save you explanation time in code-review... )


### Any limitations or related work yet to be done?
(If someone else is working on a related story, please explain who and where...)


### Any other things you've done here that aren't strictly related to the JIRA ticket?
(Consider putting big items in another PR. Small incidental ones are ok...)


### How can reviewers test the changes?
(What user steps would someone need to follow to reach the feature and see it in action?)

### To-Do List (if WIP):
* [ ] Item 1
* [ ] Item 2
* [x] Item 3