If you export your local workspace to Excel and import them individually into one repository, you should be able to merge.
You should just export/import the workspace you actually want to merge. If the workspace name already exists in the shared repository, SpecLog will create a new unique name. So you cannot import into an existing workspace parts of the map, but always just into a new workspace.
However, to merge maps into one workspace, you can copy/paste the imported workspace into the existing workspace after importing it.
The import does not merge requirements, but duplicates them when they exist already. So if you have two repositories with a US1, you will have a US1 and a US1 (1) after merging them.
Likewise, workspaces are getting a unique Id.
We also don’t support merging into a shared repository yet, but this is only for technical reasons we could resolve in future releases. If you started working locally with individual repositories, this shouldn’t be an issue though, as you can merge locally and then publish to a server, if you like.
If you export your local workspace to Excel and import them individually into one repository, you should be able to merge.
You should just export/import the workspace you actually want to merge. If the workspace name already exists in the shared repository, SpecLog will create a new unique name. So you cannot import into an existing workspace parts of the map, but always just into a new workspace.
However, to merge maps into one workspace, you can copy/paste the imported workspace into the existing workspace after importing it.
The import does not merge requirements, but duplicates them when they exist already.…