provide basic project status and assigned fields
B
Bret Fisher
In a 3-member team of creators, editors, and QA, it would be super handy to have a basic project status field that's just a list of standard kanban options like "backlog, recording, editing, QA, exported, finished, archived" etc. Maybe a list of status options that are custom per drive.
Today we have to use folders for this. In the past we've also used all-caps words in the project title to indicate status. It's not obvious when files are finished by one team member and ready for another step in the typical editing workflow. It would be handy to have this status field and even a assigned field so we could avoid needing other project management apps to know the basics of "is this file done" and "which person is working on it"
Sean Pritzkau
This would be extremely valuable, especially combined with API access.
Scenario:
• My editor marks an episode for "review" and that kicks off a webhook / automation that makes me aware.
• I approve a cut, it sets the status to "complete" in Descript and publishes my episode in Transistor.fm, etc.
Cameron Suorsa
I completely agree with you Bret Fisher! We need a way to mark the status of projects - and it should be customizable per drive. Perhaps even only certain people could have permissions to mark a project as complete.
If this was combined with an audit log of the project, you would be able to then view that a certain user gave approval for the episode. Eric Dudgeon Olivia Whiteman do you agree that this would be helpful as part of our workflows?
Then for those using other project management systems... it would be great to then have these added as Zapier triggers/actions as to improve users workflow!