option to choose categories of tasks

[schollii]

I would like to propose that each task could be skipped / postponed, or that categories of tasks could be opted in/out. Reason being that if you are focussing on one type of technology say kubernetes, but you don’t know ansible, then you don’t want to do ansible tasks now; you will do them later when you have taken the Ansible course.

Two ways this could be presented to us:

• Each task has, in addition to the current Go button, a Skip or Postpone button. At the top, you would have an additional circle for number of postponed tasks. They would come back eventually as done currently.
• Even better way: in your settings you could have ability to toggle which categories of tasks you want. Some categories could be kubernetes, ansible, puppet, git, networking, docker, etc. Eg for me right now, I would disable ansible and puppet because I don’t know them and I want to get through my kubernetes training. Eventually once I have completed the ansible course, I would enable Ansible (but I might leave kubernetes category on, or not, depending on my focus).

[iamfredrickokereke]

Hello, @schollii your observation and request are amazing, Thanks for sharing. I did notice that these are factored in:

• The Profile setting has an option to add a personalized learning path subject/technology for practice, see below:
  

• Skipped tasks are also seen as expired, which reflects on the task board with a status count, also these tasks are eventually been reassigned back again.

• Considering there are different phases of the program, which are largely dependent on growth and performance, each task precedes or is level-based.

Please help clarify again, if your issues were unresolved.

[schollii]

The profile box is just a text box, it does not affect what tasks get assigned to you.

There are no skipped tasks. There are only pending, incomplete and completed tasks:

The only way to skip a task is to start it, and once you can see the task instructions, click Finished instead of End Later. Then it is actually marked as Failed, and I have to wait another 1 or 2 days before getting another task, this wastes a lot of time.

Within the devops level, there are several categories of tasks: git, docker, puppet, ansible, kubernetes, and I'm probably forgetting a couple. I'm saying there should be a setting in my profile where I can indicate that in the devops level, I only want git, docker and kubernetes tasks (as an example; someone else might just want puppet and ansible tasks).

In the sys admin level, tasks were fairly basic so I don't think the above is really necessary, but if that makes the feature easier to implement, that's fine too.

[mmumshad]

Thank you for your recommendations and the details. You are right. Currently we do not take users interests into consideration while signing tasks. Originally we didn't have enough tasks to do that. However with over 200 different types of tasks and counting, we can now do it. We are working on multiple improvements to the platform as of now and will consider implementing this feature. Adding a skip feature should be easy and can be done soon.

[schollii]

@mmumshad if you use the "skip" approach (rather than the settings), then it would be ice if when you skip, you immediately (or within a few minutes or max an hour, say) get another task, rather than having to wait for another day or 2 as happens when you purposefully fail a task to ignore it.