ContributionsMost RecentMost LikesSolutionsCustom Status should not default to Done When using the status "Blocked", a test case execution is considered "Done". We most often use "Blocked" as a temporary status to note when something's start or work is impeded, however, it instead gives the team credit for complete work. We introduced a custom status instead, but all custom statuses are also considered "Done". Zephyr Scale should allow us to indicate whether a custom status is "Done" or not. Re: How to modified project name for Zephyr Scale Just chiming in that I would also really like to see Zephyr Scale either automatically pick up a new project key or give the Admin the ability to update it. We recently made some changes to our project structure which included some key updates, and now there is a complete disconnect between Zephyr Scale and Jira. It's not even picked up on *new* Test Cases. View for Users to See All Assigned Executions I am trying to figure out a way for my users to find a quick view of all executions assigned to them. Scenario: We have dozens of Testers with executions assigned across numerous Test Cycles. These users are not super Jira or Zephyr-savvy. Their interactions are executing and opening Bugs only. In the Cycles view, there is an option to filter cycles by Assignee, but it does differentiate between passed and open Test Executions so it's moot. My idea: Build a Jira Dashboard where they can log in and see their work. I've created a few Jira OOTB gadgets that work great - Query Results showing their Bugs, etc. However, none of the Zephyr gadgets use JQL, so I can't leverage currentUser(). That means my only option is to build customized Dashboards for every single UATer and maintain them forever, which is not great. First, any ideas or better suggestions from anyone? Second... Feature request for SmartBear. Create a JQL Query that mimics "Issues reported during testing" gadget I am trying to create a query and I'm not having much luck. I am trying to mimic the"Issues reported during testing" gadget. This returns all issues created on any project that was the result of whatever criteria you put in (in my case, all Issues created from Executions in specific Test Cycles). This is a very helpful way to monitor Bugs created during testing. However, the gadget is too limited to be useful - you can't sort, you can't customize the columns, you can't filter out resolved issues, etc. I was hoping to use the more flexible "Filter results" Atlassian gadget and write a query that mimics the "Issues reported during testing" Smartbear gadget - but I cannot seem to make that work using the Advanced Search With JQL Functions. I can't believe not a single one of these allows you to isolate issues created from a Test Cycle. In fact, none appear to even take Test Cycle as a field/value. The Covered By filter only works for Issues linked via Traceability and not those added on the Test Steps of an Execution. I could be reading this wrong. Any ideas? I'm stumped. Re: Tracking in Zephyr Scale - Multiple Testers per case and results by step Chiming in that my company also needs this. This seems like such a basic testing functionality to be missing.... Multiple Users Execute Same Test Case We have end-to-end testing across platforms. Is there a way to assign test steps to different testers (aside from repeatedly reassign the whole TC)? Move an Execution to a Cycle Users have created executions ad hoc from the traceable issues instead of in a cycle. I cannot figure out how to move the execution into the cycle so we can appropriately report/track progress. There are too many notes and attachments to make manually moving everything reasonable. Solved