<!-- An improvement is a modification to an existing capability. Improvements are enhancements to already implemented requirements and the improvement does not change the requirement or previously documented interfaces. Improvements are expected to be relatively low-cost, requiring roughly a work-week or less for implementation. Typically, improvements focus on enhancing usability or performance of the software. --> **Is your feature request related to a problem? Please describe.** <!-- A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] --> You can't really modify the composition of an object in the object tree. **Describe the solution you'd like** <!-- A clear and concise description of what you want to happen. --> Make composition easy to reorder (example in the tree, alphabetical, drag and drop, etc) the bones for this exist, just needs to be hooked up **Testing Instructions** 1. TBD **Additional context** <!-- Add any other context or screenshots about the feature request here. --> <!-- REPORT SECTION Fill in any of the below values that apply, they can then be pulled out for reporting purposes. Add the information directly after the ":" on one line. Who reported this? $$reporter:Peter di Pasquale (Feedback Session) Is there an ask ticket number (ex. 322)? $$ask: Is there a mcr ticket number (ex. 190)? $$mcr: Time estimate (ex. 3 days or 8 hours) $$estimate:24 hrs END REPORT SECTION -->