Planned
31Committed and queued
AYON Chat
It would be great to have a built-in corporate chat in AYON. Ideally, it would include a full set of modern features similar to Slack or Rocket.Chat As an MVP, a chat with project-based channels could be released, featuring functionality similar to the Comments tab in the web version, including: Mention a user Mention a folder Mention a task Mention a version Attach images and videos
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
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
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.
Task Progress page to use new table
Use the new table in the task progress page so that we get all of the nice features we have in the overview page. - Column sorting, pinning, hiding/showing. - Lazy loading pagination. - Advanced filtering
Paste Image from Clipboard for Product Thumbnails
It would be incredibly helpful if we could paste images directly from the clipboard when setting product thumbnails, instead of having to manually upload a PNG file each time. This would streamline our workflow and make the thumbnail setup process much faster and more intuitive.
Planner Addon - Checkbox to include weekends or not
Currently if you plan out a month with an artist, it'll also count the weekend days. We're not monsters, so the ability to uncheck this would be awesome. The previous request for @Planner Addon - Copy and pasting of things would already help, so you can just clone a week across multiple weeks.
Add tasks and folders to existing review sessions
Currently you can only add versions to review sessions but this isn’t very intuitive. Because you can create a review session from a task or folder you should also be able to add task/folder versions to a session. As with creating new sessions, the version to be added would be the latest published version.
New Entity Redesign - Attributes and Templates
When creating a new entity there should be an option to fill out the description and attribute values whilst creating the entity. Improve naming input to be wider and support longer labels. Add expanded version that allows for setting description and attribute values. Advanced ability to create “template forms” of certain attributes to fill out with requirements.
Complex Filters
Add more filtering options with operators and nested conditions.
Next up
8Committed and queued
Time tracking
Allow production to track artist time on tasks with automated timer start, stop and context switching, natively in AYON
Email Notifications
Add options to notify users about AYON events via e-mail
Hide unwanted attributes in the UI per Project
Our attributes are scope to the whole AYON instance making it currently impossible to hide or ignore some of them on projects where they might be irrelevant. We should find a way to add come kind of project scope to attributes. This doesn't need to affect their backend accessibility on project entities, but hiding some attributes on specific projects would be very useful.
Per-bundle note or description
It would be handy to be able to type in a small text note or a description for a bundle.
Kitsu project Import
Allow new users to import their existing projects from Kitsu. This import should not be confused with an already existing Kitsu integration which allows to work on projects with Kitsu as production tracker, but is not meant for importing historical data.
Review - Ability to add a description to Review Invite, so a client sees what the invite is about
Would be great if, when inviting people to a review session we get a field with a title/message to describe what the review is about to send along in the invite email. Now people get a neutral email.
Advanced Mentioning
Expand the scope of mentioning in comments. Mention folders, tasks and versions outside of parent folder. Mention teams (groups of users). Mention relative entities, like all child tasks. Unified mentioning into one @ UI.
Planner: Duplicate Scenario
The “Duplicate Scenario“ feature disappeared from the planner frontend. I believe that was introduced in 2.0.0. In the “Schedule“ tab of a project that feature is still present tho. Would be great if we could duplicate scenarios from the project-agnostic “Plan“ tab. Could be this was removed on purpose. If so, what is the reasoning behind this? Thanks :)
In Progress
5Actively being built
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
Thumbnails Inheritance
It would be great to have thumbnails propagated across the entities hierarchy. In some scenarios from folder to its children, in other from version to its parents. Strategy The project's thumbnail, and each folder thumbnail is inherited by children. So at the beginning of the project, every entity shows the project's thumbnail. Inherited thumbnails shows an overlay of the entity type icon to mark that it’s inherited Product versions and workfiles don't inherit thumbnails. On any entity, the frontend gives the ability to set/unset a thumbnail. When set this way, this thumbnail is always the one to display and will not be overriden. When the pipeline publishes a new reviewable, it becomes the thumbnail for the related product version. In case of several reviewables, the main one is used. The frontend web player should give the ability to set a specific frame as the version thumbnail. If a Task has more than one product version, it shows the thumbnail of the last one which updated its status or was created. Stretch Goal Arbitrary thumbnail can be uploaded or use the thumbnail of another entity. Settings to introduce: Inherit thumbnail from parent (bool=True) Propagation of version thumbnail as task thumbnail (bool=True) Propagation of version thumbnail as folder thumbnail (bool=False)
Thumbnail Filmstrips
When hovering a thumbnail a preview of the latest version will be played back.
trackable variants
We would need an option to add variants from the overview and define ahead of time. -Example 01 Let say we’re working on a show with Dino’s We need multiple triceratops in a scene and we don’t want to have a 1 on 1 copy of them, that would look silly. I would like to have the same model and rig, animation cycles, but would like to have variants of the texture, maybe some have an extra scars, a little color variation etc. etc. I don’t want to create new tasks as they 3 variants we've are all so slightly different that if the client to decide that the overall color of the Dino should be slightly more brown instead of green we need to adjust 3 (in our case substance painter) files. Or if the model changes for some reason, again changing/adjusting 3 files So i just want to be able to adjust that one file and have a folder that we can manually turn on/off for the extra scars etc. etc. etc. We can to that right now at the publish and add a variant name, but we’ve no way to track it or define to the artist which versions we’ve need except for an note in the task. And textureMain and A can be approved but textureB maybe needs some small adjustments -Example 02 We’ve got a show with some “creative” comp shots. for some of these cases we already know that we need to create 3 versions of that shot which the client will decide later on which one will be finalized, this way again, we can have 1 nuke/aftereffects file where we can create the work in, but we can publish to the different variants to address feedback on just one particular version, we can omit the versions that we don’t need in the end. But we can (in the hopefully near future) track time on it, which will also be important. My suggestion would be a variant task. So a variant task you can only add to a task. You can name it, and have all the things setup in the overview. task progress, publish to it. (maybe don’t have someone assigned to it as you’re working from the same file that should be inherited from the mainTask But if you open a variant task from the launcher or the browser, you’ll just open the asset/shot from the parent task and no other project file will be created. I am aware that this can cause issue’s as you’re working in 1 work file, and can alter other versions if not careful (luckily we publish the work file along so we can always revert back) Maybe if variant are present we can have a popup when the program start that you’re working with variant in a single file. Also described here https://community.ynput.io/t/defining-product-variant-ahead-of-time/1368
Ftrack project import
Allow new users to import their historical data from Ftrack to AYON
Early Access
6Actively being built
Team assignments and mentions
Teams are currently substantially underutilised. They should act as users for all intents and purposes for @mentions, assignments and filter.
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
Reviewers
The ability to set a reviewer for a folder, task or version. Works very similar to assignee. This is most useful for delegating work that is reviewing of the work rather than doing the work. Reviewers would get notifications when added and then subsequent notifications on new events.
Annotations Type Text on Image
Hello, our VFX supe pointed out that they’re very used to typing text when annotating frames during reviews, but currently AYON doesn’t have a text tool. It’s different to typing in the comment, as it means being clearer about to which part of the image the text relates. And on a given frame multiple blocks of text might be required. They also mentioned being able to add arrow shapes to save drawing them.
Resource management
A secondary layer of data in Planner addon that will allow adding arbitrary resources to planned events and scheduled tasks. Licenses, personel, rooms, cats or dogs. This should include capacity planning and monitoring.
Review: Allow comment only to be attached to a frame
Currently a feedback note can only be attached to the timeline as a marker by drawing over a frame. But it would be very nice if the comment field would be able to write the note “to the current frame” or “globally” with a toggle on the comment field. When set to “current frame” (which would likely be the default setting then) it would attach the note to the current frame you’re on and also appear as a comment marker on the timeline. Bonus points: When in a synced session, if you start typing the comment then ‘lock’ the comment field to the frame it’s set to at that time - so that if e.g. someone else starts moving to another frame while you’re writing the comment you’re not affected by it. (Only workaround otherwise would be to open the review session twice, once synced and once unsynced using the unsynced version to place the comments.)
Done
80Recently shipped
Planner and Scheduler
Plan out your production from rough estimates, down to subtask level. With AYON planner you can create and track project phases, studio holidays, artist bookings and deadlines. On the project level you can create multiple scenarios and when you’re ready, mark one of them as live, so the rest of the studio is always up to date. Studio Plan Project schedule
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
CSV Roundtrip
Some Producers use external services or in-house solutions to manage production steps like breakdown, planning scenarios, reporting... Using AYON should not be in the way of that. User Stories As a production coordinator I want to create many assets in AYON based on my excel sheet As a producer I want to export my filtered view from AYON to excel. As a producer I need to quickly modify a lot of information on all entities and I'm more comfortable with excel.
Entity templates
Store any part of AYON hierarchy and re-use it in other places. - Set of tasks for a lead character - Starting project folders
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.
Organise folders in the Overview
Sometimes you may want to change a task or folders location in the project because things have changed or it was created in the wrong folder. Add the ability to move the folders location: Right click menu that lets you pick which folder to move it to. Drag and drop the folder to the new location.
Analytics and Reports Dashboard
A bird’s-eye view of your projects, with powerful graphs and customizable dashboards. Track progress, dig into detailed stats like tasks completed and versions published, and generate shareable reports for your team or clients.
Products Browser redesign
A versatile browser for AYON products and their version. Users can comment, change statuses, run addon actions, open the versions for review and categorise.
Project Overview Page
The best way to manage the whole project. You can create and manage project hierarchy, assign tasks, change attributes and navigate through your project in a robust and familiar way.


