Enable propagating a subproject with a propagation change package

[mrump]

 

Idea generated from existing article 

• If you want to apply changes from a devpath to the mainline using the merge child development path functionality, all operations can be propagated except for configure subproject operations.

• The following error is received if a configure subproject operation is done on a development path that is merged:

The following were not updated due to errors:
Project: <Projectname>
Sandbox: <Sandboxname>

Subproject <subproject name>: *** no action will be performed due to errors ***

Error: Change package <CPID> contains a Configure Subproject operation.

This operation cannot be propagated automatically by Resynchronize Change Package.
You must propagate this operation manually, if appropriate.
Reference Change Packages: <CPID>

IDEA:

Merging configure subproject operations should also be possible by using the merge child development path functionality.

[mrump]

Why was this deleted ???

[Siddharth]

@mrump I'm a bit confused by your comment.

Would you please give me some understanding about the content that you believe was deleted ?

[mrump]

I just  received a mail, informing me about change in the idea. When clicking on the link in the mail 

Hi mrump,

GauravPhadtare (Level 7) posted a new comment in Integrity Ideas on 05-31-2019 08:44 AM:

Re: Visually represent working revisions in Source Project History View in Integrity Lifecycle Manager - Status changed to: Under Consideration

Reply

this idea opened, but a big red banner on the page stated that the idea I was trying to view was deleted.

This triggered my last comment

[olivierlp]

Hello,

We are archiving your idea as part of a general review. This action is based on the age of your idea and the total number of votes received, as per this announcement.

You can always post a new idea with all the details required in the form.

Thank you for your participation.