You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
the "action" collection was meant to contain unique action, where unique defines all parameters of the action + sites used (or set to "manual").
These "predefined" actions can be used to set "on-going issues with ..." that the user does not have to define over and over and just apply to various tasks.
as such, they should be loaded with the page, and displayed (maybe using the "reason" field as a short name) possible actions to be applied to available tasks.
all non-acted task_action should be also loaded in the console and displayed as such, with the "action" (see above) and the "applied to tasks". the corresponding cell in the table should have a different color, or a marker that says "there is an action already for that task".
the console should reload every once in a while (5min?) the actions and task_actions for refresh and stay on top of things.
last, it looks like a careless user like me, pushing the submit button twice (#11) would set two actions and task_action in the db ; these should be updated if already existing (upsert=True in pymongo) and not already acted on (acted=0), once they are acted=1, they should not be updated
The text was updated successfully, but these errors were encountered:
the "action" collection was meant to contain unique action, where unique defines all parameters of the action + sites used (or set to "manual").
These "predefined" actions can be used to set "on-going issues with ..." that the user does not have to define over and over and just apply to various tasks.
as such, they should be loaded with the page, and displayed (maybe using the "reason" field as a short name) possible actions to be applied to available tasks.
all non-acted task_action should be also loaded in the console and displayed as such, with the "action" (see above) and the "applied to tasks". the corresponding cell in the table should have a different color, or a marker that says "there is an action already for that task".
the console should reload every once in a while (5min?) the actions and task_actions for refresh and stay on top of things.
last, it looks like a careless user like me, pushing the submit button twice (#11) would set two actions and task_action in the db ; these should be updated if already existing (upsert=True in pymongo) and not already acted on (acted=0), once they are acted=1, they should not be updated
The text was updated successfully, but these errors were encountered: