A task doesn't disappear from the system cause the client can see reports and graphs using obsolete information. So, adding a new boolean field we can define what task is available (active: true) or unavailable (active: false).
If a new feature needs an activated task, could be add Task.actives to list only tasks that been marked as activated. This isn't enough, I had to override the destroy method to just update active field to false instead remove it from database.
A task doesn't disappear from the system cause the client can see reports and graphs using obsolete information. So, adding a new boolean field we can define what task is available (
active: true) or unavailable (active: false).If a new feature needs an activated task, could be add
Task.activesto list only tasks that been marked as activated. This isn't enough, I had to override the destroy method to just updateactivefield tofalseinstead remove it from database.Related to #15.