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.
We are using R4J for requirements management. I have put together an excel export template but the sort order does not match the order of the R4J Tree View.
We are using the Issue Key as the requirement ID since this automatically generated and always unique for the project. The tree structure breaks down the various sub system of the project. The requirements evolve over time so new requirements (issue keys) are added to sub systems. This results in the requirements (issue keys) not being in sequential order.
Is there a way to force the output to match the R4J Tree Structure? Otherwise it is a painstaking long manual copy / paste exercise.
I also tried using the R4J Excel Addin's "download" and this also outputs and out of order excel spreadsheet!
Appreciate any assistance!
Here is the pretty basice template I am using:
Requirement ID | Issue Type | Summary | Description | Issue Links | Requirement Path | Hardware Platform | Hardware Version Used | Labels | Updated |
[[key]] | [[issuetype]] | [[summary]] | [[Description]] | [[linkedissues]] | [[path]] | [[hardware platform]] | [[hardware version used]] | [[labels]] | [[updated]] |
Hello @Ed Choromanski ,
thanks for highlighting this here. As usual, could you please create a service desk ticket for this issue at https://support.easesolutions.com/
So we can track the progress easier and analyze the problem better.
Form current investigation:
Best Regards,
Bernhard from Ease Solutions
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.