TM4J Cloud Ideas

Search, vote, comment and create ideas for TM4J improvements. For more info on our review process, see here.

As a user, I can lock test cycles and test executions to prevent editing

As a user,
I want the ability to lock test cases, test plans, test cycles and test executions
so that users are unable to edit these areas.

  • Cristiano Caetano
  • Jul 6 2020
  • Future consideration
  • Attach files
  • Felicia Weick commented
    1 Sep 02:32pm

    Deita, Only to meet internal, department requirements. Everything you described (optional functionality, permission required to lock, etc) sounds great.

  • Admin
    Deita Howard commented
    27 Aug 11:20am

    Hi Sebastian/Felicia,

    This functionality will be optional. At the moment, we're planning the improvement to lock/complete a test cycle alone.

    A user will need permission to lock a test cycle too, so this shouldn't be a problem if you're not using the locking functionality (it'll be restricted for all users by default).

    Felicia - is this functionality something that you need to maintain audits/meet certain regulations?

    Thanks,

    Dee

  • Sebastian Lallana commented
    12 Aug 06:07pm

    Please don't this mandatory... test cycles can be (and should be) dynamic in agile contexts...

  • Felicia Weick commented
    6 Aug 04:37pm

    Needed functionality.

    As a TM4J admin

    I would like the ability to lock test cases, test plans, test cycles, and test executions

    So that

    • Additional test executions cannot be added or modified in a completed Test Cycle or Test Plan.

    • Closing a Test Plan also prompts to close linked Test Cycles.

    • Test Cycles cannot be modified after testing is complete.

    • Test Cases cannot be modified while locked.

  • +9