Add support for per-user saved progress

Thank you for the request, @nicxvan. This is a feature I've had on my "someday/maybe" list for a while. It would involve some significant architectural changes, so it's probably something for a 2.x branch; and I don't foresee getting to that soon. I haven't tried it myself, but the Checklist module might actually be geared more toward your use case. I hope that helps.

I think what I am looking for might fall under this issue. I am looking to allow site visitors to create goals, which can then be displayed as a checklist. The checklist module allows admin to create a checklist that a user, all users, or a group of users can complete (individually or as a team), but I am looking more for a user to set up a big goal, then add checklist items that help them track the progress of that goal.

Is that something that is outside of the scope of this module or for your future plans?

This is a distinctly developer-oriented module, because it requires custom code to implement. I don't foresee it evolving to meet your proposed use case, I'm afraid. That feels like the job of another solution. I hope you find what you need to make it happen!

Actually the patch to add field support in #2056411: Attach checklists to entities as fields should allow the field to attach to any entity type. So it should just be a matter of adding a 'Checklist' field to users at admin/config/people/accounts/fields.

Setting to 'needs review', since it can probably be closed by the aforementioned patch.

Actually, the intent of this issue as I understood it was not to add checklists to user entities but rather to have checklists as they are now which each user can complete and have their progress tracked individually. For example, a "Get started with this website" checklist that every new users completes independently.

Right, I get that. Attaching a checklist field to a user will save the checklist progress individually for each user. If you want to make it available from a menu item, rather than the account page, you can simply set the field display to 'hidden', then build a view that'll display that field for the currently logged-in user. I'm certain there are other ways to accomplish this too, but this one is dead simple. See attached example view.

Oh, I see what you mean, @ergonlogic. That's a great idea. Closing in favor of #2056411: Attach checklists to entities as fields.