Forum Discussion

josh42's avatar
josh42
Community Hero
4 years ago

Automatic Traceability Links in Zephyr Scale Cloud

Hi everyone,

right now, we are using Zephyr Scale Server in our company but we are (as a lot of users/companies probably are) evaluating the move to the cloud app.

Now, regarding the traceability in the cloud app, I'm at a bit of a loss and maybe those, that already use the cloud app, can shed some light on this.

 

Recently, we got a test account for the cloud app of Jira including Zephyr Scale and I have been looking into the differences between server and cloud. One thing that is very important to us as a financial service provider in Germany is the traceability between issues, test cases and test executions. I can link test cases to issues and link issues to test executions, just as I can do in the server app.

 

In server, if you execute a test case covering an issue and you link another issue to the test execution, you automatically get the link between issue 1 and 2 (e.g. requirement and defect) shown in the respective issues.

This does not seem to happen in cloud. All I get is the link to the impacted test execution. This means, that to trace the connection between requirement and defect I have to do a lot more work (clicks) than in server.

For example, a defect is created from a test execution in Zephyr and assigned to a developer. He/she opens the issue and wants to know, which requirement is impacted by this defect. Since only the impacted test execution is shown in the defect, he/she has to click that, then click the corresponding test case and then go to the traceability tab of that test case to finally be able to get to the requirement.

Also, I do not have the option to configure Zephyr in such a way, that test cases (including their execution history) are automatically linked to created defects (as 'blocked') which we use regularly to better manage re-tests of defects.

 

So the question for all you cloud users out there. Am I missing something? Or is this really a limitation of the cloud app?

 

Sorry for the long post and thanks in advance for any info. 😉

 

Cheers

Josh

 

Cloud
TRACEABILITY
Zephyr Scale

3 Replies

Sort By
  • BibekBehera's avatar
    BibekBehera
    Icon for Alumni rankAlumni
    5 years ago
    Copy Link

    Talsht 

     

    Please update delete and regenerate the api keys and give it a try.

    Also please send the data as  raw >>JSON, it should do the trick. 

     

    If you are still facing the same issue please feel free to create a support case and we will be happy to help you!

     

    -Bibek

     

    • Talsht's avatar
      Talsht
      New Contributor
      5 years ago
      Copy Link

      Hey,

      thank you for your reply.

      Sorry for the delay, I was away for the holidays.

       

      Well I tried following your solution and to delete and reapply a new key and to send as a raw json.

      I did not work however and I got the exact same result.

       

      What did work was adding the cycleId in the request data itself.

      From the documentation the cycleId is optional in the cloud API, however in the server API the cycleId is mandatory so this is where I got the inspiration to try it here as well.

       

      did not work:

      request = {"status": status, "projectId": project_id, "issueId": issue_id, "versionId": version_id}

      did work:

      request = {"status": status, "projectId": project_id, "issueId": issue_id, "versionId": version_id, "cycleId": "-1"}

       

      This has indeed solved the problem and you can now close the post.

       

      I do strongly suggest updating the documentation to reflect that the cycleId is indeed mandatory and not optional (or maybe change the request validation so the response is not an ambigious internal server error...)

       

      Sincerely,