Introduce New action in Workfiles tool when switching to different context to streamline the workflow

[LiborBatek]

Is there an existing issue for this?

• I have searched the existing issues.

Please describe the feature you have in mind and explain what the current shortcomings are?

Currently there is no way to navigate and switch to different context via Ayon > Workfiles without need to first open existing workfile.

There should be new action called e.g. Switch context or similar to just set current context using selected hierarchy folder/task in the left panes and without a need to open any workfile.

Could be located close to existing action (marked in green)

Users should benefit from it heavily saving time without need of opening existing workfiles switching context rapidly.

How would you imagine the implementation of the feature?

Introduce button for Switch Context or similar in the UI of workfiles.

Are there any labels you wish to add?

• I have added the relevant labels to the enhancement request.

Describe alternatives you've considered:

No response

Additional context:

No response

[BigRoy]

This actually existed originally back in Avalon - but was removed due to it being very technical and prone to the user doing very odd stuff, like having a workfile open, switching context, not saving at all but still publishing.

For context - initially Avalon had a "context switcher":

• Fix context manager allowing to switch to 'No Task' getavalon/core#451 (comment)

And then later the 'context switch' got merged into the workfiles tool:

• Merge Context Manager + Work Files (Fix #412) getavalon/core#442

I vaguely recall even @mkolar being involved in deciding some of that removal.

The only thing I can think of is adding an entry somewhere that says "New", as in... "start a new file in that context" which would force a new scene and then switch context - however, we do not have any "New scene" function the on IHostAddon so we can't do that generically currently.

A potential nice thing about having a "New" button is that it could open doors to it e.g. allowing options like:

• New: Build From Template
• New: Empty workfile

[iLLiCiTiT]

☝ I do think that New is something we actually need. It could be new method in IWorkfileHost (somehow). @LiborBatek do you think it would resolve the issue? If yes we could change the issue title and description, because I think that would get more traction...

[LiborBatek]

@BigRoy "New" action sounds also useful

Speaking of that "Switch Context" action...I see what issues it could bring to the table (thanks for explanation!) ...so how about to perform "Scene Close" so user cant keep the active workfile open to screw things up?? Or other way to force him to do so...e.g. Warning Message that he might need to close active workfile first?

..and I can imagine it would sit right in the AYON menu too (that "Switch Context" action) to be more accessible too

@iLLiCiTiT I think it do not resolve this issue...should probably stay as is (Issue title) and we should create another issue/feature request imho, thx for your thoughts!

[BigRoy]

Speaking of that "Switch Context" action...I see what issues it could bring to the table (thanks for explanation!) ...so how about to perform "Scene Close" so user cant keep the active workfile open to screw things up?? Or other way to force him to do so...e.g. Warning Message that he might need to close active workfile first?

It's totally fine to save an active workfile to another scene - we do it all the time at Colorbleed. (Maya integration for example even have prompts when saving into another context?)

Or what do you mean?

Why would you "go into another context" as an artist without new scene AND without the current file?
The only thing we're really lacking is 'starting a new scene' in another context - which is usually solved by just pressing CTRL+N in a host and then save to another context. Quirky? Maybe, but huge problem? Most often it isn't?

[LiborBatek]

@BigRoy @iLLiCiTiT yeah, you are right...so it makes sense to rename this issue and incorporate the Create New action besides the existing ones then...