I had the same idea. Currently my need would be to only have one more status:
I think keeping it simple, and maybe to offer to users to add their own statuses is the way to go here. I would dread Figma Dev-mode becoming Jira-like. 
Commenting to keep this active. We need an ‘implemented’ status ASAP.
Thanks for the feedback. I shared these with our internal team. Thanks!
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
I would like to more easily communicate to developers which section containing designs is the right iteration to develop. We like to keep a record of our explorations for stakeholder calls so that leaves us with a sometimes cluttered Figma file.
My team has used the “ready for dev” tag, used different pages marked with “Final” etc. in an effort to communicate which designs are the final ones to be developed. They have resorted to manually putting a color and a watermark over the old work.
Still some devs will look at old designs and get confused.
If there was a way to mark a section as archived where devs could not get redlines, export from or otherwise interact with it (we’ve tried locking things too), or even put a watermark over the whole section so it’s very visually explicit that’s not the design they should use for development.
Thanks!
I love the “Ready for Dev” indicator! Is it possible to make it more granular?
Here’s my suggestion:
The “New Update” status is particularly important for designers who continue working on the same screen. It allows them to notify developers of new changes to a screen that was previously marked as “Ready for Dev.”
Hi Kelli, I am expecting that feature also, but while waiting for Figma to provide it to us, I use these Fill and Stroke settings for my team:
The trick is adding a very transparent color, almost 0%, on the top fill layer for the Section. The Section name tag will have that color for background in 100%.
Hope this helps.
