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

Document generator Xray

Hi, all.

I add the following query to the report template in Word format:


${for task}
#{for n=LinksCount|filter=%{'${Links[n].IssueTypeName}'.equals('Bug')}}

No Bug

#{for n=LinksCount|filter=%{'${Links[n].IssueTypeName}'.equals('Bug')}}
${Links[n].Key} ${Links[n].Summary}


The report should include related queries with the Bug type, but the field is empty.
Tried different solutions but nothing helps.

What could be the mistake?
How do I properly unload information from a related Bug issue?

1 answer

0 votes
Rogério Paiva - Xray Xporter
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Oct 19, 2021

Hi @John 

This code ${for task} does not exist in Xray's document generator.

All iterations start with a # (sharp) char and must be run from a location where you have issue types according to the code. If your defects are of type Task, then you need to run from a location where you have Task issue types.

If you are running the report from the search for issues, and you have a list of Tasks, it is best to use the for issues iteration:

&{for issues}


Always check if the code you need exists in the documentation because it will not work if it is not found there:

If you need further help, please get in touch with Xray Support (; we would gladly assist you.

Thank you.

Kind regards,
Rogério Paiva [Xray Support Team]

@Rogério Paiva - Xray Xporter Good job. Thank you for the prompt response. Have a nice day.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events