Hi Raghu,

Could you please send an email to support@almworks.com and describe in more detail, what are your actions, what is the observed result (a screenshot would be nice) and what is the expected results?

Thanks,
Igor

Hi

i was trying to copy the structure to another project. But i am getting error message saying that
Cloning failed
Problem: No issues to clone.

But i have issues in my project.

Can any one please let me know what might be the issue.

Thanks,
Raghu

Hello. What I'm trying to explain is that you need to use two existing features in combination. Feature 1: create a full copy of the template structure. Feature 2: copy/paste between structures.

You can check out those in the links earlier in the comments or on this video: http://www.youtube.com/watch?v=j4Rx60Xf9qc

If you still need help with those, please send an email to support@almworks.com to avoid sending many emails to other subscribers of this improvement request.

Thanks!
Igor

Following those steps does not create a new key so it is a copy of the original, not a clone. And if I then paste more than once, those items are Merged as the article says. At this point the only way we can achieve what we need is to create one structure in its own project, enter several copies manually of the template we need and move a set with bulk move when we need them. This will only work for our template that has about 20 items and not the one with 100s. Once we have the bulk clone feature we can move forward. In the mean time, I will attempt a video of what I am doing and upload to youtube, providing the url.

Please check the documentation article I mentioned earlier about copying full or partial hierarchy from one structure to another: https://wiki.almworks.com/x/cwBy

Basically, it's Ctrl+A, Ctrl+C, switch structure, select parent, Ctrl+Shift+V.

I went to Manage Structures, and did Copy for the template structure and cloned the issues. Then went to Issues and did a filter for those new issues. Performed a bulk move to another project. Then I could drag those into it's structure. The only issue with this is losing the hierarchy and that's a big issue.

Will try that and get back to you.

The idea is that first you create new, unique issues, using Copy+Clone operation. It creates a new temporary structure. Then you move those new, unique issues into the structure you want them in.

If I do that, then the copied in objects are updated everywhere they are used, correct? They need to be unique.

Yes, I understand that - the approach I offered in my first comment was to create a full clone of a structure and then copy/paste the new issues (with a limited number of keystrokes or mouse actions) to the target structure.

Would that work for you?

We need to bulk clone from within one structure to within another. I just tested the template structure, but you can only clone the issues to a brand new structure, not to a certain point in an existing structure. For multiple items, we need to clone them and be able to put them at a certain point in another structure. We need to do this several times in the same target structure with new keys on each multiple clone/move. For instance, if we can bulk clone within MyStructureForTemplates, then bulk move them to another project/structure, we could get by. Or just a bulk clone over to the new project/structure without having to do the move.

Project 1/MyStructureForTemplates:
Epic template
Story template
Task template
Task template

Project 2/Structure 2:
Clone1 Epic template
Clone 1 Story template
Clone 1 Task template
Clone 1 Task template
Clone2 Epic template
Clone 2 Story template
Clone 2 Task template
Clone 2 Task template

In fact there is bulk cloning of the whole structure in Structure now, with cloning every issue - have you discovered it yet? Check out https://wiki.almworks.com/x/6Aqf and https://wiki.almworks.com/x/8gqf

If that doesn't work for you, please let me know how it's different from what you need.

Thanks,
Igor

One more note, we would be cloning the template from PR/STR 1 to PR/STR 2 under each epic in PR/STR 2.

Bulk clone would be good as well. We could clone within the same project/structure, then move those to another project/structure. But that would also require a bulk move. As of right now, there is no easy way to create a "template" of numerous issues in one structure as a template and then clone those for use in another structure. We are stuck. We will have 100 or more test considerations to clone for each new enhancement.

The problem I am running into with this is we want a separate instance of the issue, not a copy. The copy means if you update in one structure, it's updated, which we don't want. The cloned issues need to have key prefixes like the structure they are being copied into so they show up on that planning board in GrassHopper (or be a part of the project or whatever it is they need).

Thanks for your suggestion! We'll be working on improving bulk-cloning in the future.

But currently, you can combine full copy-clone of a structure with a multiple copy/paste functionality: you can select multiple issues in one structure and insert them into another - see https://wiki.almworks.com/x/cwBy

Something like: (a) copy the template into a temporary structure TEMP; (b) use copy-paste to copy all issues from TEMP into your target structure at the desired place; (c) delete structure TEMP.

Hope that helps!
Igor