Skip to main content

Section Statuses besides "Ready for Dev": Approved, In Progress, Archived, etc

  • June 22, 2023
  • 34 replies
  • 3837 views

Show first post

34 replies

Phu_Nguyen
  • Active Member
  • July 3, 2024

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.


Terence_Curtis
  • New Participant
  • December 12, 2024

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

Adam Schmid
  • New Member
  • February 17, 2025

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.  


RachelA
  • New Member
  • March 27, 2025

still hoping for a “ready for review” status : ) 


Apolline
  • Active Member
  • May 21, 2025

 

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!

 

 


Pooja_Sinha
  • New Member
  • November 26, 2025

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.


Marc8
  • Active Member
  • March 17, 2026

+1


Leo Vogel
  • New Member
  • July 23, 2026

Our team was just discussing how we can increase feedback for each other in our Figma files. The problem is that it's challenging to know what's ready for feedback. We've got several designers working across dozens of Figma files. What I think is needed is something similar to the Ready For Dev section/frame status. We need a Ready For Critique status that can be applied and when it is, it notifies people configured as part of the Critique team for that Team.


djv
Figmate
  • Community Support
  • July 23, 2026

Hi ​@Leo Vogel, thanks for your feedback! 

I’ve merged your topic with a similar, existing one here in the community. We’re using this topic to gauge overall interest to advocate for future implementation. While additional Dev Mode statuses are already on the team’s radar, the team hopes to use this feedback from the community to prioritize what users want most.

While I don’t have an exact timeline to share on when new statuses will be added, I’ve made sure the Dev Mode team has eyes on this topic, since it’s grown a lot since June 2023. I’ll be sure to follow up here if there are any promising updates from the team.