Yes! I just posted this on twitter a couple days ago. I don't see any reason why not, surely this aspect needs to keep up with evolving necessities of the designer, whom might think or receive request to implement new states at a later date, but that would be convenient to keep in a certain hierachy

Components with many states often require some logical clustering in the list, otherwise it may get really confusing.

I've been "provisioning" many empty states ahear, only to try to control the order of the list, but a simple drag would be way simpler.

Rearranging would be very helpful. Currently it is a lot of work to fix a bad arrangement in a component with a lot of states. Resizing the section would also be handy - picking the right state out of list with 16 states makes me uncomfortable now.

I was creating states and I identified the necessity to create a state between others two. I tried to drag the new state but it didn't have any effect.

It would be cool if we were able to reorder states

This is much needed. If you don't plan carefully your states will be in a not ideal order with no way to rearrange the items without releasing the component and starting over.

I think on top of being able to rearrange them, it would be great to be able to make groups as well. I'm trying to sort a style guide right now and it'd be great if I could get all my button permutations into one master component. Right now without this it's a mess.

Just to clarify, this post is about the ability to rearrange the component states in the Property Inspector > Component section (the panel on the right in Design mode and Prototype mode). Thanks.

Component state are great. However this is one of the features that is sorely needed now that we have states. Input and button states are a good examples of how organization of multiple states really matters. For instance, in an input I could need an input without a label or with a label, and without helper text or with help text, and need to show each of these in default, focus, error, and disabled states. Additionally, I made want to add or remove the required tag as needed.

One could argue that I could simply make 4-8 separate master components. However, if the intent is of the program is rapid prototyping, and I believe the intent of states is to improve this by not having to create repeat components that are, for all intent and purposes, closely related at the atomic level. The examples provided are additional artifacts that modify an atom (the most basic usable element), they are not atoms themselves.

I would not expect all sizes of each atomic element to be kept in state. However, there is not reason to consider this as well. I think the general idea is to keep your components tab as clean as possible. Particularly if an organization is trying to drive their design governance, in part, through XD.

Something as simple as not being able to reorder these makes the state less useful and, in some cases, causes outright confusion when consumed by those that did not create the component and it's corresponding states.