Zephyr for Jira Cloud... Tests Cases in separate project?

[Darlene Adler]

I'm looking at Zephyr as a tool for my team and investigating the best way to organize Test Cases.  I can foresee that Projects in our system could be sunset or change, and I wonder if I should put the Test Cases in their own Project, as opposed to creating them within the individual Projects.

I created a Project and set it up with only Epics and Test Cases.  (I had originally thought to use Epics to organize Test Cases for specific areas of the code, then realized that I could use Components for that.)  I'm wondering if anyone can suggest why this is NOT a good idea.

Thanks!

[venkatesh4317 · Accepted solution]

HI. @Darlene Adler

In addition to "components" you can also use "Lables" to organize the test cases / jira issues.

[Dan Nelson]

We did this when we first got JIRA and the biggest downside we found was the one project with all the test cases (thousands in a short period of time) would respond very slowly.

Over time we ended up moving the test cases into the projects where the corresponding JIRA ticket was located. 

Still not the best because some test cases would spawn projects due to our setup. But it made the test case management more managable.