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?
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.
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!
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!
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.
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!
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.
https://support.getzephyr.com/hc/en-us (submit a ticket)
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.
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?
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
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.
It’s very important to have access to the workflow process from anywhere. Especially if you manage the work of others. There is no difference whether you’re out of office, or drive a ca...
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