Zephyr Capture for JIRA
Rapid agile testing.
Total ratings
1.75
(Rating count:
4)User reviews
Recent rating average:
2.13
All time rating average:
1.75
Rating filters
5 star 4 star
3 star
2 star
1 star
| Date | Author | Rating | Lang | Comment |
|---|---|---|---|---|
| 2021-01-20 |  | | en | Have been using this tool in conjunction with Jira for a few years now as most of the alternative tools don't have the flexibility my workplace tasks need, and while previous versions of Capture were buggy, clunky, crashed a lot and giving me continual headaches, and support teams instructions to clear caches and reset in response to these issues seemed a little convoluted and usually didn't work. the 13 September 2020 update appears to have fixed a lot of these issues. I had to remove the tool and reinstall it at that time in order to log in, but since then it has been behaving much better. I like that it contains a link to set up the API within the log in page and details can be remembered, makes it easier to train new staff in setting up and using it. I have not yet had an error to be able to see whether clearing caches are going to be easier to resolve myself. Relatively minor dislike is that I can no longer use [~username] of a coworker to mention them in a description, it converts to an odd generic user tag once the issue is created in Jira so I have to redo it there. I have been told that to do that now the username tag includes a unique string of numbers and letters, which is impossible to remember for each coworker compared to the old way. Thanks for the improvement in this version! UPDATE 12/12/2024 I gave this 4 stars in Jan 2021 having seen improvement, but since then it has gone downhill again. We are back to constantly receiving error messages when trying to log in, that we can't move past to use the extension, and no matter how many times we raise cases with Smartbear, they ask us to go through the same troubleshooting moves again and again and are unable to replicate the issue themselves. Then we might have a brief period of it working, then something will randomly change and most of the team can't use it again. This really holds up productivity. the link to Smartbear support provided within the error message opens up a blank page, and other parts of the Smartbear support site reached through other avenues are convoluted, seem to have old information, and it's hard to know if the issues we are experiencing are widespread or unique to our team. Name changes to products over the years confuse the search for information further. |
| 2022-01-13 |  | | Does not log into Jira Cloud. I've tried multiple times and it always fails. I've attempted to visit the support link provided in the error message, but it simply navigates me to a white page. This plugin feels like it is no longer supported. | |
| 2022-01-13 |  | | en | Does not log into Jira Cloud. I've tried multiple times and it always fails. I've attempted to visit the support link provided in the error message, but it simply navigates me to a white page. This plugin feels like it is no longer supported. |
| 2021-01-19 |  | | Have been using this tool in conjunction with Jira for a few years now as most of the alternative tools don't have the flexibility my workplace tasks need, and while previous versions of Capture were buggy, clunky, crashed a lot and giving me continual headaches, and support teams instructions to clear caches and reset in response to these issues seemed a little convoluted and usually didn't work. the 13 September 2020 update appears to have fixed a lot of these issues. I had to remove the tool and reinstall it at that time in order to log in, but since then it has been behaving much better. I like that it contains a link to set up the API within the log in page and details can be remembered, makes it easier to train new staff in setting up and using it. I have not yet had an error to be able to see whether clearing caches are going to be easier to resolve myself. Relatively minor dislike is that I can no longer use [~username] of a coworker to mention them in a description, it converts to an odd generic user tag once the issue is created in Jira so I have to redo it there. I have been told that to do that now the username tag includes a unique string of numbers and letters, which is impossible to remember for each coworker compared to the old way. Thanks for the improvement in this version! | |
| 2020-09-30 |  | | Hi. Im facing a problem. When i try to login to Zephyr Capture it gives me this errors : "The JIRA server returned an empty response when valid JSON text was expected. Please check your server configuration." "The JIRA server could not found, or the Capture for JIRA plugin is not installed." And i cannot login into Zephyr with my JIRA. Thank you | |
| 2020-09-30 |  | | en | Hi. Im facing a problem. When i try to login to Zephyr Capture it gives me this errors : "The JIRA server returned an empty response when valid JSON text was expected. Please check your server configuration." "The JIRA server could not found, or the Capture for JIRA plugin is not installed." And i cannot login into Zephyr with my JIRA. Thank you |
| 2020-08-17 |  | | Nice when it works, half the time it complains the API key has expired (it hasn't) and you need to revoke and reissue a API key. | |
| 2020-08-17 |  | | en | Nice when it works, half the time it complains the API key has expired (it hasn't) and you need to revoke and reissue a API key. |