Feature Request / Enhancement: Completion State Sets

[pxlnic]

I have been playing around with Habit Beaver and overall really like the feature set this has to offer. One thing that is tedious though is setting the completion states for notes. One thing I thought would be handy would be to have "sets" of completion states at a global level that you can set for a habit.

i.e. my default set would look like the one below that would apply to all my habits by default:
- [yes:teal] [no] [skip:amber #skip] [failed:red #skip]

But I may want to set a different one for when I play games:
- [my game:teal] [with fam:purple no]

Being able to declare these as a set instead of having to always punch it in each time is very tedious. Just an idea I had to make things a little more efficient on setup, and if you ever decide to change a standard set you use across multiple habits it would take less time and be less prone to mixups.

[daya0576]

Thanks for the suggestion, I see your point — making the completion states reusable across habits.

Do u mean having a place to define custom status sets (e.g. skip:amber #skip), so that if you update one, the change applies everywhere it's referenced (multiple habits)?

[pxlnic]

I think so. Having a page to setup a custom status and a set of statuses would also be nice. For me I will mostly use the four options I posted in the first part of the issue (yes, no, skip, failed), and would like to save that set of 4 statuses to reuse.

It would also be nice to define the individual custom statuses to reuse though to. i.e. [yes:teal] as a custom status and [skip:amber #skip] as another. And then I can put those into a custom set of statuses that I name "default" (or something along those lines).

To boil it down I'm thinking two functions:

1. Custom status: i.e. [yes:teal] or [skip:amber #skip]; AND
2. Custom status set: i.e. "Default Set" = ([yes:teal] [no] [skip:amber #skip] [failed:red #skip])

That way I can choose from the custom statuses individually or choose a custom SET of statuses to use.

Sorry. That was a bit wordy. Was trying to figure out how to be articulate it. Hope that makes more sense.

[daya0576]

Thanks for the detailed explanation @pxlnic

I've implemented a configuration page for both default completion status and custom completion status (mapping). You can check it out on the demo page: https://beaverhabits.com/gui/completion-status

Feel free to share any feedback.

---

Typo: https://beaverhabits.com/gui/completion-status -> https://beaverhabits.com/demo/completion-status

[daya0576]

1. Default completion status — You can define a global default set (e.g. yes, no, skip, failed) that applies to all habits automatically.
2. Custom completion status — Define custom statuses globally (e.g. skip:#amber #skip), which override the default ones.

This adds quite a bit of complexity — let me think on it a bit more...