When adding a workout to the calendar, I find the filtering and sorting options VERY limited. I think it would be useful (and relatively easy) to create better filters. For example, I’d like to see all workouts between X and Y duration, and between X and Y TSS or between X and Y intensity factor. The current filters often leave me paging and paging through workouts because, unlike people who have used TR for years, I don’t know the names of many workouts by heart.
But an even easier thing to implement, which would probably cover 80% of my needs, is the ability to sort the results. I think right now all results are always sorted alphabetically… but I find no value in that. I’d like to sort by IF, TSS, or duration. Adding that single sorting selection would be fantastic and make finding the right workout MUCH easier.
I mostly use the calendar on the web. I see basic (checkbox-type) filtering options by Zone, Duration, Intensity, Intervals, Instructions, Workout Type, Custom, and Teams. But I don’t see ANY sorting options there.
If you search through the workout tab, instead of through the calendar, you can sort by IF, calories, duration, TSS, newest, or name. You can then add the workout to your calendar from the workout tab as well, once you find what you’re looking for.
@ajochen nailed it. Sorting is available via the workouts tab on the left, but not when adding a workout from the calendar.
So, the calendar has crippled functionality. I now would say that adding this to the calendar is EVEN MORE important. Since the calendar is touted as the center of the TR experience, and seems the logical/intuitive place to add my workout, I’d never have found that on my own if I hadn’t posted here!
Yes, but I didn’t analyze the link at the top very closely to see it was pointing to the workouts tab, so I missed that part. I saw that you had a sorting option available on those screenshots, but I couldn’t see that on my screen no matter what I did to the calendar.
I don’t have a separate list, but yeah… there are likely hundreds of feature requests if you really poke around. It’s one reason getting one done is a challenge, pure tracking prioritizing is a the first step and then acting on it… and so on.
@Joelrivera you can also file a support ticket. They happily take them, and it might make it one step further, into an internal bug/feature tracking tool that is easier to wade through and manage than a forum thread. Or it gets tossed and you get a thank you in both cases, and you’re none the wiser.
AFAIK, all “requests” end up in the same system on the TR side. That is what I understand at least. Ivy (and Bryce before her) watched this category (and the “feature-request” tag) and usually acknowledged the idea and passed it along into whatever system they have.
One thing Nate mentioned about liking the forum for this purpose is to discuss the main request, possible alterations and other considerations. That isn’t required, but is lacking when requests go through the other avenue. At least it doesn’t get the “public” discussion, but it likely does for the internal TR process either way.
Indeed, it is short, and no “official” TR rep here. I saw several threads about searching workouts, with slightly different aspects. Likely, I should merge some or all of them because they are very closely related.
Thanks for the bump! We are definitely working on some better visibility to filter by type for workouts that will help with this tons.
I think to speak to ‘low hanging fruit’, it’s important to acknowledge that there are so many good ideas that we’d like to add when considering feature requests internally. Ultimately, we have to prioritize these ideas based on how impactful they are to all of our athletes, and sometimes that means deprioritizing (or sometimes passing over a good idea), that IS good, in order to spend our development resources on something that will be more impactful immediately in helping athletes get faster.
Hope that context helps a bit. We’ve had a good winter (in terms of development) and we’re going to expand the engineering team over the next couple of months to help implement the ‘low hanging fruit’ feature requests.