decred / cmsgui Goto Github PK

A nice tool to have for users should be a log work tool that will save entered work information to local storage that can be retrieved to produce an invoice that would be then submitted for approval.

The log work form should have the following fields:

• month/year
• type of work/reason for payment
• number of hours/quantity
• rate should probably be filled in automatically or users can switch to "reimbursement" mode or something to enter in a custom amount
• description of work/item

Would be good having an alternating stripes in rows. This way would be easier to check information.

Image to ilustration:

Show a basic overview of all user information such as:

• invoices
• last activity
• payouts/pending

Basic form that allows an admin to invite new users to cms:

https://github.com/decred/contractor-mgmt/blob/master/cmswww/api/v1/api.md#invite-new-user

Currently there is no proper confirmation or feedback that a user has successfully registered.

This pathing is slightly different from politeia, since users no longer need to confirm their email (due to invitations).

Allow users to view and edit name, location information that they entered during registration.

This should notify administrators of changes.

Allow admins to comment on line items of a given invoice and also approve/update an invoices status.

Currently cmswww takes comma separated value (csv) information for the various line items that a particular invoice may have.

There are a few different approaches that have been discussed.

1. All direct csv entry (with active field validation). There will be a textbox that allows the user to directly paste a copied exported csv from Excel/LibreOffice. Since we have the expected separator from the Policy request we can provide pretty thorough validation before allowing trasmission to cmswww.

2. Add line items form. This will allow users to essentially "create" the csv by filling out a form for each line item and "adding" it to the invoice. This method is nice since the validation will be simple and based on each line item field.

3. Submit an invoice that was created from logging work. This is similar to 2, except all the information has already been accumulated in local storage.

It looks like after the 10th row, the error count returns to 0

Basic logged in admin view that shows a list of all user invoices that have been submitted.

Second iteration of this will be to select certain invoices to create new payouts.