Skip to main content

Planned

27

Committed and queued

Feature requests

Thumbnail Filmstrips

When hovering a thumbnail a preview of the latest version will be played back.

Luke Inderwick
Feature requests

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

Alexey Volynets
Feature requests

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.

sjt-rvx
Feature requests

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.

Olle Rydberg
Feature requests

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.

jonathan.hearn@ajptechnical.com
Feature requests

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.

Dieuwer Feldbrugge
Feature requests

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

Marios Bikos
Feature requests

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.

Marios Bikos
Feature requests

Lists: Separate context menu list for review sessions

When right clicking on a version and going to “Add to list” the review session lists are also included which can be confusing and messy. It would be better to have a new menu called “Add to review” that would list just the review session lists. It could also have a “New review” button at the bottom to create a new review session.

Luke Inderwick
Feature requests

Complex Filters

Add more filtering options with operators and nested conditions.

Milan Kolar

Next up

10

Committed and queued

Feature requests

Time tracking

Allow production to track artist time on tasks with automated timer start, stop and context switching, natively in AYON

Milan Kolar
Feature requests

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)

Milan Kolar
Feature requests

Email Notifications

Add options to notify users about AYON events via e-mail

Milan Kolar
Feature requests

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.

Milan Kolar
Feature requests

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.

Luke Inderwick
Feature requests

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

robert okker
Feature requests

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.

Milan Kolar
Feature requests

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.

Luke Inderwick
Feature requests

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.

Dieuwer Feldbrugge
Feature requests

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.

Luke Inderwick

In Progress

5

Actively being built

Feature requests

Team assignments and mentions

Teams are currently substantially underutilised. They should act as users for all intents and purposes for @mentions, assignments and filter.

Milan Kolar
Feature requests

Review: Providing a publically accessible Share link without having to use emails

Often when dealing with clients they might want to have random people rally around a review session. Being able to have single link from which Guests can join ( probably password protected ) without having to fill in every viewers email would be very helpful.

Dieuwer Feldbrugge
Feature requests

Ftrack project import

Allow new users to import their historical data from Ftrack to AYON

Milan Kolar
Feature requests

Make feedback/notes collectable/filterable/sortable

When working on big projects with directors who type in a lot of feedback in review sessions its nice to have a simple overview of all comments that have been made on a playlist, or even on a whole project, to sort/collect them and then go through them one by one. I see there’s the “Export review session feedback” idea already, but I’m talking about a seperate page/filter that can do this for a project/task/list to all comments it finds.

Dieuwer Feldbrugge
Feature requests

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 :)

Tony Dorfmeister

Done

49

Recently shipped

Feature requests

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

Milan Kolar
Feature requests

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.

Milan Kolar
Feature requests

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

Milan Kolar
Feature requests

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.

Luke Inderwick
Feature requests

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.

Milan Kolar
Feature requests

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.

Milan Kolar
Feature requests

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.

Milan Kolar
Feature requests

Entity lists

Entities are hierarchically organized to reflect production grouping. Task entities are grouped by Status in the Home Tasks Kanban, or other property in the Home Tasks list. But in some situation the user needs more complex or even arbitrary grouping of entities: dailies, shots to sync between sites, versions to deliver, ... In this situations the entities that share specific characteristics, are often ordered together, and some actions can be performed on them. Entity lists allow creating and storing arbitrary selections of entities without altering their actual place in project hierarchy

Milan Kolar
Feature requests

Sub Tasks

Sub-tasks are lightweight work items that live within a main task. They are designed to streamline workflows without the complexity of creating full tasks. Each sub-task will contain the following: Label (Required): The name of the sub-task. Assignee: The user responsible for the sub-task. Dates: Start and due dates to help with scheduling. Completion: A simple checkbox to track status. Sub-tasks will be introduced as a premium feature, bundled with the Planner & Scheduler Addon. This functionality will provide users with the ability to create split schedules for a single task, offering greater granularity and control over their project timelines.

Luke Inderwick
Feature requests

Project Overview Page - Show Count

Show the number of selected items in compliance to windows explorer. Show the number of rows in compliance to spreedsheets or excel.

Mustafa Zaky Jafar