Enhance replacing content type properties with composition properties

[bjarnef]

Which Umbraco version are you using? (Please write the exact version, example: 10.1.0)

12.3.10

Bug summary

Sometimes one want to move content type properties out to a composition as shared between multiple content types or element types (blocks).

However it one remove the properties first, click save and add properties from composition, I have noticed the data is lost.

If one has opened the composition dialog first, then remove the properties, e.g. "heading" and "text", the composition can't be selected.

But if one goes to content type / element type, remove "heading" and "text" properties, the composition can be selected (inheriting "heading" and text" properties) and the data in the existing content properties are persisted.

Specifics

No response

Steps to reproduce

Expected result / actual result

No response

[github-actions[bot]]

Hi there @bjarnef!

Firstly, a big thank you for raising this issue. Every piece of feedback we receive helps us to make Umbraco better.

We really appreciate your patience while we wait for our team to have a look at this but we wanted to let you know that we see this and share with you the plan for what comes next.

• We'll assess whether this issue relates to something that has already been fixed in a later version of the release that it has been raised for.
• If it's a bug, is it related to a release that we are actively supporting or is it related to a release that's in the end-of-life or security-only phase?
• We'll replicate the issue to ensure that the problem is as described.
• We'll decide whether the behavior is an issue or if the behavior is intended.

We wish we could work with everyone directly and assess your issue immediately but we're in the fortunate position of having lots of contributions to work with and only a few humans who are able to do it. We are making progress though and in the meantime, we will keep you in the loop and let you know when we have any questions.

Thanks, from your friendly Umbraco GitHub bot 🤖 🙂

[skttl]

This would be a fantastic feature.

I think it could be added into the UI on the content type editor, with a button (or icon) on each property like this:

Clicking it, could open a modal, where the user could select to move the property to an existing composition on the content type (provided that there would be no alias clashes - neither on the current content type, or on other types composed by the composition), or create a new composition which would then be composed into the current content type.