Automation between discovery idea and delivery issue
Asked by Snorre Strand Asbj?rnsen:

++Note 1: Our Issue hierarchy in delivery projects: (Bets (Custom)-\>Initiative(Custom)-\>Epics-\>Story)++

++Note 2: All initiatives exist under a singular project and the underlying epics are represented in multiple other projects.++

++Note 3: Bets are represented as the overarching Issue where some Bets live in perpetuity and projects with a specific timeline (1 year, 2 years etc)++

We currently have our Initiatives in the delivery project (Jira Software Project) which are issues living from over a Quarter to a year.

We are exploring the option to move our Initiatives from delivery projects to our discovery project (Jira Discovery Project) for roadmaps, development of initiatives etc.

We want to create ideas in discovery project and than linking to an initiative (potentially have that initiatives automatically created in our Jira Software Project based on the idea from the Jira Discovery Project). Our reasoning for wanting it to be represented in both a JSP and JPD project is that from our governing team we want to use the discovery project (JPD) for upper management engagement with certain fields and development of our Initiatives with other fields.

**What it boils down to is this:**

If we have corresponding idea in a JDP with an initiative in a JSP. Can we have 2 way automation between description or specific fields between the two? If so, how does one do that?


Answers:
author: Jet
body: Hi [@Snorre Strand Asbj?rnsen](/t5/user/viewprofilepage/user-id/5473273)

It sounds like you are using Jira Plans to track initiatives? We are currently working on the Jira Plans x JPD integration <https://community.atlassian.com/t5/Jira-Product-Discovery-articles/Early-Access-Program-new-integration-with-Jira-Plans-ex-Advanced/ba-p/2743110>

This first version of the integration allows you to link initiatives to ideas, with some limitations, like only seeing the key issues and summary, no other fields just yet. We plan to improve the integration based on feedback (see community post), so soon you will be able to see specific fields between the two.

In the meantime, you can follow [@Bill Sheboy](/t5/user/viewprofilepage/user-id/1685313) advice (thanks [@Bill Sheboy](/t5/user/viewprofilepage/user-id/1685313)

comments: author: Jet
body: We also have automation templates if you purely want to automate the global fields between your delivery tickets and JPD ideas

Here's how you can do that <https://support.atlassian.com/jira-product-discovery/docs/manage-automation-templates/>


author: Bill Sheboy
body: Hi [@Snorre Strand Asbj?rnsen](/t5/user/viewprofilepage/user-id/5473273)

Short answer: that is likely possible.

First, Jira Product Discovery (JPD) projects have Idea issue types, and those have specialized link types to "delivery tickets". Those delivery tickets are normally Jira Software Project (JSP) issues, allowing visibility of delivery progress.

Next, a project-scope rule can create issues in other projects (e.g., a rule in a JPD project creates an issue in a JSP project), but it cannot access them otherwise. To access or update issues in another project, a rule must have multiple-project or global scope. Your Jira Site Admin will need to manage such rules in the global admin functions.

Next, and from my perspective, a JPD project is a special type of team-managed project (TMP), and so the field types and configurations are different. For many fields it is possible to use automation rules to move / copy data back and forth with a JSP project's issue. The "trick" is understanding the underlying structure of the JPD Idea fields so the data can be moved. One exception is the Calculated Field type in JPD: those are set based on values in Ideas and cannot be set by rules.

Finally, please consider that rules could have errors or fail to run when expected (e.g., such as during an Atlassian outage). Please consider creating a test, free Jira site (or use a sandbox) to fully exercise your configuration and rules before using them in production. And, consider how to "catch up" if rules do not run when expected.

Kind regards,  
Bill


Tags: cloud

jira

jira-cloud

jira-product-discovery

link