Hi all,
We started using Jira Product Discovery as a possible external roadmap product replacement and so far we are really happy about the flexibility. The option to have "delivery" issues linked to the idea is great...however, in terms of the "Project Target" you are missing those dates indications in the Jira software issue...
I tried to use the Jira Automation rule to manually sync as suggested (https://community.atlassian.com/t5/Jira-Product-Discovery-questions/Automation-to-Sync-Dates-Between-an-Initiative-in-JIRA-Software/qaq-p/2212438#M1268), but it cannot find "linked issues", perhaps as it is a delivery issue and not a native linked issue?
Having more details within the Jira Software part for the delivery would really beneficial.
Hope someone can help or the product team can give some insights about the coming features :-)
Regards,
Peter
Hi @PeterE
Without knowing more about your scenario, I hypothesize accessing the linked issues between Ideas and other Jira issues is possible in automation rules.
You can confirm that using this how-to article, which describes how to learn if a field is supported by automation rules, and the exact structure and smart values to use: https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/ Basically you identify an example Idea and call the REST API with a browser to find what fields are visible (or not).
And...Jira Product Discovery (JPD) appears to be built upon team-managed projects (TMP), and so is just another project. That means if you want an automation rule to access issues in multiple projects it will need to be either global or multi-project in scope. Please check with your site admin on your license level because there are limits to the number of global/multi-project rule executions per month based on your level: https://support.atlassian.com/jira-cloud-administration/docs/explore-jira-cloud-plans/
Kind regards,
Bill
@Bill Sheboy is exactly right here. @PeterE we're thinking about introducing date syncing across Jira Product Discovery and Jira Software in the future, would you like to speak to us about your use case? https://calendly.com/rswami-atlassian/customer-calls
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Bill Sheboy thanks for your explanation...I believe there is a current limitation the way "delivery issues" are linked. As such, automation rules don't work in that way.
But I will first take a call with @Rohan Swami to further discuss the use-case, perhaps I'm looking in the wrong direction.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Interesting...when I did a quick test to check the REST API with an Idea issue type, I did see the linked delivery issues in the results. Please post what you learn after the call to benefit the community. Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.