We love your Feedback!

Please tell us how we can make AYON work better for you. You can also report bugs or ask questions if our Help Portal is not helping.

If you’re looking for developer resources, you can find all of them on our Developer Portal

Tray Publisher - CSV ingestion

When publishing a csv - which was made as yuou suggest, I’m getting this error. Traceback (most recent call last): File "/home/luciano.cequinel/.local/share/AYON/dependency_packages/ayon_2502101346_linux-rocky9.zip/dependencies/pyblish/plugin.py", line 528, in __explicit_process runner(*args) File "/home/luciano.cequinel/.local/share/AYON/addons/kitsu_1.2.7/ayon_kitsu/plugins/publish/collect_kitsu_entities.py", line 51, in process kitsu_entity = gazu.entity.get_entity(kitsu_id) … File "/home/luciano.cequinel/.local/share/AYON/dependency_packages/ayon_2502101346_linux-rocky9.zip/dependencies/gazu/client.py", line 303, in check_status raise ParameterException(path, text) gazu.exception.ParameterException: ('data/entities/sequence', 'Malformed ID.')

Luciano Cequinel

πŸ›

Bugs

Feature Request: Pinned Comments & Threaded Replies in Task Activity Feed

Summary: I’d like to propose two enhancements to the comment/activity feed section in AYON’s web task view: Pin Comments β€” ability to pin one or more important comments to the top of the activity feed (e.g., briefing notes, important decisions, client feedback). Threaded Replies β€” ability to reply directly to a specific comment in a thread, keeping conversations organized and contextual rather than a flat list. Current Behavior: The activity feed currently shows comments in a flat chronological list. There’s no way to group related replies under a parent comment, or highlight critical comments for visibility. AYON does support Comment Categories for visibility control, but there’s no threading or pinning mechanism. Problem This Solves: In a busy production task with many comments from artists, TDs, supervisors, and clients, it becomes very hard to: Track which reply belongs to which discussion point Keep important notes (like a brief or approval status) visible without scrolling Proposed Solution: Add a β€œPin” icon on comments (visible to users with sufficient permissions) that anchors the comment to the top of the feed Add a β€œReply” button on each comment that nests responses under it in a collapsible thread, similar to Slack threads or Discord replies Use Case Example: A supervisor pins the shot brief at the top. Artists reply in threads to specific feedback comments. The feed stays clean and everyone knows what’s actionable. Who Benefits: Studios with large teams, review pipelines, and client-facing workflows β€” especially when combined with the existing Comment Categories feature. I’m happy to discuss further or provide mockups if helpful. Would love to know if this is on the roadmap!

#youssef#

πŸ’‘

Feature requests

More standard available Variables

We need to have more available variables for in the pipeline. Like current Folder name (like shotgrid has shot, sequence, etc etc) For most programs, like houdini, nuke, maya etc you can get around it with getting the β€œAYON_FOLDER_PATH” split it in ptyhon and source what you need. But again, not artist friendly, an β€œAYON_FOLDER_NAME” or parent folder or even shot/ sequence etc would be really helpfull. But for let say something like OCIO witch is just a YAML and can’t do any splitting, it’s now impossible to setup a proper OCIO config with show/ shot luts. The only way to use this now is create your own custom pre-launch hook. But this can be problematic, or cumbersome if you want to use the Batch deliver etc. And this is such a massive basic feature to be able to configure your OCIO that this shouldn’t have to be done by manually creating custom pre-hooks etc.

robert okker

6
πŸ’‘

Feature requests