Finding myself wanting to use test cycles on unscheduled (version) as a logical grouping of tests, for example create a "Regression" test cycle and assign all tests want to run for regression for a JIRA project, that way whenever a new version is available to test, I just clone the "Regression" test cycle from Uncheduled version.
Now for the problem, soon as more tests are created, those tests are not added to the unscheduled "regression" tets cycle I described above. Seems to me more fitting to just have saved filters for "Regression" tests that have a "Regression" test cycle that will be out of date/missing tests soon as some are added.
Am I missing how unscheduled test cycles should be used?
Additionally, it would be great if the test cycles (for unscheduled) can sync to a jql query/filter so that they are never missing appropriate tests.
I agree. Once I've added tests to a Test Cycle using a filter, and then a new test is added that meets the criteria of that filter, it doesn't seem to get added into the Test Cycle. I either have to delete the cycle and re-create or manually add the test to the existing cycle. Will this be fixed soon?
As a Belgian, beer-lover and home brewer, beer is one of my great passions. I love the fact that with just a few ingredients (usually just water, hop and malt) you can create so many different tastes...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot