moritzrupp / contractview-jhipster Goto Github PK

As a developer, I want to use JHipster 6, so that security vulnerabilities are fixed and new features are introcuded.

Acceptance criteria

• Upgrade to JHipster 6
• All unit tests are still successful

Update the README file.

• Remove the non-relevant jhipster content and add relevant contractview content.
• Add waffle.io badge

As a user, I want to be able to choose between different types of contracts, so that I can easily distinguish, filter, and set different settings for each type of contract.

Acceptance criteria

• A contract can be of one type
• A user can create own types
• The following types are provided out of the box
  • Insurance
  • Entertainment
  • Energy
  • Communication

As a user, I want to have an calendar overview of my contracts, so that I know exactly which contracts ends/has to be cancelled by day/month/year.

Acceptance criteria

• The user can see a calendar like overview (day/week/month/year) with all the contracts reaching the end
• By hovering over the contract entry more information is displayed
• A list view is provided as well

As a user, I want to receive e-mail notifications before a contract reaches the notice period, so that I am aware of it and can decide to cancel the contract.

Acceptance criteria

• A daily schedule checks for contracts with are reaching the notice period
• The user can set how many days before the notice period of the contract the e-mail should be sent
• The e-mail is sent to the e-mail address the user is registered with
• An e-mail is only sent if at least one contract is reaching the notice period
• The time for the schedule checking the contracts can be configured

Set up CI/CD with Travis CI and automatic deployment to heroku.

Also update README and add Travis CI badge.

As a developer, I want to use grommet as the frontend library, so that I have a framework for common components.

Aceptance criteria

• grommet is used as the frontend framework
• All frontend code is replaced by grommet
• A jhipster blueprint is created for the usage of grommet

As a user, I want to batch import my contracts, so that I can quickly and user-friendly add alls of my current contracts.

Acceptance criteria

• A user can upload CSV (tab-, comma, and semicolon-separated) files from the UI
• All rows in the CSV file are imported
• A CSV file can be uploaded from the UI
• If a row cannot be imported, the conflict is shown to the user, but the rest of the rows are imported
• If the format of the CSV file (invalid columns, missing columns) is wrong, an error message is shown with information about the correct format