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

It possible to import test cases with associated datasets using the test case importer?


 I'm using Xray in Jira and I would like to know if it possible to import test cases with associated datasets using the test case importer?
If possible how it is done?

Thanks in advance

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.
Sep 22, 2021

Hi @Ana Fragoso 

Sorry, currently, it is not possible, but it is a feature we have in the backlog to include in the product.

Thank you.

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

it would be nice to see this feature soon. @Rogério Paiva - Xray Xporter Can you please provide a reference to this backlog issue (if possible)

Just to add on this note: I have tried using the parameter in the Test Step / Data column during the test case import eg: ${User}. The dataset once defined with the same name it gets mapped :) 

I see the same thing.  Thanks for confirming. 

However, I noticed when using Xray Document Generator, the exported Excel strips the parameter placeholders.  For example, instead of exporting the Action "On screen ${SCREEN}, select...", my export says "On screen , select...". 

I realize that the Dataset data is not being exported, but stripping the parameter placeholder from the Action makes most of my Steps unreadable.

Is there a way to force these parameter placeholders to not get stripped?

Suggest an answer

Log in or Sign up to answer