Hello,
I would like to know a way of having in a structure, a columns which shows the linked issues marked as "depends on", not showing all other linked issues (parent, child, etc).
thank you,
Marina
Hello @Marina_CL
You can do it with the formula like this:
issuelinks.FILTER($.type = "depends on" and $.source = key).destination
You might need to adjust either the link direction name, or the source of it in the formula.
I hope this helps. If you need further assistance or have other questions about Structure, please reach out to us directly at our support portal.
Best regards,
Stepan
Tempo (the Structure app vendor)
I am not sure this is what I was looking for. If I am not wrong, you are adding into a structure the issues that depend on one (or several) specific issue(s).
What I would like is: from a issue filter which has several results (no all with dependence links) inserted into a structure, adding a column in the structure which shows the issue in which each issue of the list has a "depends on" link.
Same as the columns "linked issues" does show, but showing only "depend on" linked issues.
Hope it is clearer now... Thanks.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You can do this in the Formula column using the formula above. It's not about building the structure, but about showing data related to linked issues in a column. The formula checks if every existing issue in the structure has any issues linked to it with the 'depends on' link type & direction. And if an issue has such links on its Issue Page, the formula returns issue keys of the linked issues.
Please reach out to us directly if you have more questions.
Best regards,
Stepan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Stepan,
thank you for the explanation. I am still not able to get it. I inserted formula column with the formula, and it is not showing the issue key on it (on the issues that have that type of link. I guess I am doing something wrong.
I enclose the screenshots
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Marina_CL
The 'depends on' link displayed on the Issue Page os DST-3361 is a link direction(inward or outward, how it is configured in your Jira); in the formula, you need to specify the link type. You can find the name of the link to which the 'depends on' direction belongs to at Jira settings | Issues | Issue linking. The name of the link should be defined in the formula in quotes. But the formula might still not return anything because .source and .destination parts reference how two issues are connected by the link of a defined type; you might need to flip those in the formula, depending on the direction of the link.
If you need further assistance - please reach out to our support portal and we'll get back to you shortly.
Best regards,
Stepan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks @Stepan Kholodov _Tempo_ does this work in Cloud or only in DC? Thanks,
Kel
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Aha! Finally got it! Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This is awesome, but how would I extract the dueDate from each of these values? For instance I would like to know the due date of each dependency. I used following code. I am able to extract key, but not due date :(
issueLinks .FILTER($.type = "depends on" AND $.source.key = key) .destination .MAP(CONCAT("Key: ", $.key, ", Due Date: ", $.duedate))
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.