Perhaps something like TravisCI?

Look for a way in which we can automatically put a build out. Maybe something online or local that can create a release on Github.

Convert the entire project to a react app.

• Hook up the apis to the existing Bugzilla website here.
• An initial test for using the apis against this website show that a username and password is not needed to make the request, all that is needed is an API key.
• Thinking of hooking up the lists functionality over to AWS, it could be stored with a user ID or and API key, or a combination of both, with a column of the list contents (a comma separated list of bug numbers). Could be done in a DynamoDB table or an S3 bucket.
• Remove the documentation functionality, this is no longer needed.

Any further ideas / comments should be noted here.

Instead of a local file.

When using an api key only, Bugzilla figures out who the person is, removing the need for usernames and passwords as previously used.

All that should be needed at the login is the api key. Searches for bugs by user should just require a username to search against.

Separate environments for development in Eclipse and when installed as an application. Suggest using a config file that the application reads in eclipse, and depending on which mode, use a specific folder.

This could be done in the Folders interface.

Maybe it can be included as a program argument, e.g:
-Dactive.profile = dev
Or something like that?

Should direct to the Wiki page.

I think this will be a lot better project if done this way.

• Make backend a Spring Boot application
  • RestControllers and Services
    • Bugs
      • Get by numbers
      • Get by username
      • Get comments
      • Add comment
      • Get attachments
      • Change status
    • Config
      • Integrate with Mongo
      • Get config
      • Save config
    • List
      • Integrate with Mongo
      • Get list
      • Get existing lists
      • Save list
      • Delete list
  • Config under /resources
    • Custom banner
  • Unit tests
  • Add swagger
• Make frontend React App
  • Bugs
    • Bug table
    • Remove bug from table
    • Add bug to table
    • Comment modal
    • Attachment modal
  • Lists
    • Show lists
    • Use a list as current
    • Edit list
    • Delete list
  • Config
    • Manage config page
    • Add link to swagger documentation
  • Information Pane
  • Add favicon
  • Linting
• Dockerise
  • Sprint Boot Dockerfile
  • Front end Dockerfile
  • docker-compose.yml
• Travis

Go through each file and remove things no longer needed or make it better.

One thing is that the message boxes should be called at the very top level, not halfway down the stack in a try catch.

ApiRequestor should throw a custom exception instead of the Java Exception

GUI should be changed to UI

login package should be moved into the app package.

Create a test bug under my email to test.

Instead, look for a lightweight queue solution? What about a node express app with routes?

It's no longer needed.

For example, it should be Bug Service, BugComments, BugAttachment etc

Seems to be because the database is empty, and so the app fails as there is no list to use.

What about in docker?