Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

sync with actions and task_actions already set #17

Open
vlimant opened this issue Feb 13, 2019 · 0 comments
Open

sync with actions and task_actions already set #17

vlimant opened this issue Feb 13, 2019 · 0 comments

Comments

@vlimant
Copy link

vlimant commented Feb 13, 2019

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant