Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Writing story points from associated 'delivery' tasks to idea tasks



I see that when issues are added to an "idea" issue on the product discovery board, the discovery board issue is linked as an 'implements' link type.

1. I would like to have the story points of the tasks that 'implement' the product discovery idea task added to said task under a new integer property i called "StoryPoints"

2. Below is the automation I am trying to build, however I cannot fetch linkedissues of the trigger issue with type implements


linkedIssues({{triggerIssue}},implements) does not work 


1 comment

Hi @ABD ,

Shouldn't your query be:

linkedissue in linkedIssues({{triggerIssue}}, implements)

This seems to work for me if I replace the smart value with an issue ID

@Chris Timms thanks for your reply. This fix worked and I see that the automation is indeed able to find the correct `implements` issue from the trigger issue.


However its telling me that it cannot find the field StoryPoints (A field I created on the implements issue [PM-58 in this instance]).


Is that because the third step in my automation is trying to apply the rule to the trigger issue and not the looked up issue?


This is how my third step looks


Your automation is trying to edit the StoryPoints value on ZL-3508 which doesn't exist because StoryPoints only exists on PM-58.

On reflection, doing something like below is a little neater than relying on your original JQL:


@Chris Timms Thanks for this suggestion, I implemented it and it works great!


A question: Are "value change" triggers not triggered if the field itself is changed by automation?


I have the following hierarchy:

Task <- child of Epic <- implements product idea


I have an automation that when the story points on a task are changed, all child stories of the epic have their story points summed and update the story points of the epic.


I wanted this change in the story points of the epic to trigger this above automation we're discussing to update the product idea task. 


However this seems to not work. 

@ABD there is a setting in "Rule Details" that allows you to enable a rule to be triggered by other rules:

"Check to allow other rule actions to trigger this rule. Only enable this if you need this rule to execute in response to another rule."

Enable that on and you should be good.

Thanks so much! This worked like a charm. 


Log in or Sign up to comment
AUG Leaders

Atlassian Community Events