djrieger/kantan

Manage expenses in a group or community

kantan's Issues

Settlement notifications

When a group administrator settles all current expenses (#3), notify users who they have to pay or who owes them money, respectively, via e-mail. For users who have added their bank account details, include this data and inform each debitor that the creditor prefers a bank transfer instead of being paid in cash.

Implement settlements

A group administrator should have a "Settle" button for each group they administer. When clicked, all current (unsettled) expenses for this group will be settled.

Limit group membership

When users register and/or request access to a group, the group administrator is notified and has to grant access before this user can view the group.

Allow specifying date for expenditures

UI implementation:
http://stackoverflow.com/questions/13340982/twitter-bootstrap-datepicker-internalization
http://stackoverflow.com/questions/9306515/property-date-must-be-a-valid-date-error-when-using-jquery-ui-plugin
http://comments.gmane.org/gmane.comp.lang.groovy.grails.user/138704

Display balance on all pages

The current user should be able to see his current balance no matter which page they are currently viewing.
If a user belongs to only one community, their balance should be displayed in the top right corner. If a user belongs to more than one community, the balance for each community should be displayed on the community's tab.

Join requests

If a user is the group administrator, display a list of all pending requests for group membership (caused by #8). The administrator can decide whether to grant or deny each request and the user who made the request is notified via e-mail.

Save preferred language

Implement registration

Users should be able to register with their email, full name, bank account details (optional). They are immediately granted access to the groups they specify.
Upon successful registration, they are redirected to the first group they requested access to.

Display only relevant expenses to each user

Community administrators should be the only people allowed to view all expenses in a community. All other users should only be able to see expenditures if

• they are the creater and thus creditor
• they were listed as a debitor (possibly with additional guests) in an expense created by another user

Allow editing of expenditures

Allow the creator of an expenditure editing unless the expenditure is already settled.

Force names to be unique

Add a global unique constraint to the combination of first and last name.

Request group membership

Allow existing users to request membership for groups. As of #4, users are immediately granted access to groups.

E-mail notification for new expenditures

When a new expenditure has been added, notify all debitors via e-mail.

List of expenditures

For each group the current user gets a table containing all expenditures they created and all expenditures listing them as debitors.