Task Discription in the Launcher
It would be helpful to add a feature in the AYON Launcher that displays the task description. Ideally, users should be able to view a description for each individual task within the launcher interface. Use Case: This would improve task clarity for artists and developers by providing context directly in the launcher, without needing to switch to browser.
Alexey Volynets
Pipeline
Feature requests
Task Discription in the Launcher
It would be helpful to add a feature in the AYON Launcher that displays the task description. Ideally, users should be able to view a description for each individual task within the launcher interface. Use Case: This would improve task clarity for artists and developers by providing context directly in the launcher, without needing to switch to browser.
Alexey Volynets
Pipeline
Feature requests
Filter users by level and license
It would be nice to be able to click on various user level stats in the top bar of user management page and automatically prefill the filter by the value.
Lorenzo Basurto
Feature requests
Filter users by level and license
It would be nice to be able to click on various user level stats in the top bar of user management page and automatically prefill the filter by the value.
Lorenzo Basurto
Feature requests
New workfiles for softwares without addon
I really love the simplicity of the Tray publisher. Any file with any extension can be published and be a part of the pipeline. It would be great to add this simplicity to work files as well (but not using the tray publisher) * Creating addons for every software in every industry will be hard to manage and take very long time. * “Simple” softwares like Excel, Word, Powerpoint, Notepad etc is in need of a simpler approach than addons, since there is simply no way to develop addons for every single software *The simplicity of the tray publisher could be applied to workfiles as well and therefore open up possibilites to add any type of software to the AYON pipeline, also for workfiles. To solve this we need a new feature to create new work files based on pre-existing template files. Maybe this could be done with the interactive web action? Example User creates a new task in overview and with web action the user gets to choose if it wants to create a work file from pre-existing template (For example there might be 5 different Excel templates for different purposes) Once the template is chosen there will be a new workfile created on disk and also a new database entry. For publishing we could still use the tray publisher. This feature would open up a lot of freedom for the user to add softwares that does not have an addon and not necessarily need a fancy pipeline. Problems to solve * Versioning of the workfiles would need to be added somehow. Maybe as a right click feature on the current workfile.
Olle Rydberg
Pipeline
Feature requests
New workfiles for softwares without addon
I really love the simplicity of the Tray publisher. Any file with any extension can be published and be a part of the pipeline. It would be great to add this simplicity to work files as well (but not using the tray publisher) * Creating addons for every software in every industry will be hard to manage and take very long time. * “Simple” softwares like Excel, Word, Powerpoint, Notepad etc is in need of a simpler approach than addons, since there is simply no way to develop addons for every single software *The simplicity of the tray publisher could be applied to workfiles as well and therefore open up possibilites to add any type of software to the AYON pipeline, also for workfiles. To solve this we need a new feature to create new work files based on pre-existing template files. Maybe this could be done with the interactive web action? Example User creates a new task in overview and with web action the user gets to choose if it wants to create a work file from pre-existing template (For example there might be 5 different Excel templates for different purposes) Once the template is chosen there will be a new workfile created on disk and also a new database entry. For publishing we could still use the tray publisher. This feature would open up a lot of freedom for the user to add softwares that does not have an addon and not necessarily need a fancy pipeline. Problems to solve * Versioning of the workfiles would need to be added somehow. Maybe as a right click feature on the current workfile.
Olle Rydberg
Pipeline
Feature requests
Completed
Watchers
Hi There the Watchers features seems not working. there is no notification in the imbox about any change i made, like comments, deleting a folder, deleting a task….
Jacques Deschambeault
Production
Bugs
Completed
Watchers
Hi There the Watchers features seems not working. there is no notification in the imbox about any change i made, like comments, deleting a folder, deleting a task….
Jacques Deschambeault
Production
Bugs
Periodic Staging Directory Cleanup
A tool or AYON service to delete staging directories after a set period, such as a 90-day timeout. It can serve as an alternative to automatic deletions managed by cleanup plugins. This is idea was mentioned in some old discussion on discord. Just found it while I was cleaning up my notes.
Mustafa Zaky Jafar
Pipeline
Feature requests
Periodic Staging Directory Cleanup
A tool or AYON service to delete staging directories after a set period, such as a 90-day timeout. It can serve as an alternative to automatic deletions managed by cleanup plugins. This is idea was mentioned in some old discussion on discord. Just found it while I was cleaning up my notes.
Mustafa Zaky Jafar
Pipeline
Feature requests
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 :(
Shea
Community
Feature requests
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 :(
Shea
Community
Feature requests
Planned
Enable Partial Substring Matching in Overview Tab Search
Hi Ayon team, it would be great if the search functionality in the Overview tab supported partial substring matching—instead of only matching from the beginning of names. For example, if I type "ave" it should return results like "Waavel" where "ave" appears in the middle of the name. This would make searching more flexible and user-friendly, especially when users don’t remember the exact name start.
Marios Bikos
Production
Bugs
Planned
Enable Partial Substring Matching in Overview Tab Search
Hi Ayon team, it would be great if the search functionality in the Overview tab supported partial substring matching—instead of only matching from the beginning of names. For example, if I type "ave" it should return results like "Waavel" where "ave" appears in the middle of the name. This would make searching more flexible and user-friendly, especially when users don’t remember the exact name start.
Marios Bikos
Production
Bugs
Planned
Assignee defaults to Current User first
In the Web App, selecting the Assignee gives the user list alphabetically. But the first choice should be the current user.
Wei-Maverick
Production
Feature requests
Planned
Assignee defaults to Current User first
In the Web App, selecting the Assignee gives the user list alphabetically. But the first choice should be the current user.
Wei-Maverick
Production
Feature requests
Planned
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
Community
Feature requests
Planned
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
Community
Feature requests
Planned
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
Community
Feature requests
Planned
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
Community
Feature requests
Completed
1:1(square) Thumbnail size support
Is it possible to support square format instead of 16:9 for thumbnails?
Marios Bikos
Production
Feature requests
Completed
1:1(square) Thumbnail size support
Is it possible to support square format instead of 16:9 for thumbnails?
Marios Bikos
Production
Feature requests
Planned
Deeplink support for all tabs
Right now we can use an ayon url for browser and will highlight the entity found in url, but that does not happen for Tasks tab and Overview tab. Would it be possible to do the same for those? This works https://{SERVER URL}/projects/{Project Name}/browser?uri=ayon%2Bentity%3A%2F%2Fcatches%2FCatches%2FProducts%2Fp_diesel_2023_ss_m_a_jt_000 These don’t: https://{SERVER URL}/projects/{Project Name}/tasks?uri=ayon%252Bentity%253A%252F%252Fcatches%252FCatches%252FProducts%252Fp_diesel_2023_ss_m_a_jt_000 https://{SERVER URL}/projects/{Project Name}/overview?uri=ayon%252Bentity%253A%252F%252Fcatches%252FCatches%252FProducts%252Fp_diesel_2023_ss_m_a_jt_000
Marios Bikos
Production
Feature requests
Planned
Deeplink support for all tabs
Right now we can use an ayon url for browser and will highlight the entity found in url, but that does not happen for Tasks tab and Overview tab. Would it be possible to do the same for those? This works https://{SERVER URL}/projects/{Project Name}/browser?uri=ayon%2Bentity%3A%2F%2Fcatches%2FCatches%2FProducts%2Fp_diesel_2023_ss_m_a_jt_000 These don’t: https://{SERVER URL}/projects/{Project Name}/tasks?uri=ayon%252Bentity%253A%252F%252Fcatches%252FCatches%252FProducts%252Fp_diesel_2023_ss_m_a_jt_000 https://{SERVER URL}/projects/{Project Name}/overview?uri=ayon%252Bentity%253A%252F%252Fcatches%252FCatches%252FProducts%252Fp_diesel_2023_ss_m_a_jt_000
Marios Bikos
Production
Feature requests
Completed
Allow grouping of fields in overview tab
Similarly to how airtable does it, besides filtering it would be great to select “Group by …” and group the entities for a field
Marios Bikos
Production
Feature requests
Completed
Allow grouping of fields in overview tab
Similarly to how airtable does it, besides filtering it would be great to select “Group by …” and group the entities for a field
Marios Bikos
Production
Feature requests
Planned
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
a.xerri
Pipeline
Feature requests
Planned
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
a.xerri
Pipeline
Feature requests
Custom endpoints should have a fixed url
Current situation : Currently, paths to addon endpoints always contain the addon version, since all endpoints from all versions are always exposed. Example : http:// myserverayon:5000/api/addons/my_addon/0.1.2/get-test-data/myProjectName Problem : If we code a custom endpoint, to be used by other departments, we can’t tell them it’s a moving target, they need a fixed url, as in usual REST APIs. Because other departments can’t use self.version or similar, as the calls are done from other softwares. Proposal Please provide a “production" placeholder, that would replace the version. Example : /api/addons/my_addon/production/my_endpoint Context : It is also discussed here : https://github.com/ynput/ayon-backend/issues/494
a.xerri
Community
Feature requests
Custom endpoints should have a fixed url
Current situation : Currently, paths to addon endpoints always contain the addon version, since all endpoints from all versions are always exposed. Example : http:// myserverayon:5000/api/addons/my_addon/0.1.2/get-test-data/myProjectName Problem : If we code a custom endpoint, to be used by other departments, we can’t tell them it’s a moving target, they need a fixed url, as in usual REST APIs. Because other departments can’t use self.version or similar, as the calls are done from other softwares. Proposal Please provide a “production" placeholder, that would replace the version. Example : /api/addons/my_addon/production/my_endpoint Context : It is also discussed here : https://github.com/ynput/ayon-backend/issues/494
a.xerri
Community
Feature requests
Completed
Add thumbnail column in Overview tab
Would it be possible to have a column showing the thumbnail in Overview tab in same way you do it for Task Progress tab? So ability to allow thumbnail in view here As task view offers
Marios Bikos
Production
Feature requests
Completed
Add thumbnail column in Overview tab
Would it be possible to have a column showing the thumbnail in Overview tab in same way you do it for Task Progress tab? So ability to allow thumbnail in view here As task view offers
Marios Bikos
Production
Feature requests
Add Transcoding Options During Export in AYON for Hiero
In standard Hiero functionality, when exporting shots, there's not only the ability to create folder hierarchies and organize shots, but also to transcode frames into the desired format and colorspace: Currently, when exporting via AYON in Hiero — for example, working with.mxf files — we need to manually transcode the shots outside of AYON before publishing. AYON then copies these intermediate files into the correct structure, effectively duplicating the data. This creates issues, especially at scale. For example, exporting a film with 100+ shots to.exr results in around 10TB of unnecessary duplicated data — aside from the added manual steps and general inconvenience. It would be great to support format and colorspace transcoding directly during publish through AYON, so we can eliminate this intermediate step and avoid redundant storage usage.
Alexey Volynets
Community
Feature requests
Add Transcoding Options During Export in AYON for Hiero
In standard Hiero functionality, when exporting shots, there's not only the ability to create folder hierarchies and organize shots, but also to transcode frames into the desired format and colorspace: Currently, when exporting via AYON in Hiero — for example, working with.mxf files — we need to manually transcode the shots outside of AYON before publishing. AYON then copies these intermediate files into the correct structure, effectively duplicating the data. This creates issues, especially at scale. For example, exporting a film with 100+ shots to.exr results in around 10TB of unnecessary duplicated data — aside from the added manual steps and general inconvenience. It would be great to support format and colorspace transcoding directly during publish through AYON, so we can eliminate this intermediate step and avoid redundant storage usage.
Alexey Volynets
Community
Feature requests
Unified Launcher
Thanks to this post — it finally pushed me to take the time and share an idea I've been holding onto for a few months now: Right now, we have three separate dialog windows, each of which needs to be opened individually via the system tray. The first flow is pretty much the same in each: select a project, a shot/asset, and a task: Why not merge all three dialogs into a single unified launcher? This would reduce the number of required actions and bring all the functionality into one solid entry point. It would look something like this: 1. Workfiles tab Additionally, building on this post, I suggest combining the functionality of the "Working Files" tab with the "Launcher" tab (including Thumbnails). This way, the user can choose to either launch through a specific working file or go in via the selected software. 2. Browser tab 3. Publisher tab
Alexey Volynets
Community
Feature requests
Unified Launcher
Thanks to this post — it finally pushed me to take the time and share an idea I've been holding onto for a few months now: Right now, we have three separate dialog windows, each of which needs to be opened individually via the system tray. The first flow is pretty much the same in each: select a project, a shot/asset, and a task: Why not merge all three dialogs into a single unified launcher? This would reduce the number of required actions and bring all the functionality into one solid entry point. It would look something like this: 1. Workfiles tab Additionally, building on this post, I suggest combining the functionality of the "Working Files" tab with the "Launcher" tab (including Thumbnails). This way, the user can choose to either launch through a specific working file or go in via the selected software. 2. Browser tab 3. Publisher tab
Alexey Volynets
Community
Feature requests
Persistent Tool UI State
For the numerous tools that ship with Ayon - each one reverts back to it's default size, location and settings (mostly filters) in a new DCC instance. It would be helpful if the UIs had a persistent state between DCC instances so they didn't need to be moved, resized and have the same settings re-applied each time.
Shea
Community
Feature requests
Persistent Tool UI State
For the numerous tools that ship with Ayon - each one reverts back to it's default size, location and settings (mostly filters) in a new DCC instance. It would be helpful if the UIs had a persistent state between DCC instances so they didn't need to be moved, resized and have the same settings re-applied each time.
Shea
Community
Feature requests
Planned
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
Production
Feature requests
Planned
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
Production
Feature requests