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

Cucumber import appears to ignore steps and examples

When importing JSON files generated by Cucumber I expected that the option autoCreateTestCases=true would not only create the test case object, but also create the steps in the case and match success for the outcome in the execution object(s). That does not happen. I could understand that for JUnit imports as steps are not available, but  Cucumber reports have steps and steps have outcomes. So I wonder why they are ignored.

As I am using Cucumber with scenario outlines and examples, I am even more surprised that an example does not match to an execution, but there is only one execution. So the mapping appears to be on the outline level.

Am I doing something wrong here or does it mean that the cucumber endpoint is not able to deal with steps and examples ( meaning that I would have to write my own importer ) ?

1 answer

0 votes
Katy Kelly
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 28, 2020


We recommend moving this question and tagging SmartBear on it as Adaptavist no longer owns Test Management for Jira. Learn more.

Please direct your TM4J Server/DC queries to or TM4J Cloud queries to You can also visit their general support portal

Kind regards,


Adaptavist Product Support 

Thanks Katy.

I am clarifying how to pass the wall / gate of the support page.
( As I think, we should have corporate support here ... )

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events