You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When two development solutions contain the same entity as a container only (i.e. metadata not included), approving a solution merge for one of these development solutions will show a potential warning conflict for the other solution.
Steps to reproduce
Steps to reproduce the behaviour:
Create two issues and progress them to an in progress status
Add the same entity to both development solutions excluding metadata
Create a solution merge for one of the issues
Click the approve button
Observe a conflict is reported
Expected behaviour
No conflict should be reported.
Additional context
The only possible conflict that can arise from this scenario would be if one of the solutions has made ribbon changes to the entity. Ribbon changes don't require entity metadata to be added in order to be included in the solution. Ribbon changes are made far more infrequently than changes to entity sub-components, however, so it is probably preferable to avoid lots of false positives in favour of a few false negatives (that should be picked up on the pull request anyway).
The text was updated successfully, but these errors were encountered:
Description
When two development solutions contain the same entity as a container only (i.e. metadata not included), approving a solution merge for one of these development solutions will show a potential warning conflict for the other solution.
Steps to reproduce
Steps to reproduce the behaviour:
Expected behaviour
No conflict should be reported.
Additional context
The only possible conflict that can arise from this scenario would be if one of the solutions has made ribbon changes to the entity. Ribbon changes don't require entity metadata to be added in order to be included in the solution. Ribbon changes are made far more infrequently than changes to entity sub-components, however, so it is probably preferable to avoid lots of false positives in favour of a few false negatives (that should be picked up on the pull request anyway).
The text was updated successfully, but these errors were encountered: