Linking testing issue (bug) to original issue (user story) in Capture and Jira Agile

I am using JIRA Agile to create story issue types. Then I am using Capture to create test sessions and potentially new issues or bug issue types that relate to that story (issue type).


I have two problems or questions:

1) When using the Chrome capture browser extension to create a new bug, I cannot create a template that includes the ability to link the issue to another issue (thus I cannot link a bug to it's parent user story on creation in the extension).

2) I can manually add the linkage between the bug and it's parent user story after I create the bug, but it seems to me that by virtue of a test session being linked to the user story, that any issues/bugs created during that session should automatically show as related to the issues at the test session level. Did I just not set up my test session correctly?

Seems like a pretty common thing to have a user story and then a bug that relates to that user story and that they should be easy to link together.

1 answer

0 votes

Hi Jann!


1) JIRA Capture displays just the same fields, that are present on the issue create screen. 
If the 'Linked Issues' are present on the JIRA's Create Issue Screen, it will be visible on the Issue tab of the extension too. Fields that are visible on the Create Issue Screen screen can be configured on the Screen tab of JIRA Administration pages.


JIRA Capture does not support 'Linked Issues' in templates, so this field to be selected each time issue is being created.

2) I think it does not make sense to link test session to the story, just because it's up to the teams to decide the number of stories they are going to cover in a test session. Maybe someone would like to test the work tracked as epic?

Test Session makes it easy to triage all the issues raised: all the issues are shown on the Test Session page. See the example of Stash team test session:


You can see all the issues in the JIRA Issue Navigator by clicking the eye icon on the test session page:

 Capture 2015-05-05 at 13.46.28.png

Image 1.


 Issue Navigator shows all issues raised during the test session:

Capture 2015-05-05 at 14.05.43.png

Image 2.


It would be easy to Bulk Link then, but this is not yet implemented


But you can link them easily using following technique.


  1. Memorize the JQL for all the issues in Issue Navigator (Image 2).
  2. Open your story issue in JIRA. Click More -> Link.
    Capture 2015-05-05 at 14.09.24.png
    Image 3.
  3. In the Link dialog, select search for an issue.
    Capture 2015-05-05 at 14.00.12.png
    Image 4.

  4. In the Find JIRA issues dialog click Advanced Search.
    Capture 2015-05-05 at 14.00.37.png
    Image 5.
  5. In the Find JIRA issues dialog paste the JQL you've seen in Image 2, select all the issues you'd like to link:
    Capture 2015-05-05 at 14.23.33.png
    Image 6.

  6. Click 'Add' to submit the dialog.
  7. tick Congrats! You have Linked all the Test Session Issues to the Story!


I hope this helps!




JIRA Capture Developer at Atlassian.

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

2,760 views 11 18
Join discussion

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
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot