Asset and Shot Tables

There doesn't seem to be a really practical way to create an API key with more specific conditions. The current system, in which the bot is given the role of a human user, seems too restrictive to me. For example, if I want to set up a bot in 'read only' mode, there seems to be no way to do that (if I understood correctly). Currently, I can assign him the role of “artist” to limit his permissions, but he still has the ability to publish content and change certain statuses. Likewise, for the role of “salesperson”, I must assign each task to the bot individually to ensure the necessary visibility. The ideal would be to have a “read-only” option, or better, to be able to define specific conditions (for example: permission to read notes, download files, etc.) Thanks!

Currently it appears that comments on video entities are sorted chronologically by date/time posted. Where comments have a timestamp added (by using @frame or the toggle on client views), it would be useful to be able to sort by this frame number, so comments appear in order based on playback. We've had some cases where multiple reviewers leave comments at different times, or may leave comments on subsequent playthroughs, meaning the comments are out of order.

Similar to how annotations appear on the timeline in playback on video entities, it would be useful to have a coloured marker appear on the timeline when a comment has been added with a timestamp (using @frame or the toggle in client view). This would help identify during playback where comments have been left.

Right now, project URLs contain the project ID and not a readable name of the production itself. Could a more readable slug be implemented to make the URL more user friendly, especially when sending out the link? Thank you! https://docs.short.io/articles/useful-articles/what-is-a-url-slug

I'm using the breakdown function for the first time and I would like to get an overview or a trigger for the person who will prep the shots when the background is done. So a list or a trigger for the shot task "scene_prep" when the background for that shot is done. I tried using the automation, but it does not go from asset to shot. I can see the cube turning green in the shotlist, however, it does not show in the export csv. Is there another way to visualize it? Or trigger a status change to "Ready"

In the production page, I'm looking to group open and closed projects into even more specific sections. I want the ability to create subgroups by year or other criteria, much like shots are grouped by sequence on the shot page.

This window is always cut off no matter how big or small the kitsu window is

Would be cool to filter by a string included in a comment (by specifiying the task of course) Since comments are not exported in the "export" feature", it makes it impossible to filter by comment either in Kitsu or even in other tables softwares Would be cool to filter directly in Kitsu :)

We need to be able to make in-screen annotations in zoomed-in versions, currently after zooming and clicking to make annotations, it auto resets to 100% and it doesn't let us to make notes in the details of each version

During a production the number of task status can be growing. But they are not used for each task. It could be great to be able to associate specific task status to specific task type.