Zephyr Scale Server/DC Ideas

Search, vote, comment and create ideas for Zephyr Scale improvements here. For more information on our review process, see here.

As a user, I can add approval/review workflows for test cases

As a user

I want to put rules in place/a workflow for the transitions of test cases/Jira issues

So that I can prevent changes to the test case/Jira issue that should not be allowed

Suggested improvements:

Test case approval
* Set permission for specific status of a test case (“Approved”)

* Set permission for editing test case - can only save with permission.

* Prevent test case from being edited once status has been set to “Approved” (force user to create new version)

* Set permission for locking a test case once it has been set to “Approved”

* Enforce test case status flow

* Workflow to prevent changing test case status from “Approved”

* Prevent tests from being executed if they haven’t been “Approved”

* Prevent Test Case owner from changing status to "Approved"

*Jira issue transitions*
* Prevent issue from transitioning to status if no test case is linked

* Prevent issue from transitioning to status if test case linked is not approved

* Prevent issue from transitioning to status if no test execution exists for linked test case

* Prevent issue from transitioning to status if not all tests are passing

  • Cristiano Caetano
  • Jul 6 2020
  • Future consideration
  • Attach files
  • Lynda Hooper commented
    2 Mar 10:26pm

    Would definitely like to restrict who can approve a test case and once a test case is approved, it can not be modified.

  • Julian Palmer commented
    15 Sep, 2021 12:32pm

    We want to do something similar.

    We have added a test case status of "In Review".

    We want a test case to have to go through states of Draft > In Review > Approved.

    Today all test cases start in Draft. We cannot force it to go only through the states we want.

    This could be a very simple "fixed" workflow. Perhaps just ordering the status values so that it defines the next/previous state. . Nothing as complex as Jira workflows is needed .

  • Ben Abrams commented
    17 Aug, 2021 07:15pm

    I was asked today for this same functionality by my VP.

    *Jira issue transitions*
    * Prevent issue from transitioning to status if no test case is linked

    * Prevent issue from transitioning to status if test case linked is not approved

    * Prevent issue from transitioning to status if no test execution exists for linked test case

    * Prevent issue from transitioning to status if not all tests are passing



  • Rachel Tam commented
    28 Aug, 2020 05:54pm

    Hi Deita,

    I'm open to arrange a call. What is your email so I can contact you directly? Or you can email me directly by getting my email from my profile.

    Thanks,

    Rachel

  • Admin
    Deita Howard commented
    28 Aug, 2020 04:11pm

    Hey Rachel, thanks for this feedback. We're planning to improve the approval workflow in TM4J.

    Would you mind joining a quick call with me sometime in the next week or so? It would be great to understand your process for this.

    Dee

  • Rachel Tam commented
    30 Jul, 2020 11:46pm

    It'd be nice to have the permission granularity to allow a group of users to ONLY approve a test case but not do anything else.

  • +3