Is Post Function 'Copy Value from Other Field' parent as the source broken?

[Matt Houck]

I have seen several other posts on this that are a bit aged or off point by a little bit. 

Specifically, I have a series of fields that we collect in parent issues and I want to use the in-house Jira functions to copy them to the exact same field in the child issue during the post function. 

I have the Parent link set up between the parent and the child issues but the post function does not transfer the data.  Any help or guidance would be appreciated.

[Matt Houck · Accepted solution]

I have continued to work on this problem and have finally found a solution that works, albeit clunky, based on @Fabian Lim 's suggestion of looking into Jira Automation.  In the issue hierarchy I have set the issue types in the following order;  CIT, RP, and then MS

With this, CIT is the parent of RP, and RP is the parent of MS.  This relationship is required for the advanced roadmap and Plans as is needed in my original question but is also required to pull the contents from parent to child. 

I was also required to establish a "linked issues".  For this I have restricted it to "is blocked by" so CIT is blocked by RP and RP is blocked by MS.

From here I can establish automation that when the CIT information is changed the automation will look for all linked issues where the type is "is blocked by" in the branch rule.  It then copy's the fields from the parent.  

Note:  The linked issues is the only option I can use for the branch rule as there is no branch rule looking for the child.  Only for the sub-task and for me, RP and MS are not sub-task issue types.  It would be nice if Jira added the option to branch looking for the child.

Note 2:  It would still seem to me that my goal here should have been accomplishable through a Post Function Copy Value from Other Field using parent as the source but it does not.  I feel this is a bug.

[Fabian Lim]

Hi @Matt Houck

Can you share a screenshot that shows the relationship between the tickets? Also which relationship are you using on the post function. You may be using link relationship type (parent of) instead of the parent-child link that is used for advanced roadmaps for example.  

Regards

[Matt Houck]

The top picture is the Child and is also the issue with the Post Function.  You can see in the second picture that there are contents in the fields.  The third and 4th pics show the Post functions for the fields I'm showing.   Here I am showing the screens for the create transition but I use the same post functions further down the workflow as well.

Also, I have confirmed that I have published the workflow.  Thanks for your quick response so far I'm looking forward to having this one solved!

[Fabian Lim]

Based on the pictures, you are using the Parent and Child link from Advanced Roadmaps.  (I see a Story and Epic)

The post-function you have only works for parent and subtasks relationships.  I think that's why it doesn't work.

I suggest you use Jira Automation instead where based on a trigger you can copy to the children.  

[Matt Houck]

Based on what you are saying I'm going to try something to see if it will work but neither of the issue types I'm using now, are actually an epic.  I just use the same Icon for epic on MH CIT issue type.

I will say, once I get this working I will want to use the Resolution Plan issue type as the parent for Milestone issue type.  You can see my hierarchy screen below.  To me this hierarchy is counter intuitive but in having it set up in this way allows the Plans to work properly, bottom screen.

I will need to also look more into Jira Automation 

[Fabian Lim]

Thanks for sharing.  Either way they are not subtasks of a parent so that's why the post function doesn't work.  

Use this video as an example, it will be the second rule and instead of subtasks you are looking into a parent-child relationship.  Link: https://youtu.be/DcPYrw-Puus 

I hope this helps.