The week did not start out strong. Sunday night D&D, Monday late back from work, and Tuesday was another day without coding. However, I was exploring what to build by brain storming ideas with a colleague in the Philippines and bouncing ideas off Co-Pilot on how to implement the projects.
Co-Pilot was off the opinion that I should use Python and TKinter over Flutter and Dart. From a maintenance perspective, if I had to hand this project over to a colleague then writing it in Python would have made sense a few years ago. Now that we're in the world of generative AI and LLMs, it removes some of the need for actually understanding the code if it was created with Flutter and Dart. So after some internal debate, I decided to proceed with the latter.
Having concluded on:
- Project ideas
- Sync tool between JIRA and Aha!
- Tool checks if JIRA requirements are closed
- It will automate the closure of the linked features in Aha!
- Tech stack
- Flutter and Dart for Windows
- Decision whether to sign the app will be made later on
I started creating the first login screen. This will prompt the user to enter Personal Access Token for JIRA as well as API key for Aha!. Each entry has a button to check if the keys are valid. If these have already been entered on a previous occasion, this screen will be by-passed and the next screen is shown.
The second screen is the main activity screen. It prompts the user at the top to enter a JIRA query that returns a list of requirements. If the list is valid, it will display the requirements in a table with ID, description, status, and closure date (if applicable). It will also show the linked Aha! feature (if there is an ID in Aha!) and will show the ID, description, and status.
The user can then update each JIRA requirement - Aha! feature pair individually. Or the user can multi-select the pairs and the app will update each one after the other and display the results on the screen. The app should also keep an audit file that is appended with each set of updates.