new request forms section

[adambreznicky]

requests related to new features, new apps, permission alterations (temporary s3 bucket accesses), etc. are currently done through casual verbal requests for less-than-specific github issues. let's curb against this by defining the specific criteria we need for these various requests via a form within the admin console!

i imagine a new dashboard section of the console listing a table for each type of request. then each type can accept new submissions by tnris employees adding new records to them. each new record will be, itself, the form used for submitting. with this in mind, each schema can vary based on the type of request it is.

each table's existing records should be un-editable to anyone outside of the IS team. outsider should only be able to create new records for submitting. after submitting, IS team will have control of managing field content, deleting, etc.

each table should have columns for use and editable only by IS team for managing the request itself. I imagine an open notes or assignee field, checkbox for 'reviewed', checkbox for 'approved' vs 'disapproved', date field for expected work bring or end date, and so on.

i imagine there should also be notfications wired up for various events. new record events is a must. that way, when a tnris employee submits a new record for a request, IS team peeps receive an email alerting them.

holding an IS team meeting to discuss the details when one of us chooses to begin work on this is probably a good idea. will help the brainstorm and outlining the project plan for implementation.