You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hi,
I've tried everything. I want to export JQL searchresult (Epics & Tasks) to Word in iterations with this schema
> Epic A:
- Task 1
- Task 2
> Epic B
- Task 3
- Task 4
The problem I have, is, that it randomly sorts, i. e. it looks like that
> Epic A:
- Task 2
- Task 1
> Epic B
- Task 5
- Task 2
...
Currently, my template is this:
&{for issues|filter=%{'${IssueTypeName}'.equals('Epic')}}
1 ${Summary} <--Epic Name -->
#{for n=LinksCount|filter=%{‘${Links[n].LinkType}’.equals(‘is Epic of’)}}
#{for issues|sortby=Summary ASC}
${Links[n].Summary} <--issue-->
#{end}
&{end}
I've tried all possible variation. What do I wrong?
Could anybody please help me?
BR,
Bernhard
The &{for issues} does not allow sorting.
Please use #{
for
i=JQLIssuesCount|clause=...
} ...
#{end} where you can write a JQL statement including the order by to sort the information.
Please check the Xporter Server documentation or the Xporter Cloud documentation (depending on the version you are using).
Any additional questions, please get in touch with Xporter Support; we would gladly assist you.
Thank you.
Kind regards,
Rogério Paiva [Xporter Support Team]
mmhm. The problem is the #{for issues|sortby}. Not the &{for issues|sortby=..} because
1) I use it and it works.
2) The documentation says it works.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sorry, my bad, it is possible to use the sortby in the &{for issues} as @Brigitte Bedard pointed out.
In your case, I would suggest using the JQLIssues since it allows more flexibility, however, if you prefer, you may use the sortby in the &{for issues} as well.
Thank you.
Kind regards,
Rogério Paiva [Xporter Support Team]
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.