nested for in XPorter template

Deleted user June 19, 2020


I have prepared an excel template that contains this line


#{for a=JQLIssuesCount|clause=issuetype = "Area" and project = "pippo"}

listing these fields

${JQLIssues[a].Key}

${JQLIssues[a].Components}

${JQLIssues[a].Summary}

and then the last line is

#{end}

 

on the Jira project I have these issue types:

1. Area

2. Attività

3. Progetto

4. Sotto Progetto


the hierarchy is that a certain number of issuetype Area has as related issues a certain number of issuetype Attività.


so I modified the XPorter commands above by writing like this:


#{for a=JQLIssuesCount|clause=issuetype = "Area" and project = "pippo"}

${JQLIssues[a].Key}

${JQLIssues[a].Components}

${JQLIssues[a].Summary}

#{for b=JQLIssuesCount|clause=(project = "pippo" and issue in linkedIssues(${JQLIssues[a].Key}))  and issuetype = "Attività" ORDER BY key ASC}

${JQLIssues[b].Key}

${JQLIssues[b].Components}

${JQLIssues[b].Summary}

#{end}

#{end}

 

 

The issuetype Attività may each have one or more links to issuetype Progetto.

So I modified again the XPorter commands above by writing like this:


#{for a=JQLIssuesCount|clause=issuetype = "Area" and project = "pippo"}

${JQLIssues[a].Key}

${JQLIssues[a].Components}

${JQLIssues[a].Summary}

#{for b=JQLIssuesCount|clause=(project = "pippo" and issue in linkedIssues(${JQLIssues[a].Key}))  and issuetype = "Attività" ORDER BY key ASC}

${JQLIssues[b].Key}

${JQLIssues[b].Components}

${JQLIssues[b].Summary}

#{for c=JQLIssuesCount|clause=(project = "pippo" and issue in linkedIssues(${JQLIssues[b].Key}))  and issuetype = "Progetto" ORDER BY key ASC}

${JQLIssues[c].Key}

${JQLIssues[c].Components}

${JQLIssues[c].Summary}

#{end}

#{end}

#{end}


it just so happens to me that the fors nested don't show all the issues the way I'd like them to. It seems that only the first issue type Area is read, let's say key = pippo-1 and then listed only the linked issuetype of Attività type and then the further linked issuetype of Progetto type.

It seems as if the letters "a", "b" and "c" of the for cycle don't update

2 answers

1 vote
José Domingues [Xray]
Marketplace Partner
Marketplace Partners provide apps and integrations available on the Atlassian Marketplace that extend the power of Atlassian products.
July 16, 2020

Hi @[deleted] 

Can you please create a new ticket in our Service Desk and share the template you are using and some screenshots of the issues you are trying to export, including the link between them.

Best regards,

Team Xporter

Deleted user July 16, 2020

ciao @José Domingues [Xray] Yes, I confirm that I've done this before.

Like José Domingues [Xray] likes this
EPSSystems DCDD November 26, 2020

Can you please share the solution to this, I'm experiencing a similar issue

Like Deleted user likes this
0 votes
Deleted user November 26, 2020

@EPSSystems DCDD   there was no time to wait for Xporter's answers and when they arrived it wasn't adequate to my client's needs, so my developers colleagues wrote a customization for Jira and I solved it this way. However, I would like to point out two things: the first one is that Jira is still in 2004 for the report functionality. It is amazing how in this company they never realized the importance of being able to represent data well. Luckily there are plugins like Xporter that despite Jira's enormous limitations, can give you something that allows you to present usable reports.

EPSSystems DCDD November 26, 2020

Thanks for the response, will continue working on this till I figure out a solution

Like Deleted user likes this
Deleted user November 26, 2020

@EPSSystems DCDD  I suggest you to write directly to Xpand.IT support they can help you better than me. 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
SERVER
VERSION
8.2.4
TAGS
AUG Leaders

Atlassian Community Events