Create connections automatically

 
1
0
-1

I have a connection between Jira Software Cloud and Azure DevOps. In Jira I have only one Jira project (Management project) with a lot of issues (issue type = project) inside of it. On the other hand, in Azure DevOps I have a lot of projects. 


I need to sync projects (my Jira issues) and epics between Jira with Azure DevOps projects and epics. When I create a new project (issue with issue type = project) with some epics inside of it, I need to create in Azure DevOps a project with an epic inside of it. 


The problem is that I cannot automate the connections between the new Jira project (issues) and Azure DevOps new project and I don´t know how to do it. Maybe you´re able to imagine another idea  to do what I need. 

  1. Francis Martens (Exalate)

    How many projects would this be?

  2. Agustin Reta

    At the beggining there will be between 20 and 25. But I don´t really know if it´s going to increase. 

CommentAdd your comment...

1 answer

  1.  
    1
    0
    -1

    We have multiproject support on the backlog, and the whole use case can then be captured in a single connection

    What I can advise now is to create these 25 connections (as scripted connection) and copy paste the configuration on the different connections.  



    1. Agustin Reta

      Do you have any idea when it´s going to be implemented this functionality?

    2. Francis Martens (Exalate)

      Nope -  we are wrapping up the feature on github to support multiple repositories in a single connection - this will be delivered on 5.4.  Based on our experience with that feature, we'll expand the concept to AzureDevops.

      So - don't hold your breath.

      Can you (or anyone interested in this feature) please raise a ticket on our support portal
      https://support.idalko.com/servicedesk/customer/portal/8 referring to this discussion,

      We'll link it to the product issue on our backlog and let you know when it has been implemented.

    3. Daniel Carvajal

      Hi Agustin Reta 

      We just received notice that this feature has been implemented in the latest ADO Exalate node release https://docs.idalko.com/exalate/x/AYDmBw, please check the documentation here: https://docs.idalko.com/exalate/x/LwCjC

      Cheers,

      Daniel


    CommentAdd your comment...