I love the new “Ready for Dev” status option on Sections, but would love to add and use other statuses relevant to my process. For example, it’d be great to have a “Ready for Design Review” and “Ready for PM Review” statuses so that everyone knows where things are at.
Section Statuses besides "Ready for Dev": Approved, In Progress, Archived, etc
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.
I agree with the need for more statuses, integrated with Jira and Confluence, so the link in Atlassin products show the status
I prefer custom statuses, however here are some static ideas:
- Ready for Dev (Current)
- In progress
- in Sprint XXXX
- Complete (current)
- Ready for QA
- Ready for deploy
- In Production
- Locked
I agree. My team has a process unique to our workflow with certain checkpoints needed along the way. Setting up custom statuses similar to Jira would be an incredible feature to have.
still hoping for a “ready for review” status : )
I love the “Ready for Dev” indicator! Is it possible to make it more granular?
Here’s my suggestion:
- Ready for Dev (New, New Update, In Progress, Developed)
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.”
So looking at another thread I discovered that there’s a status for New update and Completed but Figma mentions this basically nowhere. Why can’t you use it? You’re using a pro plan!
Figma’s “Ready for dev” and “Marked as completed” statuses are useful, but most of the iteration actually happens before those stages. A “Ready for review” status would add a clear checkpoint so stakeholders know exactly which frames need feedback.
Right now I maintain two pages, one for working files and one for review or handoff. This helps keep the handoff page clean, but it also creates a comment management issue: stakeholders comment on the shared review page, while I need to make changes in the working page. Since comments do not carry over when you move frames between pages, it becomes messy to track feedback.
If anyone has found a more efficient workflow or a way to keep comments linked across pages, I would love to learn from the community.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.