Designing the schema

Back in Chapter 3,The TrackStar Application we proposed some initial ideas about the issue entity. We proposed it have a type, an owner, a requester, a status, and a description. We also mentioned when we created the tbl_project table that we would be adding basic audit history information to each table we create to track the dates, times and users who update tables. Nothing has changed in the requirements that would alter this approach, so we can move ahead with that initial proposal. However, types, owners, requesters, and statuses are themselves, their own entities. To keep our model flexible and extensible, we'll model some of these separately. Owners and requesters are both users of the system, and will be referenced he rows in a table called tbl_user. We have already introduced the idea of a user in the tbl_project table, as we added the columns create_user_id and update_user_id to track the identification of the user who initially created the project, as well...