Copy Project including KanBan board and issues/tasks

[Christodoulos Mouskos]

What is the correct way with Jira tools to find a solution for our problem?

Description of our problem: we have a template project with 20 steps/tasks. Then for each client that we sign we need to duplicate the template project and follow these 20 steps to complete his onboarding on our system and finish the project.

If we sign a new client we will again clone the template project and do the same.

We tried to do this in Jira software by creating a template project, with a kanban board with 20 tasks. These 20 tasks are the steps that someone should follow to complete the  project.

Then we did not find a way to clone the project along with the kanban and the 20 issues/tasks 

Did we get wrong the use of projects and kanban?

 Thank you in advance

[Christodoulos Mouskos]

Is there a way to give us more details about the Epic way you mentioned above?

Any specific sections in the documentation to look for? 

Thank you

[Christodoulos Mouskos]

Further to your 1st suggested method above, I tried to do the below:

I created a general project with a kan ban board

In this project I created an EPIC with 3 sub-tasks (assuming that corresponds to client 1). 

Then, I  cloned that EPIC and I ticked the box to clone also its sub-tasks. (assuming that the cloned corresponds to client 2)

Now, in the kan ban I see the 2 EPICS with 3 sub-tasks each, which means there is the whole picture there.

Now, I want to be able to do filter search in Kan-ban to view only the EPIC and sub-tasks related with client 1. And I want to be able to do this easily, without the need for pre-defined Quick filters. Otherwise, it means that each time i will have a new EPIC for a new client i will need to add a Quick filter. And clients might be 200-300 or more which is not a number that is manageable with pre-defined Quick filters. Something like dynamic filtering search will be the solution. Or something else that you could suggest please.

Thank you

[Deleted user]

Well, I don't pretend to be bad behaviour but what you re asking for is a bit inapropriate, you are asking me to make a design of a process I know nothing about and be lucky to accomplish what you need without breaking other things that you need.

I can point tips and use cases of other atlassian customers, even use my imagination, but I won't be able to reach all of your needs that easily. I would day, use epics as projects, standard issue types as Child of epics (not subtasks!!!!) and allow users to create subtasks (commonly used as child of standard issue types,, not época).

With add-ons you could even customize your needs and permissions as creation, automations in workflows, etc

About boards, also with for example scriptrunner add-on hoy can use more dynamic quick filters, or look for documentation of JQL out of the box functions and see if they adapt to your needs.

You can find this documentation quite easily on the web (I'm at the Atlas Camp in Barcelona at the moment and is a little harder to do It! ^^)

[Deleted user]

You habe more than one way of action. You can use a normal issue type for a project and 20 subtasks. It can be automated, they will all appear in your board and backlog and then use quick filters or swimlanes.

If you want to hide them by user groups/roles usé the security issue scheme.

You can also use epics and 20 standard issue types as the template and allow your users create any subtask they need to complete the tasks (we use exatly this in our company)

I would reccomend a little formation about the tool first (atlassian academy or learning the old way). You can find anything you need in the atlassian documentation

[Christodoulos Mouskos]

Noted, thank you for your answer.

So, is there a way to solve the kind of problem that we have (please see "Description of our problem" in above post) using any Jira tool?

Thank you

[Deleted user]

Are you creating a project for only 20 issues? Is that really the best way to use your instance? Of course, it all depends on your needs, but I would never create a project for only 20 issues.

Remember that a project is just a set of schemes, this is a tool which names things that must not be the same in real world, as an issue is a ticket and a project is a mix of schemes