How to create a template with epics and stories for structures

[Sergio Alonso]

Hi everyone,

I'm trying to find a solution to a challenge I'm facing right now, and I would like to know if someone had the same problem and how you solved it.

I'm leading a program composed of several projects, and I created a playbook in structures with a hierarchy (parent/child) with epics and stories.

I thought it could be so simple to replicate it as copying the structure and pasting it to another one. Still, the problem I'm encountering is, when pasting it, the epics and stories are the same as the original (same project ID - number) and what I need is that those "clones" should have their own "PROJECTID-XXX".

Do you know if what I want to achieve is possible? Is there a solution without an external plugin (we can't buy them as it should be applied to +18.000 users)

Thank you!!

Sergio

[Valerie Knapp · Accepted solution]

Hi @Sergio Alonso , thanks for your feedback. Sorry, I don't manage to reply to your comment directly for some reason so I will just write you here.

As far as I know, what you have described is something I used to be able to do in data center / server with a ScriptRunner script https://docs.adaptavist.com/sr4js/latest/features/built-in-scripts/copy-project#:~:text=From%20ScriptRunner%2C%20navigate%20to%20Built,the%20project%20to%20be%20created. 

I understand what you are trying to achieve but I think anyway it won't be possible to copy and paste a core set of issues from one project to another, at least not without some kind of scripting or app. I would be happy to be wrong though, if anyone else has some ideas.

Cheers

[Sergio Alonso]

Thank you @Valerie Knapp , it is what I was expecting... Do you know if would be possible to create a template in Structures APP? as this would be the best thing I could achieve.

[Valerie Knapp]

Hi @Sergio Alonso , thanks for your feedback. When you say Structures, sorry to be pedantic, do you mean Structure?

I know in BigPicture, for example, you can clone he scope of another project, like this from within the Gantt module of a box -

But this would required you to have the BigPicture app. You could install it and try it out if you want. https://marketplace.atlassian.com/apps/1212259/bigpicture-project-management-ppm?hosting=cloud&tab=overview 

Cheers

[Valerie Knapp]

Hi @Sergio Alonso , thanks for your question.

Please can you clarify a few things?

When you say you have created a playbook in structures? Do you mean with the app, Structure?

I have understood your desired outcome is something like a board with different projects included and their issue hierarchy displayed in the board.

Also, you want to impose a standard structure for how the issues are related in different projects.

In terms of a board that has multiple projects and their issues, you will likely need to use Advanced Roadmaps or Plans to achieve this, or an app, which you said you wanted to avoid.

In terms of implementing a standard structure, or starting point for projects, in terms of issues and hierarchy, you could use a global automation for this.

For example, I just tested this and it works

Then, in Plans, you can add the projects which have the same issue structure from the automation to get a view like this - 

Is this what you wanted? Does it help you at all?

If not, or you have more questions, write us back and either I or someone else will try to help.

Cheers

[Sergio Alonso]

Hi @Valerie Knapp, thank you very much for your message and your time dedicated to it.

To be honest, what I'm trying is different from what you just mentioned, I have the structures view already with the epics and tasks, stories, etc I need, and what I want to achieve is that other people in my organisation would be able to "copy & paste" it to their structures with the condition that the Jira ID will change to their Project's :

In my case, every issue has the ID of my project (TPMDATA-XXX) and I'd need they change it to something like DATAPLATFORM-XXX or BI-XXX.

Is this possible? because if I can't achieve it, means that everyone needs to create their issues manually following the structure I've created ;) 

Does it make sense?

Thank you!