Backlog
1Under consideration
Next up
Committed and queued
No Next up issues
In Progress
1Actively being built
Done
10Recently shipped
Component ride history
Along side with the component install history it could be also the component ride history, listing all rides where it has been used on.
Only count the activities a component was actually used on
Right now every component installed to a bike picks up every ride on that bike (depending on the install date). If you keep one wheelset for the trainer and another for outdoors, or swap between mountain bike and gravel tyres on the same frame, both sets wear out on paper while only one of them is being ridden. Same story if you rotate several pairs of shoes. You can off course uninstall and later re-install but that is cumbersome. I'm planning to fix this in two steps. First, by the kind of ride. On a component you'll be able to say it only counts for indoor rides, or only outdoor, or only for a particular sort of ride — road, gravel, mountain bike, e-bike. Strava already records which kind each activity was, so this works with what you've uploaded already, including rides from months ago. It stays off unless you switch it on for a specific part, so nothing changes for anyone who doesn't want it. Second, and I'm less sure about this one: tags. For things the kind of ride can't separate — four pairs of shoes, two identical wheelsets — you'd give a part a tag, add it to your Strava ride title like #raceshoes, and only that part picks up the ride. It depends on you remembering to type it, which makes it the weaker of the two, and the first step may well cover most cases on its own.
One-step "Swap with..." for rotating components
I rotate two waxed chains on one bike and swap them every couple of weeks. Today that takes two separate status changes: set the installed chain to In Storage, then set the stored chain to Installed. Each step asks for its own date, so it’s easy to get them out of sync. Nothing warns me if I forget the first step, and I end up with two chains installed at once. Suggestion: add a “Swap with…” action on an installed component that: Lets me pick a stored component of the same type (or any type). Moves the current one to In Storage and installs the new one in a single step, sharing one date (and time, if that’s added). Optionally logs a service on the part coming off, e.g. “Re-wax”, since that’s usually why it’s being swapped. Optional extra: warn me when a second component of a type that’s normally single (chain, cassette, saddle) is installed on a bike, with a “Swap instead?” shortcut. This would help anyone rotating chains, wheelsets, tires or shoes. It pairs naturally with optional time of day on installs, so a mid-day swap is recorded accurately.
Can’t record a past service for a part that was off the bike on that date
I rotate two waxed chains, so I wax the off-bike chain while the other one is installed. Recording a service on a stored chain works with today’s date, but any past date between installs fails with “Failed to record service”. Expected: the service is accepted, at the chain’s mileage as of its last removal. Repro: take a chain with an install period ending 2026-03-04 and the next one starting 2026-03-10, and record a service dated 2026-03-05.
Component service/install needs a time component
As far as I can tell, you treat the Installation Date as happening at midnight, which means if I had a big ride, got home and swapped a part out I would have to specify “tomorrow” as the date, which you do not allow. Instead I must physically wait until tomorrow to record the install for the math to add up. Likewise, Service Date seems to be treated as 11:59pm. This means if I lube the chain before leaving the house, I have to remember to select “yesterday” to keep the maintenance interval accurate. Even worse is if I ride to the bike shop to have service done and then ride again afterwards that the same day (we have a DIY tool station so this isn’t uncommon!) - there’s no way to record that correctly. ProBikeGarage handles this by allowing the user specify the time in addition to date for service and component swaps. If you want to keep it backwards compatible, make the field optional and show the default it is using in each case.
Nuovo marchio bici.
È possibile inserire in elenco il marchio italiano “THOK”? Grazie
Note to a specific tour
Sometimes, I want to document a noise or something my bike make during a specific tour. Would make sense to be able to have a note or comment field for a Tour.
Add/remove components and/or rider gear per activity
The ability to add/remove manually an “In Storage” or an “Installed” component, rider gear or other stuff to a specific activity. Not install permanently, exemple, I’ve many shoes for specific rides on the same bicycle, instead of installing a shoe to a bicycle the counts for every activity I only chose that shoe for that activity only ou others in the future, that can be applied for specific components or other stuff. The same can be applied to “Installed” components or gear, exemple, on an activity I’ve had to change the wheelset, only for that activity. Then I just go to the activity, that has the list of components and gear I used and remove the wheelset and add other manually, but the defaults installed components and gear remains the same for the next activity. Kind of complex, don’t know it’s possible but useful when you are an athlete that constantly changes gear and components 😆. The alternative is to use Strava tags that can remove or add that gear, but that’s another topic…
Bike transfer with components — server-side deep copy to another user
Let me transfer a bike and its components to another user. Primary use: selling a bike. Secondary: forking a build someone likes. Server-side deep copy into the recipient's account; the transferred bike carries its accumulated distance as manual base distance and can then be linked to the recipient's own Strava account.
Combined service intervals
Be able to create one service intervals that combines several intervals. for example, a rholoff hub should have it’s oil changed every 5000 km or after one year, whichever comes first. It would be great if you could create one service interval that “triggers” on whichever of those happens first, and that you can record the service and thus reset both intervals in one action.