Status change on user action

[timsergeeff]

App start status change

Now we have ability to change status on users starting app action.

Pause other tasks with WIP status

We can turn off pausing all other WIP tasks. This logic made of state: only one task can be WIP at a time.

Farm render status change

Previosly task was getting status change (WFA) only at publishing state in deadline so in between of publishing job to farm and publishing to kitsu we have nothing indicating current task status. Now we have FARM status change when farm rendering is on

Additional info

The settings allow to configure status change conditions so statuses will not double. And some other changes to settings needed to be done to make all logic work and ahve opportunity to swith in on or off

Testing notes:

1. Add nessesary statuses to your kitsu production
2. configure status changes in addon
3. mark some statuses in kitsu as WIP (only for test)
4. start other task
5. see all other tasks now was PAUSED
6. publish a job on farm
7. see status change to FARM status

[timsergeeff]

I have doubts about code style and some decisions i've made to make it work, bot it works now help me please to make code and logic pretty please) Hope you like it!

[MustafaJafar]

could you create an issue for your enhancement request/suggestion and link it to this PR ?
https://github.com/ynput/ayon-kitsu/issues/new/choose

[MustafaJafar]

I didn't test run the PR yet.
I'd recommend adding settings in multiple places. so that we have them near to each other so that we know that these settings belongs to the same feature.

[BigRoy]

@timsergeeff could you please install a linter for your IDE that matches the code style of the repo, mostly PEP08. There's a lot of invalid blank lines.

Also, a spell-checker may also help since the log messages contain typos.

[BigRoy]

Filename has a typo cahnge -> change

[timsergeeff]

ohh sorry will fix

[timsergeeff]

i dont undestand how to remove this

and from previos PR there was a comment i think from @BigRoy that we may be dont need this

[BigRoy]

I really don't understand this use case - why would launching a task pause all other tasks? :/

[timsergeeff]

I had a ton of situations when artist started a task and then switched to another and mark it wip resulting in two WIP tasks at the same time and it makes tracking of production confusing and harder to make nessesary desigions fast

[BigRoy]

I had a ton of situations when artist started a task and then switched to another and mark it wip resulting in two WIP tasks at the same time and it makes tracking of production confusing and harder to make nessesary desigions fast

It's interesting - because on our studio for example it's quite common for someone to do that (usually working on a few smaller tasks at once) and they'd basically open both and sometimes do a bit in one, then some stuff in the other almost simultaneously. For smaller tasks though where usually waiting needs to happen in-between (e.g. test-rendering, etc. and then continuing with something else while the test render is occurring in the background). Both tasks being active then is the logical state.

Anyway... will leave the "production scenarios" reviewing of this to others. @dee-ynput

Also, something tells me we should be setting this statuses TO AYON - and then sync to all the others or whatever so we don't need to duplicate this logic for kitsu, shotgrid, ftrack, etc. but have on entry point in the code to do this - no matter the production tracker integration. But maybe I'm too hopeful.

[timsergeeff]

@MustafaJafar i think i cant connect pr with issue because of rules of repo