Customized Test Case Execution statuses need an option to turn the Defect button on or off
When creating a custom execution status, I would like the option to trigger the D button to appear, or not to appear The only statuses that do not trigger the D button to appear are "not executed" and "pass" Use case: I'm trying to create an "Approved" status, and I don't want the D button to appear. I could change the system default "pass" to "approved", but then then the custom status for "Pass" would trigger the D button.ability to set email notification "when a user has been added to Zephyr enterprise" as optional
Currently, whenever a user is created in Zephyr enterprise, an email is sent to the user's email account with the instructions on how to access zephyr. We would like a feature to make this feature optional or send a custom message to the new user with the instructions to access zephyr enterprise.Revert to previous git commit
Originally posted by user Alucryd to the Stoplight Community on 02/29/2024 at 08:50 ET. Hi all, we unfortunately made a mistake and wiped out a whole api definition, is there any way to revert our files to a previous commit on the basic plan? Couldn't find any way to view or edit the git history.19Views1like1CommentAuto-scroll within Administration
Most of the Administration section requires the user to scroll down to a specific area after making a selection. For example, in the Project Admin section, after clicking on a project, the user has to manually scroll down to edit or update the project. This is also the case in groups, user set up, role creation etc. There are multiple frames within a page, which requires the user move outside the frame and to scroll down after making a selection, this is not intuitive or natural for most users. Ideally, the application should auto-scroll after making a selection.Zephyr Test execution reindex failed:errorType":"ERROR","clientMessage":"We encountered some problem
Hi All, We recently came across this problem post successful migration from Jira server to Jira cloud with Zephyr App data. While following documentation for app data migration there is one step mentioned that you need to clear server cache from Zephyr configuration and perform Metadata reindex and Execution reindex. Metadata reindex works fine for migrated project while Execution Execution failing with below error: errorType":"ERROR","clientMessage":"We encountered some problems during processing this request. Please try again!","errorCode":111}" We have spent hours to figure out the issue and finally after comparing the project already exists which we can successful Execution reindex, cross verified the permission schemes for both project and identified the differences missing the addon role in migrated project, just add the role to permissions Administer project ,edit issues, browse permissions and solved the problem. Hope this will help those who struggle on last step during migration journey from server to cloud! If you still face issues let me know will try to help!962Views1like2Comments