How to lock a test cycle?

[ADF]

Users are editing past test cycles. How do we lock previous test cycles so they remain untouched? Because people are still able to edit these test cycles it is 1) impacting and changing our past metrics and 2) users can't find the changes they are making in the current test cycle because they are editing in the wrong test cycle. If this is not yet a feature, is there anything to do that could be a workaround? Thank you!

[Andy Rusnak]

Hi ADF, 

Welcome to the Atlassian Community!  

Just to make sure I understand you question, these past test cycles are associated with previous releases that are already completed and released?  

If that is the case, you should be able to Archive the release which could be configured to stop it from showing up in the interface when users are looking at the various Test Cycles.  

The page below provides some additional insight into this: 

https://support.smartbear.com/zephyr-squad-cloud/docs/test-cycles/archived-and-released-versions.html

Is this along the lines of what you are looking to do?  

Thanks!

Andy 

[ADF]

Hi Andy,

We will have 4 test cycles before we release anything. We are currently in testing cycle 2 and are looking to lock down 1. We would like the team to be able to refer to the previous test cycles so we don't wish to archive but we don't want them to be able to make changes.

[Andy Rusnak]

Thanks for the additional feedback ADF!  I have a better understanding of what you are trying to do now.  I believe this is related to this Idea request the Zephyr team is reviewing: 

https://z4j-cloud.ideas.aha.io/ideas/Z4J-I-208

You can set a Jira issue to not be editable in certain statuses via the Jira Workflow Configuration, but based on this Idea linked, I do not believe that it applies to test cycles.  So I do not believe that the functionality exists today for Test Cycles.  

If you have questions on locking Jira issues based on Jira Workflows I am happy to try to answer those, but I do not believe that will apply in this situation.  

Best, 

Andy