How to sync Components and Versions

General Questions
, ,
1

Originally asked by Maria Alfonso on 25 September 2019 (original question)

We want the components and versions to be available to the other local project. Is it possible for the Project 2 to just inherit the components and versions of Project 1, and not create a new issue?

I tried to Exalate an issue in Project 1 (key: P1-6), it just creates an issue P1-7 inside Project 1, Instead of in Project 2Source: Jira Cloud (old community)

2

Answer by Francis Martens (Exalate) on 25 September 2019

You could set up a ‘transfer issue’ where the project information is transported whenever it is changed. It is a specific use-case but perfectly doable

  • Setup a connection between P1 and P2 which also transports and creates components and versions
  • Exalate a generic issue P1-123 which generates a twin P2-234 using that connection
  • Whenever components/versions need to be transferred, update issue P1-123. This will trigger the functionality

Let me know if this helps

Comments:

Maria Alfonso commented on 07 October 2019

Sorry for the late reply. I am trying to setup a connection between P1 and P2. but its not working. I tried to Exalate an issue in Project 1 (key: P1-6), it just creates a new issue (P1-7) still inside Project 1.

Francis Martens (Exalate) commented on 07 October 2019
  • Is it a local sync or a sync between two different instances
  • Can you provide the incoming sync of the reeceiving end of the connection
Francis Martens (Exalate) commented on 07 October 2019

Hi Maria Alfonso-

You will need experience with Jira as an administrator and understanding of scripting to be able to successfully complete this task. Some companies are outsourcing this to their Atlassian Solution partner (or directly to us).

Note that we do provide a 2 hours workshop to help you set up this use case. It is complementary to your evaluation of the product.

Please reach out to sales@exalate.com to set up the workshop
Make sure that you include a colleague that has the necessary background knowledge whenever proceedings

Maria Alfonso commented on 07 October 2019

Is this because the Component “Project A Component 1” is not yet listed in Project B?

Francis Martens (Exalate) commented on 07 October 2019

Probably it is.

Check following documentation regarding how to create missing components

Vedant Kulkarni commented on 20 February 2020

Hi Maria Alfonso , Did you got the answer? I have a similar use-case where I do not need to create an issue rather I just want to copy field values from Parent to subtask after creating the subtask in a parent issue.