Should be a really simple version change.

Tests currently don't work, go ahead and write them to test our backend models and controllers.

Write an overview and purpose of the app in the readme underneath the build steps.

Implement the following two tables on the test database on the server:

Tables

• User
  id
  name
  password // Dummy only 123password
  active_ind

• Ticket
  id -> primary
  logger_id < foreign key for the person who logged the ticket.
  worker_id < foreign key for the worker on the ticket
  title
  description
  resolution
  status_ind -> open closed inProgress

Upgrade to .NET 7 and look at using Span and Memory where it makes sense.

Create a docker image to hold the app so we can easily CI/CD to it. Then the consumer just needs to throw the image up and be done.

Install and use Entity Framework.

There is no log at the moment. It would be preferable if all the encountered exceptions are logged to a text file.
So, add a good logging so that someone knows what's going on in their instance.

Write Sql queries to make cool charts related to the tickets. How many closed per month, average close time, etc.
May also need to add rows to database or add new tables.
Just keep the table creation scripts for the build updated and it would automatically update stuff so no problem.

We should have a build script that does the following:
Installs elixir for running the script.

1. Just use F# so we don't have to do more dependencies.
2. Installs a local database.
3. Builds the application and sets up information to work with that database.
4. Automatically runs tests on PRs

Src should be separate from the sln, sln should be top level or at least top level in src, projects relegated to their own spots.

Create a build process for CI/CD

The instructions on building the app have changed.

The build script doesn't wait for the install GUI for MySql to close before continuing. It would be better if it installed MySql via the command line and then continued after it is done.

1. Rewrite most of the code so that the Sql scripts take care of everything on the back end instead of having it in the controllers.
2. Rewrite the controller to consume the DB info from the settings file which will be in git ignore. Dependency Injection
3. Port the code to core 5.0 for records as the classes were already basically immutable.
4. Do a code pass to make sure all the code is the same stylistically and there are no bugs.
5. Once the rewrites are complete we can consider that a 2.0 and throw it on a server. Maybe: Write deployment scripts to set it all up for me in probably F#.
6. Will need to write several sql scripts to take care of all the actions already done.
7. Break up this problem into their sub domains.

I'm going to remove all the nullable stuff. It's inefficient and a poor replacement for a real option type.

We should have a script that sets up a local dev database for testing.

We will keep using blazor, here's the items I want to do on this:

1. Change the tables to a better library to use that instead.
2. Make sure every view works correctly.
3. Add in better feedback to the users.