Separate Kanban Board Timelines

Question

I have a Board on my KANBAN and I created a Timeline for it.

Is there a way to copy that exact board and put it under the same Project and it have a different Timeline? Everytime I edit the epics and stories on the other board it's changing things on the other board. I tried creating a copy of the filter its pulling from but still same issue.

The vision is the timeline I created for one of my releases be copied and dates adjusted to use for my 2nd release instead of having to make new ones all the time and creating new projects!

Thank you!

Trudy P Claspill · Answer

FYI - Another step after cloning each child issue would be changing the newly created child issue from the original Epic to the new Epic.

To display the issues in another board you would have to create a new filter to select those specific issues. You have to figure out the right JQL for that. For example:

issue in (comma separated list of new Epic issue keys) or
issue in (comma separated list of new child issue keys)

Another example:

issue in (comma separated list of new Epic issue keys) or
parent=NewEpic1IssueKey or parent=NewEpic2IssueKey or parent=NewEpic3IssueKey or parent=NewEpic4IssueKey

...with the "parent=..." chain being one of those for each new Epic you created by cloning in order to get the child issues associated with that new Epic.

Then you would set the Kanban board to use that filter.

You could either copy the original Kanban board and change the new board to the new filter.

Or you could create a new Kanban board using the newly created filter as the source.

Elena Papa · Answer

I am okay with creating individual clones of each epic and story but How do I display them on my new board? I am assuming Only the clones will go on the other board so i can modify the dates but How can I pull only the clones in a filter? Unless I am mistaken there is no way to do that.

Trudy P Claspill · Answer

In that case you need to make copies/clones of the Epics and Stories.

There are native options to do that, but they take some work. There is a native Clone operation. If you use it on an issue with Sub-tasks it gives you the option to clone the issue and its sub-tasks. However, when used on an Epic it does not give you the option to clone the Epic plus all its child issues (and their subtasks).

There are third party apps that provide the functionality to do that. Are you open to using third party apps?

If not there are more complex solutions that can be developed using Automation Rules

It may also be possible using a CSV file as a template to create all the Epics and child issues. Note that the process of importing CSV files has changed recently and I have not actually used it. I know the old process would work for importing data to create Epics and their related child issues, but I have not confirmed that can still be done with the new method.