Can your plugin support this use case?
My use case:
There are 3 projects in JIRA1 and 1 project in JIRA2.
1. A new ticket of each of projects in JIRA1 will trigger creating a ticket of the project in JIRA2;
2. Any update in a ticket in each of projects in JIRA1 will be updated into the corresponding ticket of the project in JIRA2, like comments, title, description, attachment.
3. Any update in a ticket of the project in JIRA2 will be updated into the corresponding ticket in each of projects in JIRA1 , like comments, title, description, attachment.
I encountered an issue as below
JIRA1: ProjectA, ProjectB and ProjectC
JIRA2: ProjectX
Three synchronizations are built for
ProjectA - > ProjectX,
ProjectB - > ProjectX and
ProjectC - > ProjectX
When a ticket is created in ProjectA, I see what happened as below
Case 1: a ticket is created in ProjectX (It is expected)
Case 2: a ticket is created in ProjectB (It is NOT expected)
Case 3: a ticket is created in ProjectC (It is NOT expected)
Anything to do in order to avoid this issue? Please help
-
Hi,
Thanks for the question.
Just to clarify, do you want to synchronize issues created in Jira X to project A/B/C? Or do you only want to sync issues in one direction (A/B/C to X) but then also sync field updates from X to A/B/C?
If you don't want to sync newly created issues from X to A/B/C, you can simply set up backbone to synchronize issues in 1 direction (from A/B/C to X) and then configure the field mappings to be synced bidirectionally, so that once an issue has been synchornized to Project X, field updates then get synced back from X to A/B/C.
I hope this clarifies things – if not, I can help further if you provide more precise details of your use case.Cheers, Tom.
Please sign in to leave a comment.
Comments
1 comment