Synching issues, not importing them
Asked by JulienFritsch:

Hi,  

I'm starting to test this interesting and promising new tool because I wanted to see what a true native Atlassian Product Roadmap tool could offer regarding Jira integration.   

And so far, this is still the big question and limitation I see. Indeed here is my use case, which has been working with other similar tools.

- we use different Jira servers and projects to manage lots of engineering products development

- the feature requests for each of those products are inside those projects

- other tools allow us to synchronise those (using a filter search) between the Jira project and the Roadmap tool workspace/space/project managing the idea/features...

- on the Roadmap tool, we can enrich the request with insights, RICE scores, and customer information, .... and those values remain in the Roadmap tool. But the rest of the Jira fields are in sync with the development project.

But in this tool, it looks like I only have three options :

- create manually new ideas

- import from a bulk list, but then those issues are MOVED. And this is working only for the same server.

- import a CSV list: but in this case, there are no links back to the issues

So this means that we cannot "synchronise" our feature requests with the ideas and have to "create" them all by hand. And this is not what I was expecting and not what we want.  

In the past and even today, I have been developing Javascript scripts with Google Sheets and Jira and using Zapier to synchronise some fields that are not synced with our current roadmap tool. I'm not even sure if it's possible here. But if it is, I have to say that's not wanted. The principal value expected was to avoid such custom development and get a native integration.

**But I'm new to this tool; maybe someone knows better or found a solution.**


Answers:
author: Tanguy Crusson
body: Hi [@JulienFritsch](/t5/user/viewprofilepage/user-id/1002276) , you are right, this is not the model we designed the tool around. Instead the approach we've taken is that all your ideas live in Jira Product Discovery, and the ones that you commit to are connected to delivery work that you track in various Jira Software projects (and you can track the progress from Jira Product Discovery). If you use the app like that, then the integration is native.

(and we're currently working on improving it to share more info between the idea and its corresponding initiatives/epics)

comments: author: JulienFritsch
body: Thank you [@Tanguy Crusson](/t5/user/viewprofilepage/user-id/502312) , unfortunately, it's not what we need then, but good luck.


author: Andrej Freeze _ greenique
body: Hey there [@JulienFritsch](/t5/user/viewprofilepage/user-id/1002276) ,

I can see that this use case may not even be uncommon. Especially if one has Jira Service Management or another service desk in use, where feature requests are gathered first.

I have not yet tested it, but looking through the community I saw that Jira Product Discovery is capable of using the default [Jira Cloud API](https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issues/#api-rest-api-3-issue-post). Utilizing it, you should be able to create Automations that:

* initially send your issues to JPD and create ideas
* synchronize future changes and relevant fields between issues and ideas

In theory you could even create these automations with Automation for Jira but the amount of requests you will send for each update will be tremendous. Good filtering and setup will be the key, if you want to use this.

Hope this helped a little!

Andrej

comments: author: JulienFritsch
body: Hi,

First, thank you for your answer [@Andrej Freeze _ greenique](/t5/user/viewprofilepage/user-id/909291).

<br />

Maybe, it's possible to create such integration ourselves using the API, but I don't want to do that since I don't want to spend time on it and maintain it over time, whereas it's between 2 Atlassian products.  

I want a roadmap product that easily gets feature issues already in Jira projects to be used and synced to avoid having to re-recreate them manually or to develop our integration using the API. And the one we use currently doesn't do it perfectly yet, but almost already.

Regards.  
Julien