Merge organizations

[RikkeVestesen]

Hi Costas

We have a vendor organization that currently appears as two separate organizations in the ITB, although they should have been set up as one.

Tests are being executed for both organizations, and we were wondering whether it is possible to merge the two organizations so that they no longer appear twice in the ITB iwthout loosing the test executions already run?

[costas80]

Hi @RikkeVestesen!

This is not possible currently but it sounds like a great new feature. I see this as a new Merge... option in the organisation details screen (under the community administration), that will allow you to:

• Merge one or more of the organisation's own systems.
• Merge the entire organisation into another one. In this case each system from the "to-be-merged" (source) organisation will be listed allowing you to choose how to handle it in the "merge-target" (target) organisation: (a) delete, (b) create as new, (c) merge with target system. For options (b) and (c) where the original system is maintained, you will also have the option to maintain or not the original source system's conformance statements. Note that the associated tests will always be carried over regardless of conformance statements.

Finally, in terms of additional merge considerations I would propose that:

• Users from the source organisation are dropped.
• Custom configuration properties from the source system(s) are maintained if they are added as new systems in the target organisation. In case a source system is merged into a target system the source system's configuration is dropped.
• Custom configuration properties from the source organisation are dropped.

I think this results in a useful and concise new feature. Can you confirm this matches what you expect? In terms of planning I will put this on the backlog but would ideally wait until the upcoming release is published (and then prioritise this for a subsequent nightly build update). If this is urgently needed however we could reconsider this.

[RikkeVestesen]

Thank you @costas80

I will discuss this with my team and get back to you soon.

[RikkeVestesen]

Hi again,

I got the needed input from my team now :)

We think that your suggestion mostly covers our needs, and we agree with the description of when users and configuration properties are dropped.

One thing we are missing is the ability to move a system from one organization to another. This happens when a system is sold to another company (organization).

I would also suggest adding some sort of warning when merging systems and organizations, so that it is not done unintentionally.

Looking forward to hearing your thoughts. Thanks!

[costas80]

We think that your suggestion mostly covers our needs, and we agree with the description of when users and configuration properties are dropped.

Great!

One thing we are missing is the ability to move a system from one organization to another. This happens when a system is sold to another company (organization).

Hadn't thought of that. We can support that easily (plus with the extra merge feature you have full power over systems without ever risking to lose testing status).

I would also suggest adding some sort of warning when merging systems and organizations, so that it is not done unintentionally.

Haha of course! In general anything that takes place in the ITB that could have a consequence that is not easily reversible is gated by a confirmation (also presented as a red-danger-non-recoverable action).

Looking forward to hearing your thoughts. Thanks!

All points sound good to me and result in a nicely comprehensive feature. I'll add all points to the backlog to pick up as soon as the upcoming release (1.30.0) is published. I'll let you know when this lands in the nightly build.