JIRA Agile and Zephyr: Link Test to Story

Is it possible to link a Test to a Story? I've created an Epic, and a Story linked to this. Now I want to create a Test linked to the Story. But the only option I have for the Test is to link it to an Epic, which is really not what I want (this being, as I see it, two different test phases/levels).

3 answers

1 accepted

0 votes
Accepted answer

I had to find this out for myself: Tests can indeed be linked to a Story - or any other kind of issue. Just not while creating it. It has to be linked manually afterwards. The "Link to Epic" is apparently a rarely used feature, so I'm unsure why it's there when creating the Test.

Hi Frank,

It is important to note that a Zephyr test is a standard JIRA issue type. This means it follows the same rules as any other standard JIRA issue type. One of the abilities of the standard JIRA issue type is that you can link one to another.

My question is, is the Story you want to link the Test to a standard JIRA issue type? Or is it something else like a sub task?

Kind Regards,

Emily

Hi. The Story is a standard Jira Story. First, I created an Epic issue. Then I created a Story issue, linked to the Epic. It's the Story issue I'd like to link my Test to. (The Test is created from the Tests menu -> Create a Test.)

Here's how I'd like it to be:

Epic 1 <---- Story 1 <--- S-Test 1
Epic 1 <---- Story 2 <--- S-Test 2
                     <--- S-Test 3
Epic 1 <---- Story 3 <---S- Test 4
Etc.

The reason for this is that I'm exploring Epics as being similar to business requirements, and functional/non-functional/system/etc. requirements as Issues linked to an Epic. Just as a business requirement is on a high level, and has multiple functional etc. requirements linked to it, and Epic gets multiple Stories. And for testing, f.ex. systems testing is done against the Stories (functional etc. requirements), and f.ex. acceptance testing is done against the Epics (business requirements). However, if Zephyr Tests can only be linked to Epics and not Stories, then the test architecture and methodology gets severly limited.

Epic 1 <--- A-test 1
etc.

For some reason, I didn't see the general option to link issues to eachother. I can, of course, link a Test to a Story with "relates to". I'm unsure if this is the way it's supposed to be done? And I'm wondering why there is an "Epic link" field when creating the test, but no other link field?

Its not an answer to your question but seeking solution to my problem

 

i am wondering same. DId you find answer to it.
I have one more issue. Is there any way to see to which test case particular defect is linked to.
I can see Epic and defect relationship from Epic. But if i want to make sure if defect is linked or not to test case/epic. Is defect is left standalone?
Have you came across this issue?

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Oct 31, 2018 in Marketplace Apps

Marketplace Spotlight: Zephyr

Hello Atlassian Community! Each month, we run a series of Spotlights to highlight Marketplace vendors and apps that our team thinks this Community would find valuable. In last month's Spotlig...

333 views 0 1
Read article

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you