Match status from child Epic to Parent Feature project

[Yuliia Vyborova]

Hello!
My previous ticket expired so I had to submit new one. My question was how to set automation to match status of child Epic in one project (TXL) to its parent (custom issue type called Feature project) in a different project (ETE). 

The suggestion was to add Variable and specify it in the Branch step. Here what I have: 

And I can't validate query in JQL. Is my syntax wrong? Or steps are wrong? 

[Kai Becker]

Hi @Yuliia Vyborova 

thanks for your question.

First thing I saw in your JQL:  issuekey 
This is not a valid JQL syntax. A single issue key would be referenced like this: key = XYZ-1

Maybe this already solves your problem? If not, it would be good to see the part, where you create the variable.

[Yuliia Vyborova]

@Kai Becker in JQL I need to specify variable from previous step. Is my step Create variable correct? 

[Kai Becker]

Hi @Yuliia Vyborova 

thank you for your response. 

You are right, you need to specify the variable from the previous step. You might try a different variable name, as parentLink might be something internally used.

Also I would recommend to log the variable content to the audit log using Log Action. This should return an issue key, if not there is something wrong with the  variable.

[Yuliia Vyborova]

thanks! I updated to ParentProject. But I think smart value is not correct. This is what I found in documentation about Parent Link: Which one should I choose in this case? i need to specify Parent Link in ETE project for Epic in TXL project. Should this be {{issue.parent.key}} or {{issue.parent.epic.summary}}?

[Yuliia Vyborova]

@Kai Becker can you help with this please?

[Kai Becker]

Hi @Yuliia Vyborova 

{{issue.Epic Link}} should return the key of the parent epic.

This could also be used directly in your JQL. No need to create a variable here.

[Yuliia Vyborova]

Thanks Kai! I need to return parent issue of an Epic, parent issue is Feature project (custom issue type). What JQL should I use in this case? sorry for bumping with this, I can't find a solution.

[Kai Becker]

Hi @Yuliia Vyborova 

I guess I got you wrong in the first place. Could you try to use the following as branching JQL:

parentissuesof("{{issue.key}}")

I hope that this should be enough.