Automation not triggered after issue linked via "added to idea"

[Jörg Eggs]

We have a project to collect customer feedback. The issues in this board are then linked to jira product discovery board ideas via the Chrome plugin, i.e. they are linked to already existing issues on the product discovery board via an "added to idea" link. They then appear on the PD board as "insights" linked to that PD issue. We very much like this workflow as one can measure how many different customer feedback issues are related to a PD issue and we can use that to measure the customer value of a PD issue.

I then tried to set up an automation rule which should automatically update the status on the customer feedback issues as soon as they are linked to a PD issue via "added to idea". I found in the automation the correct link type ("Polaris datapoint issue link") which should be triggered by both "is idea for" and "added to idea" link types. However the automation is only triggered when I link the PD issue with an "is idea for" link. Unfortunately the Chrome plugin only creates "added to idea" type links so I would need to update my customer feedback links manually after having used the Chrome plugin.

[Bill Sheboy]

Hi @Jörg Eggs 

First thing, just an FYI that there is a Jira Product Discovery area in the community to post questions specifically focused on that beta: https://community.atlassian.com/t5/Jira-Product-Discovery/gh-p/jira-product-discovery

Next, would you please post images of your complete rule and of the audit log details showing the execution?  That may provide some context for what is happening.  Thanks!

My understanding is that automation handling is still a work-in-progress for Jira Product Discovery, and so it may be that all things do not have support in REST API information to trigger rules yet.

Kind regards,
Bill

[Jörg Eggs]

d

Hi Bill,

Thanks for the quick reply!

Here is my screenshot. Just to clarify: The project where the automation is running and the link sources is a team managed software project (Jira Software). The issues in the Jira Software project should have the status changed. The project with the link targets is a Product Discovery project.

Kind regards,

Jörg

[Bill Sheboy]

Thanks for that information.  I have not used a Chrome browser extension to link issues in Jira before, so my ideas are based on general rule/Jira knowledge...

When you look at the issue with the links, do you see the other types of links and the issue history reflecting link-types which do not appear in the trigger options?

Next, if you changed the trigger to check for all link types, and add a Related Issues Condition on the link type you desire, would that work?