This feature is so, so important. The whole purpose of components is to speed up workflows and allow for consistency, but if I create a button or a field using a component and have a few different states (e.g. view mode, edit mode, mandatory, disabled) then I have to change the field label, value and size for EVERY state which renders much of the benefit of states and components lost. This is another gap with regard to components, just like the inability to see all of the states in the developer preview.

Another feature that would be really helpful for components is that if you select multiple instances of the same master component it would be great to be able to set them all to the same state, so that if I have a field component and I have 10 fields on an artboard I can just select them all and set them all to edit mode, or disabled at once.

This drives me insane with hover states! Especially if it's a component that is repeated 10 or 20 times (such as a row in a table). Having to make each text change (or whatever) twice due to the hover state is extremely tedious. Thanks for looking at this one Adobe!

OMG. Yes, I need this! Please!

I am again surprised that this feature isn't there. There should be a way to select the whole button and resize all states, rather than just the default one.

I could really use this feature.

I need this!

The lack of this functionality is making me push my workplace to use Figma or Sketch instead of Adobe XD. Many wasted hours on changing the text on additional button states.... sigh

Too much manual and time-consuming editing, please improve it.

Yes, please, so very much! I got a project that spans across over 250+ artboards. All of them use some master components, and if a feedback comes to change a certain component, it'd save me unbelievably large amounts of time. Not to mention all buttons that come inside that component too.

I agree that I have spent hours reorganizing components because of this issue. I used to work with Sketch and Sketch identified a text field/color/icon as a part of a component that could be specific to a particular instance and provided a panel for modifying these for each instance. With XD, the component panel is only useful for hover and click states, but not for repeating styles. This is very disappointing!

would be highly appreciated

This issue makes the states feature very difficult to use. If the user creates a new state and edits one element of that state, it should be treated as an override. The new state should still inherit all other properties from the default state and any changes made to the default state should propagate to all other states unless there is an override present. This is the way it would work in simple css.

may i ask, how this is still marked as "feature-under-review" but in the forum someone said, u are actively working on this (since nov 2018) how is this not done by now? this renders the feature almost useless

This means I just simply can't have a functional and interactive design system. So now I have to delete all my components states because when I interact with them it is absolutely ugly. This should not be a feature but a bug fix. What it the point of having a library of components with different states if you can't interact with them? It prevents me to do a good job in my company. This issue has been highlighted for a long time now and you can't even give us a proper time frame to fix the issue.

I am also looking forward to seeing this update made. The states almost aren't usable otherwise.

I'm literally having to remake all of my components. I have a UI Standards Guide with master components. If I drop a master component from my standards guide(for example a button) into a new design(file), then create a table (for example) that includes this button component (with a new label), then paste the table back into my UI Standards Guide for reference, it reverts the button to the master component label and width. Is there any override for this? We also, need a way to create a master component from a modified component.

Yep, obvious really...

We REALLY need this to be a thing. I waste so much time with asset instances having to get all of the text the same across instances. In our design system, like many others, we have various button states, and the fact I have to copy the custom button name into every state manually is just ridiculous. It really makes me wonder if the folks who program this software actually use it. These wasteful microinteractions add up, and make the experience time consuming and frustrating.

Brilliant work on this application so far. Thank you for the hard work.

Of course nothing is perfect ;-) - As a visual designer, it's really important that I can convey the animations and micro interactions to stakeholders where possible in my high fidelity visual mockups.

Unfortunately, the process required to do this relies on my re-use of button components with built-in states. These states don't inherit the new labels and icons when I override the instances. This means I'm editing the following for every button I override:
enabled, hover, focus, pressed, selected and disabled .... it takes a looooong time.

Recently started using XD and I can't believe component states were added without thinking about this since the whole point of components is to be able to make a base design and use it throughout your design with slight changes.

If I change the text on the default state of a child component that change should be there on all states just like if I did it on the master I shouldn't have to retype it for each one. And the same should be for nested components; I'm currently working on creating some CTAs that all have the same look but different icons. I should be able to replace the nested icon component with another and it should replace it for all states and a bonus would be that it takes on any color changes I made for the other states.