Retrieve user stories from JIRA

Once the integration with Jira is set up, it is possible to retrieve Jira user stories in Testersuite Test cycles. A requirement is created in Testersuite for each Jira user story. This allows the user stories (requirements) Testersuite tested in Testersuite . The following image is a conceptual representation of the integration:

Once the integration with Jira has been set up, Test cycle Jira action button will appear in the tree view of a Test cycle . This action button can be used to retrieve user stories:

When a Jira project Test cycle linked to the Test cycle (see the image above), retrieving Jira user stories involves two steps:

  1. Step 1/2: Select one or more sprints from the linked Jira project
  2. Step 2/2: Select the user stories from the chosen sprints and retrieve them
  3. Next, a requirement is created in the Test cycle for each Jira user story

If no Jira project Test cycle linked to the Test cycle (see the image above), retrieving Jira user stories involves three steps:

  1. Step 1 of 3: Select a Jira project (you can always change this later)
  2. Step 2/3: Select one or more sprints from the linked Jira project
  3. Step 3/3: Select the user stories from the chosen sprints and retrieve them
  4. Next, a requirement is created in the Test cycle for each Jira user story, Test cycle the Test cycle linked to the Jira project selected in the first step.

For more information, see also: Test cycle with Jira sprints

Link to the original Jira item in the comment line
When a user story is retrieved from Jira, a comment line containing a link to the original Jira user story is added to the newly created Testersuite . If the requirement Test cycles used in different Test cycles via the Master List, that comment line is retained. This ensures you always have a reference back to the original Jira user story.

Please note: Fields are synchronized between the Testersuite and the Jira user story only in the Test cycle the user story was originally imported. Any other instances of the requirement (for example, if it was imported into a different Test cycle via the Master List) will only contain a reference to the user story in the comment field.