Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request] Vehicle-specific reminder urgency thresholds #477

Open
barstown opened this issue Apr 8, 2024 · 3 comments
Open

[Feature Request] Vehicle-specific reminder urgency thresholds #477

barstown opened this issue Apr 8, 2024 · 3 comments

Comments

@barstown
Copy link

barstown commented Apr 8, 2024

Checklist

  • [X ] I have read and tried the steps outlined in the Troubleshooting Guide
  • [X ] I have searched through existing issues.

Description
From Issue #124:

The reminder becomes "Very Urgent" when it has less than 7 days to due date or less than 50 miles to the target odometer reading, so you'd have to intentionally ignore it for it to become past due.

Reminders change their urgency status at set intervals that are not user configurable. This seems to work okay for reminders that have longer intervals, but for reminders that have a short interval time those tasks are perpetually "very urgent" or "urgent."

As an example, I set up a farm tractor as a vehicle on your live demo website and created a reminder entry for "Grease fittings." My tractor requires that I grease them every 10 hours. When I create a service entry or select the "done" button for that item it resets and updates the hours correctly, but the task remains "very urgent." For this specific task, I'd probably set my urgent state to 5 hours and the very urgent state to 8 hours or so.

Another example, I created a vehicle for my lawn mower which recommends oil changes every 50 hours or annually. Same concept here, I had a task that repeated after 1 year or 50 hours, and when I added the service entry for it the fields all updated appropriately, but the reminder reset back to an "urgent" state. For this specific task, I'd probably set my urgent state to 35 hours and the very urgent state to 45 hours since I don't accrue hours on my mower all that fast.

If you made Reminder urgency configurable per entry, that'd help get some of these short tasks out of the higher urgency state. Alternatively, maybe changing how it determines that state to be percentage based on the interval time could be an improvement? At 50% past the interval time it becomes urgent and at 80% it becomes very urgent? I'm flexible here, but I've seen that you said the Reminders page has a lot of interaction with other pieces so I'm not sure how feasible this is.

@barstown barstown changed the title [Feature Request] [Feature Request] Reminder urgency status based on interval percentage or user-configurable values Apr 8, 2024
@hargata
Copy link
Owner

hargata commented Apr 8, 2024

Not at a per entry level, but the urgency thresholds are configurable app-wide. Available as of 1.2.5, please see #366

@hargata hargata closed this as not planned Won't fix, can't repro, duplicate, stale Apr 8, 2024
@barstown
Copy link
Author

barstown commented Apr 8, 2024

I had missed that, and that looks really helpful. I don't see that on the demo site, but I recognize that certain things may be disabled there.

Would you consider making the reminder thresholds be vehicle-specific in the future? That's still going to present a similar issue, but now the opposite. If I tailor it for my equipment with frequent maintenance items, my truck's reminder urgency thresholds will be skewed now as well.

@hargata
Copy link
Owner

hargata commented Apr 8, 2024

Sure.

@hargata hargata reopened this Apr 8, 2024
@barstown barstown changed the title [Feature Request] Reminder urgency status based on interval percentage or user-configurable values [Feature Request] Vehicle-specific reminder urgency thresholds Apr 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants