When I Search Test Executions, select a few tests, then select Tools --> Copy to Cycle, I can't copy it to a different project. Why is this? If it's true that I can't copy it to a different project, then why make it even possible to select "Project" in that "Bulk Copy to existing/new Cycle" dialog?
I am just evaluating the whole solution, and when I noticed the Copy to another cycle with project option, I got so excited that I actually didn't notice at first that the end message says my tests were not copied.
I follow on the initial question - if you can only copy within same project, why in the first place have the combo to select a project?
As much as I was excited at first, I am really disappointed now. This would be a HUGE point to make when I throw a demo. I have setup one jira project only to keep non-regression test and cycles. I am suing structure to put order in them. I want people to be able to quickly and easily select tests they need for their project and copy them. No test will be executed in the regression project itself.
The workarounds are possibly, but I am trying to sell JIRa+Zephyr solution on easy of use and flexibility mostly, so that's a drawback.
Currently there is not a way to do what it is you are looking for in Zephyr for JIRA. Zephyr for JIRA is 100% project based. This means that you can not copy or share test cases or test cycles between projects. The tests and cycles that you have in each projects will be there and only there.
There are two ways to get tests out of one project and into another. One is to export the tests out of project A and then import them into project B.
The other is to copy the test case you want to add to another project. Once copied, you can move the copied test case to another project using the JIRA move abilities.
However, what you are seeking is available in our Zephyr Enterprise Edition. In Zephyr Enterprise you can easily copy tests from one project to antoher. Meaning, you can have one main project that contains all the test cases, and then the other projects and copy the tests out of the main project as they need them.
This is unfortunate.
Our scenario is that we have projects that are definitely different products and defined as different projects, but could affect common areas as other products. There are regression tests that we need to run that are common to multiple products and projects. If we had the original tests in ProjA, then export it to ProjB to run, any updates we make to the tests while running them in ProjB will need to be back ported into ProjA.
As I said, I know there are workarounds possible, but having the option to copy to different cycle in different project as the option in the menu suggest is super easy and functional. Workarounds require to use different tools, pages and so on, instead of working from one place.
I think I got something that may help all of us: Let me know .
It is the "Copy Structure" functionality that can clone your existing template structure into another project.
NOTE: Before we start using this feature - Breakdown of STRUCTURE should be by functionality.This will allow teams to copy only what they want to map between projects.
Step 1 – Navigate to Structure / Manage Structures / ALL /
ONLY STRUCTURE that has been shared with all Jira users will be visible.
(In order to do this - structure should be available to ALL and permissions can be setup from below page.)
Step 2 - Select COPY link under Operations column for the structure you want to use test cases from. Let Copy complete.
Step 3 - After copy is complete – each original test case Key # associated with Project A will be given a new Key# associated with Project B.
Step 4 - Go to Project A Test Cycle and search for key# of this new test case from Project B that just got added. Test case successfully added.
This approach requires you to have the JIRA administrative rights. The main aim of this article is to help you achieve an organized, easy-to-maintain workflows in your JIRA instance thereby, reducin...
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