Closed timsergeeff closed 1 week ago
Maybe we need to change "hooks" to "actions" not to rubbish logs or find a way to make kitsu addon expect "hooks" but it works logs is only issue
Do actions
in this context refer to launcher actions ?
For information, Here's an example of launcher actions: example https://github.com/ynput/ayon-applications/pull/12
From pipeline perspective, Do we actually want to change the status once a workfile is opened ?
I'd say that it's better to have that option rather than dont have because i have a ton of cases when i work with freelancers and they always forget to change statuses and if i dont have automatic timetracker (as i do right now) my options to track time are limited.
And I believe that opening a file wo doind any work happens less often than normal work so why we wouldn't prefer automatization 90% of a time? maybe better way is to implement similar checkerbox? "not change status"
This code should work for everybody because it uses just env variables and methods whitch i stole from neighbors sripts from kitsu addon
It's a good feature but in my opinion it shouldn't be the default. Someone might accidentally open a comp or something like that. If I'm not wrong this also executes on each open? That would quickly clog up the comments field on Kitsu. Maybe if nothing have bin published before, then change the status to wip.
Also, there really needs to be settings for this feature!
Yes this what I'll try to implement soon. And i have an idea of addissional logic: i want hook to check if loggined user have some other tasks in "wip" (comming from settings) and hook will send something like "pause" status to other tasks with "wip" so only one task at a time should be wiped
I'll do a separate PR with approriate tag
Changelog Description
Created a hook to make automatic status change to WIP In kitsu from any application start within kitsu connected task
Testing notes: