Planned
2Committed and queued
Anatomy handling of uppercase and lowercase modifiers
It would be awesome to allow Anatomy syntax to force uppercase or lowercase. Here is an example : {folder[name]:upper}_{task[name]:lower} It is already discussed here : - Enhancement: Add custom formatting specifiers for uppercase, lowercase, etc. in templates #739 | AYON Core
Check link dependencies when deleting
It would help a lot if AYON was smart about how everything in the pipeline was connected. For example when you delete a product it would be good if it could detect if that product is currently used in a project or not. “Are you sure you want to delete render v003, it is being used in animation v004” I know the node graph feature is visualizing all connections so it’s more a matter of making use of those connections in other places (for instance when you try to delete something). A right click function to view dependencies would also be helpful. Does not have to be node graph, a list of products copied to clipboard is also a good start.
Next up
Committed and queued
No Next up issues
In Progress
1Actively being built
Done
18Recently shipped
Show thumbnails in AYON pipeline tools
Show the folder thumbnails for the folder entries in the Folder Widget, making it how in the Launcher, Workfiles Tool, Loader, etc. Some prototypes: Additional references: Prototype PR: Show Folder thumbnails in Launcher, Workfiles tool, Loader in the Folder Widget. #1144 | ayon-core Issue: Workfiles: Create and Show thumbnails for workfiles #748 | ayon-core Forum post: Thumbnails for workfiles
See and open workfiles in Launcher UI
I suggest to be able to see and open work files in the launcher. Instead of being presented with different DCCs you will instead see the actual work files (see examples below) The current UI leaves a lot of guess work for the user since there are no way of knowing what work files have already been created previously. I know there are ways of limiting the amount of softwares shown for each specific task, but I still think there are better ways to do the UI to remove any guess work. Current UI 1. Better example (from AYON web) 2. Better example (from Prism) + Clear representation of all workfiles + Icon showing what software + Thumbnails + Artist comments
RV review workflow
Bundle per project
The Project settings allow configuration of addons for each project. But in some situations studio also need to alter the list of addons and/or their version per project. One specific and generic need is to "freeze" the addon versions for a project while still being able to upgrade addon versions for other projects, giving the opportunity to go back to a project using the set of features actually used while it was in production.
In the loader, make Hero selection easier
When Hero mode is OFF : artists can just load the product, no problem, they get the latest version. When Hero mode is ON : in the Loader, the default version that is selected is the latest version, and not the Hero version : Problem : if artists want to import a Hero, they need to manually select the [v] for each product they load (which can mean 4 or 5 textures, in the case of published Substance). If Hero mode is active, it would make sense to have it available easily in the Loader, which means force the Hero to be on the first position among the versions list. I think it would help avoid user errors, as we could ask users to not touch anything and just load. It is also discussed here : https://community.ynput.io/t/in-the-loader-make-hero-selection-easier/2537
Product aliases
In some situations, the product type is not enought to convey the purpose or usage of specific products. For example, in a 2D animation workflow, most of the product are Images. But there are different purposes for each task: Concept, Blocking, Polish... Users want to distiguish between these as much as between a Model and a Camera for example. Implementing a new Product type for each of these would give the intended result, but we need a solution available for non-developers. User Stories: As a Concept Artist, when I create a new Product for my task, I should be able to specify that the produced Image is a Concept Image. As an Artist, when I need to reference a Concept image, I need to be able to filter out all other Image product and see only Concept Image in the Loader dialog. As a CG Supervisor, when designing a production workflow, I need to be able to declare specialised product types conveying a clear and specific purpose without writing code.
Load menu : add sub-menus to group loaders
When we publish images (for example from Substance Painter), we use Ayon's OIIO to automatically provide several resized versions of the images. The Ayon Loader allows to choose which of the output images we want to load. But it displays it as a flat list, which can quickly become too long and difficult to read. Please provide sub-menu (see my screenshot and mockup gui), to group by load types, to greatly enhance the use of that gui. Already discussed here : Load menu : add sub-menus to group loaders #1132 | AYON Core
Project thumbnails
Our project sometimes have very weird names and after a few months it becomes hard to remember It would be great to have thumbnails for projects so you get an idea what it was about and can browse quicker Obviously this would be great in web browser, launcher, tray publisher… anywhere where you need to choose a project really
Set Product Status on Publish
To make it easier for users to set statuses it would be super helpful if the status of a product version could be set when publishing - I am thinking along the lines of two per instance attributes, one to set the status of the new version and the second to change the status of the currently existing version(s). So I want my new version status to be Pending review and the previous versions to be set to Omitted. This will also help with the status filters in the loader which hide versions based on status, so if you want to make sure all previous versions are excluded when Omitted is set to be hidden, all versions have to have their statuses changed manually, which is very tedious :(
Launcher folder creation does not respect capitalization of folders in webui
So our NAS has case sensitivity, I am using propietary tools to generate folders that support CamelCase formatting, the way that ayon creates folders on the disk when assets have CamelCase formatting removes any capitalisation except the first letter. Here’s an example of the asset HeroBranch being formatted to Herobranch to disk, my own tools will still create a HeroBranch folder and this will clash. Would be awesome if ayon can respect the capitalisation of entities completely from site to disk.


