Good work by all involved; sufficiently implemented and functional to release and start using.
- Change the title element of the initial frontend page to something more meaningful than "TssgDbApp"
- All frontend page titles should, perhaps, be something other than, for example, "TSSG Home", as that's not really the actual TSSG home page that people will see when they go to http://tssg.tech
- Very long table values (such as the first and last name fields in the users' list) make it almost impossible for a user to scroll all the way to the right to use the Edit or Del buttons on the correct entry. (Perhaps move the buttons to the far left on all tables, make the long fields/columns individually horizontally scrollable, or limit the length of data)
- Move the descriptive text for the list pages (e.g., "A list of all venues currently in the database.") to the top of the page, perhaps between the page title and the table headers
- We probably shouldn't allow whitespace in a username
- Usernames are case-sensitive during login, this is non-standard IMHO
- Home page (after user successfully logs in) should show username (either in addition to or instead of user's first and last names)
Jira |
---|
server | TSSG Web |
---|
serverId | 21f4836d-b757-3b00-8915-8851ff10f1a5 |
---|
key | TWS-340 |
---|
|
Add copyright in footer- On the "List Team Schedule" page, the on-page title shouldn't be "Select Team Name"
- On the "List Team Schedule" page, move "(select one)" hint into the dropdown box as its hint
- Add the capability for a user to see which teams they belong to (perhaps just dump it out on the "Current User" page, but it might also be useful for an admin to see all the teams each user is a member of
- Add tips for when the user hovers over (with a mouse or whatever) a field name in all pages
- Sometimes, when I'm adding data and click Add, I see the pink flash of an error message, but it's gone so fast, I can't capture it
- When creating a new team, the specified team lead should be considered to be added as a member so as to not get the "At least one member is required" and/or "One or more team members are required." error