How to populate new version with issues and test from the previous version as a template?

[Dustin Welty]

I am trying to implement a hardware project in Jira. These are large-ish projects 12-18 month complete device designs. There are a lot of requirements that go into the project. It will take a good amount of time to build each requirement as an issue as well as build test cases for each requirement. So far what I have implemented is:

• Epic to list overall project objectives, use cases and rationale.
• Requirements (task) linked to the Epic to describe a specific functional requirement including a description, acceptance criteria, and rationale. These are also marked as essential, conditional, or optional.
• Sub-Requirement (Sub-task) These are detailed Engineering requirements built off of the parent functional requirement. Again containing description, AC, rationale and priority.
• Zephyr Tests built for each sub-requirement and possibly for each requirement as well.
• Zephyr cycles used to group and execute the tests are each phase of the hardware project.
• Additionally sub-requirements are grouped using components based on the type of work or who will be completing the design/work (in house/vendor).
• All of the issues are then assigned to a version for the generation of the device being designed.

My objectives for implementing the hardware project in Jira are:

• Create the data in a more manageable format that can be used to generate reports and better share with others.
• Use work follows and test to verify and validate each requirement in the design
• Capture the link between Requirements, Engineering requirements, tests and test results.
• Test results are captured with date and the assignee.
• Once a product generation is set up in Jira with all the issues and tests, the next generation of the product would be a clone with modifications made to the requirements.

So here is the main problem I have not over come. How do I take all the issues and test for one release and clone them to a new release so that all the work of setting up the relationships between requirements and test doesn't have to be redone.

What I have tried.

• Export all issues and test to CSV keeping all the fields.
• Modify CSV to break the like (remove Issue Key) to the original issue, bulk edit to change working to new rev, and change the version.
• Use the Jira external project importer to load the issue back in.

All issue import with relationships as expected! However the tests loose all of their test steps.

Any ideas on a way to "clone" all the issues as described or if there another way to attack the tests?

Thanks!

[Bernhard Doleschel _Ease Solutions_]

Hello Dustin,

I´ve verified your requirements with our add-on R4J - Requirements Management for Jira, it is possible to create a set of new issues in one step, keeping the links to the original tests. Additional to the option to "reuse" a bunch of issues/epics for new project you can use various features to manage your issues (any kind, not only requirements). E.g.

• Setup a full customizable tree structure
• A reading view which considers your structure - like chapters in Word
• Suspect monitoring for changed issues (and it´s effect to linked ones)
• Coverage and Traceability view to get your linking cleaned up
• Revisions and Baselines for a full history of changes
• Reuse of issues and folder structures across projects 
• Export features by your own templates

If you interested in a free 90 min demo including your use case please contact me via our service desk. You can test R4J for free, just download it from the marketplace.

Best regards, Bernhard (I´m employed at the vendor of R4J)

[Marlene Kegel - codefortynine]

Hi Dustin,

I've recently tested the compatibility of our Jira cloud app Deep Clone for Jira with Zephyr.

Deep Clone for Jira is a cloud app, which enables among others to bulk clone up to 5000 issues at once.

It is possible to clone zephyr test cases and test steps. But zephyr attachments are not cloned.

You can try out Deep Clone for Jira for free to test if it could be a solution for your problem.

If you have questions or feedback about our app, don't hesitate to contact our support team.