Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Can Zephyr tests be created as a sub task of a story in jira

I found that zephyr test can be linked to a story, but I need to create a test task in jira and then a zephyr test and then link it . Instead if directly jira allows me to create a zephyr test task as a sub task in a story . it will reduce the effort . Please let me know whether this requirement is available or not?

33 answers

1 accepted

6 votes
Answer accepted

Hi Archana,

Currently Zephyr for JIRA does not support creating subtasks. The bug will have to be manually converted to a subtask.

We have added this ability to our feature request list and I will add your endorsement. What the feature request list means is that our product team will review this list and decide what features to add in future releases.

Kind Regards,


We have run into the same challenge and did the same as Archana's team to resolve it. It would be nice to see the Zephyr test directly linked to our stories (without having to create an extra issue and link them together), so we can see when all of the sub-tasks/tests associated with a story are done. That way, it's much easier to make a story as complete.

Please add my endorsement to this request, as well!

Emily could you please add my endorsement here as well, this would be a huge benefit to our workflow.

We also use Zephyr and such missing functionality is big gap. I'm waiting for possibility of adding tests as sub-tasks to story

Please also add me to the endorsements!

Do you have a public link to this feature request?

This is understood as KEY FUNCTIONALITY for us, as we are totally restructuring our JIRA instance. We want the ability to standardize a set of sub-tasks under a story, and having the Zephyr test as part of these is not only nice, it's the RIGHT WAY to have a natural flow and prevent silly duplicates!

Like Mridula Wittke likes this
Deleted user Sep 07, 2014

Please add me to the endorsements. It's a must have!

Please add my endorsement for this as well. This would be a huge benefit for our workflow

Hi Emily, Do you have any news on this? Meaning is this planned for a future release or is this feature even on your backog? Is there a feature request that we can officailly vote on ? KR Johannes

Repeat of question from @Avira Operations GmbH & Co. KG above - @Emily Schneider - was this entertained and implemented - and - as such is available now?

Any progress on this? I want to recommend this software to stakeholders but not having a test event as a subtask of a story is a killer.

Endorsing as well. We are presently gradually moving to using Zephyr, and would love to include Test sub-task, or Sub-Test, to existing JIRA issue/task/story instead of linking. 

Please add this as priority!

We really need this as a feature.

Also Endorsing, but it seems Zephyr has stopped responding... Will the feature ever be added?



It will be super helpful to have that feature!

We're getting started with Zephyr, and this also seems like the obvious way to integrate tests into our workflow. Our team would also like to see this feature.

We also would like to have this subtask feature to be available soon. But it looks like they haven't accomplished this request since 2013.

We also want to be able to add tests as sub tasks to stories.... 

A better solution would be to make it possible to create new issue types with the same functionality as the existing issue type "Test". This would mean you can add testing steps, perform executions and add to cycles,...

This way you could also create a new sub-task issue type with the full zephyr power.

We are stuck with an issue after including the Zephyr Add-on to JIRA cloud.

JIRA does not have the issue type TEST, so when zephyr is added, it is not letting me create Test as it cannot find Issue type TEST.

Any solution for this

Please add this a.s.a.p.

This question has been open for nearly 4 years. Whilst the initial responce was hopeful, the time lag in any update does not give me confidence that this feature (or more to the point, removal of restriction) is forthcoming, or that there is any intention to implement and role out this feature. Please, eihter infiorm your customers of your roadmap for this, or just simply state that you have no intention on delivering this. You are impeeding my workflow enough without having to go chase responces to this question. Creating tests as sub-tassks just to have to convert them back to tests is a pain in the back side! All I want is to have my relevant tests shown within the story they belong to! 

I agree, I need the same feature, but i see no response from the Jira/Zeyphr team

@Emily Schneider,

Do you know if this feature has been reviewed? This is would reduce a lot of work load. Would be nice if this is released in near future.

Thank you!

Since we are a year down the road, does anyone know if this is now possible?


Thanks for leaving your comment on the Atlassian portal, but please see our link below to have direct correspondence with Team Zephyr's support staff. They will be able to answer any technical questions you may have. (submit a ticket)


Thank you,

Team Zephyr

This would allow us to keep Zephyr.  Please add my endorsement.

Agreed that this is critical functionality. It really makes the whole integration way more cumbersome than it needs to be. Testing of a user story is inherently a subtask of the Story, not some separate but related task. The user story isn't done if it's not tested. 

I have a similar situation now. We are currently evaluating Zephyr JIRA plugin for use in our projects. 

Please update on a tentative time when this would be available.

Appreciate an early response.

HI JIRA-Zephyr Team, I see this ticket tagged for almost 5 years now. Do you have an update on this?

Wow, 5 years later and it's still wasn't resolved.... This is important functionality request. I can't believe it after all these years it wasn't resolved.

Actually, I'm evaluating Zephyr among other test management tools. This feature was one of the main topics to validate our candidates, but I don't know what to think about this 5 year discussion not going anywhere.

Hi Janet,

I have also added your endorsement to this.

Kind Regards,



This would be a real benefit.

Currently, we have to select each 'linked' test to see if it has passed.

Seeing the test as a sub task would give much more visibility.

Hi Eric,

I added your endorsement to this request.

Kind Regards,



Any update on when this would be added to Zypher? Please let me know.



I'd just quickly like to add that would also find this very handy to do.

I have a section of a site (homepage for example) I’m testing which has a number of scenarios, these scenarios I would like to separate into tests however linking them as a sub-task to the main item being tested.

For example:

I would like to create a test item/ ticket called 'Homepage', which would then have all the user listed scenarios ("User wants to find out more information about X", "Y has no associated button target or text", "User must be able to carry out Z") as sub-tasks. These scenarios/ sub-tasks would then have the test instructions/ steps added to them, being able to split out the testing against various scenarios yet keeping them within the relevant section.

I would then expect to be able to easily report on the amount of coverage/ progress against a specific section through all the linked/ sub-tasked items/ scenarios. Also meaning that all sub-tasks must be closed before being able to close (sign off) the item under test.

Henceforth we have been creating two testing sub tasks for every Story - Create Test Case and Execute Test Case. Test cases were created in a spreadsheet or a Word document and attached to the Create Test Case sub tasks. This went well until we switched to Zephyr. In Zephyr we are now cloning a user story and updating it as a Test task. All test steps are then provided in this task with Create Test Case and Execute Test Case sub tasks linked to it. The result is that we now have an additional task, which we don't really want.

In a training session with Zephyr last week, we were told that Zephyr does not allow creating a sub-task. Does anyone know when this function is going to be available?

(I hope I read your post correctly)

Personally a Sub Task ticket in a Test ticket does not make sense since the Test ticket is the Testcase.

The following are the few CRITICAL Features, to add to the next version of Zephyr:

1) During the execution of test, If Status Selected as "FAILED" it must automatically generate a BUG with a Unique ID, along with sub task to assign the bug to a developer to fix it.

2) Add More fields instead of only 3 at Test creation. Like TEST STEPS, TEST DATA, EXPECTED RESULT and ACTUAL RESULT.

Wouldn't the Actual Result be the Bug ticket it's self?

Also if a Test Step failed and could possably be the same issue as an existing Bug or Test Step from the same Test ticket, that would cause ticket administration overhead by creating a duplicate Bug tickets someone would have to sift through.

Bugs cannot contain Sub Tasks either.

I am currently testing an evaluation of Zephyr for a very large enterprise. My goal is to move from HP ALM Jira integration to a fully JIRA process. We currently have our stories structured with 7 base subtask (very similar to Arshad Mehmood mentions below). Two of them are Create tests and Execute tests. My hope was we could put Zephyr sub tasks in our process directly without redesigning the process. This is not the case it seems. I am curious why creating zephyr tests would NOT be able to be subtasks to a story? To me testing is ALWAYS a subtask to the overall story process - we NEVER have testing at the story level. This makes our incorporation of Zephyr a non starter. I am not going to change our process flow to accommodate a tool - I already have that with HP.

Absolutely agree, when development breaks a story down into subtasks with QA as one, you should be able to make that task a Zephyr task so you can rollup the QA effort to its originating story. Now we must clone the originating task and make it a Zephyr task, which is not convenient or efficient. Thanks, Jill

Hi, any news on this?

can youi please add my endorsement for this feature too ?

Regards Robin

In true Agile Methodology, initial or unit base QA should be built into the scrum, and therefore the real need to have the test as a sub task.

Any update on this? My team is evaluating the trial version but not being able to add a test as a sub-task is a deal breaker for us. I'd love to find out if any progress has been made here or if it's in the works?

0 votes
Bibek Behera Community Leader Dec 22, 2015

Hello @Robin Bleeker, @Adda Birnir,

Our Product Management team has been made aware of this feature request. They will review the same for consideration. We appreciate your valuable feedback in making Zephyr for JIRA better.

Please do not hesitate to reach out to us at our support portal for any additional information.


Zephyr Support


Endorsing this as a way to remove overhead that provides no value.


has there been any update on this feature?



Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Marketplace Apps & Integrations

How to create a Confluence page linked to a Jira cloud ticket

Have you been looking for a solution to easily create Confluence pages directly from a Jira Cloud issue? The no code solution is here with the brand new app Elements Publish to Confluence, which work...

58 views 0 2
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you