Status changes of child ideas (Merge)

What is the challenge?

• After two ideas are merged, the parent idea's status will always drive the status of the child ideas. However, the child idea's status can still be changed independently, which can result in the parent and child status becoming misaligned and falling out of sync.

What is the impact?

• It is not ideal that the status of a merged child idea can still be changed independently. Since such status changes are reflected in the portal and thus communicated to customers, this creates a risk of inconsistent messaging and confusion.

Describe your idea.

• The status field of a merged child idea should become locked or read-only once the merge is completed, ensuring that status updates can only be managed through the parent idea.