Update Integrations-Troubleshoot.md - #80
Conversation
simonhbor
left a comment
simonhbor
left a comment
There was a problem hiding this comment.
Do not say Spira Project anywhere please.
I could have made those changes myself after a merge, but also wanted Bruno to review to make sure the data sync explanations match his expectations.
| For example, you might need to sync Spira product A with a Jira project on your company's Jira Sandbox instance, while also syncing Spira product B with a Jira project on a different Jira instance, such as your Jira Production. In order to do this, you need to: | ||
|
|
||
| - Create two different DataSync plugins. Their "Name" fields should be defined according to their type (e.g., "JiraDataSync"), and their "Caption" fields should be used to differentiate them (e.g., "Jira Sandbox" and "Jira Production") | ||
| !!! warning "Avoid Syncing Multiple External Tools to the Same Spira Project for the Same Artifact" |
There was a problem hiding this comment.
Spira PRODUCT not Project - update in other relevant locations too
There was a problem hiding this comment.
Hi Simon,
I haven't found any Spira "project" - it is about Jira or any other external tool.
There are 5 matches and none of those related to Spira.
There was a problem hiding this comment.
It's in the different warning. For us, it shows up as: warning "Avoid Syncing Multiple External Tools to the Same Spira Project for the Same Artifact"
brgruber92
left a comment
brgruber92
left a comment
There was a problem hiding this comment.
The technical info we are adding is accurate. I just flagged a small inconsistency and please scan the proposed chages for the word "project".
When it referes to external projects, it's OK, but for Spira, our docs should say "product"
|
|
||
| !!! danger "Avoid more than one dataSync plugin type activation for the same Spira product or external project" | ||
|
|
||
| Having two dataSync plugins of the same type active for the same Spira product and/or external project will lead to duplicate data in one or both applications, depending on your configuration. To avoid this issue, it's recommended to use only one plugin for each combination of Spira product and external project. |
There was a problem hiding this comment.
Here, we are contradicting ourselves. We should say:
Having two dataSync plugins of the same type active for the same Spira product and/or external project without careful isolation will lead to duplicate data in one or both [...]
| For example, you might need to sync Spira product A with a Jira project on your company's Jira Sandbox instance, while also syncing Spira product B with a Jira project on a different Jira instance, such as your Jira Production. In order to do this, you need to: | ||
|
|
||
| - Create two different DataSync plugins. Their "Name" fields should be defined according to their type (e.g., "JiraDataSync"), and their "Caption" fields should be used to differentiate them (e.g., "Jira Sandbox" and "Jira Production") | ||
| !!! warning "Avoid Syncing Multiple External Tools to the Same Spira Project for the Same Artifact" |
There was a problem hiding this comment.
It's in the different warning. For us, it shows up as: warning "Avoid Syncing Multiple External Tools to the Same Spira Project for the Same Artifact"
|
|
||
| Do not configure multiple external projects (e.g., two different Jira projects coming from the same source URL) or multiple DataSync plugins to sync the same artifact type (such as Requirements, Incidents, or Tasks) into a single Spira product. | ||
|
|
||
| While Spira allows multiple DataSync plugins and project mappings to be active globally, mapping multiple external projects to the same Spira product for the same artifact creates severe risks of data overwrites, mapping ID collisions, and infinite update loops. |
There was a problem hiding this comment.
It's OK to say Jira projects, but we should say Spira products
4 participants
Original text in this section:
