Sprint 14 Inventory Management

Inventory Management

Back in 2017 I created demo called BoatInventory which I showed to people at the kayaking club.  It was purely a database application where people could search our boat inventory.  I got some good feedback and people thinking about how a booking system could work.  Well, around 3 years later, I've finally added this functionality to BoatTrippy to make the demo obsolete! 

A key part of this functionality is the Inventory Management that the Equipment Officers can use to manage the boats.  Here are the new features:

Add New Inventory Item

Update an existing Inventory Item

Retire an Inventory Item

Fault Management

Also I've completed the fault / damage reporting and resolution workflows.  This now allows any member to report a fault, but only the equipment officers to mark as in repair and then resolve the report.  

There are two ways this can be used. 1) Mark as in repair which will stop people booking the boat until resolved.  This is for more serious faults that make the boat temporarily unsuitable for trips.  2) Resolve without marking as in repair. This is where the fault doesn't stop the boat being used on a trip.   

Integrated / embedded usage

This week I had a conversation with the club chair about the potential issue of the members not reading messages on the forum as they spend more time on the new application.  This is a valid point as the app is not intended to be used for general messages and discussions, particularly around club nights and SBOAC issues.

My intention is for the application to be used 'from the forum' rather than 'instead of the forum'.  I'll be doing some work in the next sprint to ensure that each of the workflows work from a single route (url) which can be reached from the forum.  

This means that we will remove the menu at the top of the application.  The parts of the application will only be accessible from direct links and login will redirect to these direct links.  If someone logs onto the app directly, they will land on their profile page where officers will have access to their console.  standard members. Any failures will be routed to a standard failure page where the user can report this to admin.

Sprint 13 Getting to production ready

Production Ready

There were a couple of features that I wanted to add to aid support in production.  The first was an auto-generated version number that is tied to an individual build.  This allows me to determine if a user is using the latest version or an older cached version.  Also, if an issue is found. I can log this against a distinct build and code revision.  I've also standardised all dates as UK format using this pipe and this list of timezones.

There is now a conditional release to a production environment which only runs on 'master' branch.  Details on how to specify these conditions can be found here.

Inventory Management

I've started the inventory management stories including the ability to filter the boats, mark as in repair and mark as repaired.