Allow to mark nested elements "Ready for dev"

Thanks again for the feedback, @Arlo_Jamrog!

This isn’t on our immediate roadmap, but we hear you. I’m sure there are others in the community that would want to be able to mark nested sections or frames “Ready for dev” as well.

We’ll pass this onto our Dev mode team for consideration and use votes to gauge overall interest from the community.

As a PO I have the need to reference on single components/groups/frames to specify jira tickets for the developers. Therefore it would be helpful to set components/groups/frames to “ready for dev” & link them to the jira tickets separately.

I have the exact requirement as Melanie. To support agile development, I need to denote some sections within a frame ready to develop, and some still have open questions but they logically belong in the same frame (We build reusable components, not apps, so our frames aren’t pages but related features for a component). I name sections with jira tickets but then I can only declare one section within the frame as buildable, so we can’t really use ready for dev feature. We use a kinda lame and not trackable yellow highlighting instead.

I’d also like this because we group our UI icon components in a “frame”, so that finding icons is within a frame category. For example, the General frame contains the “log in” UI icon. When designers attach this library they are able to find the icon by category OR search, helping them find the icon in their way. We have tons of ui icons, larger icons, and illustrations that we categorize this way. When I send updates to my dev, I want to send one icon at a time so he can easily find the ones that need updating into our code library. I don’t want to do this at the section level, just the icon level.

P.S. This DID work with sections. It does not work with frames.

Same issue here with needing to add documentation and related components in one frame for clarity for consuming designers, product owners, and devs, but marking the ENTIRE frame is just silly when 1 component out of 5 changed and all documentation remained the same.