Combining tickets from other projects/other sprints in one sprint

[Bastiaan Rademakers]

Hi, 

I got a nice challenge, if possible at all.

Project A is a customer project, with it's own tickets and it's own sprint pace, defined by the customer and internal team.

Project B is an internal project, again with it's own tickets and it's own sprint pace, defined by myself and my (internal) team.

The resources in project B are also needed in project A, so I need some way to combine these 2 projects, without loosing the overview.

We've created a board with tickets from both projects, but the problem is that the sprint pace is different from both projects.

Is it possible to combine the tickets from both projects into a new sprint, while leaving the existing sprints intact too? I can't figure out a way, but maybe I'm overlooking something...

[Scott Theus · Accepted solution]

Hi Bastiaan,

Here is some information that may help:

https://community.atlassian.com/t5/Jira-questions/How-do-I-combine-issues-from-multiple-projects-into-a-single/qaq-p/89053

-Scott

[Bastiaan Rademakers]

Thanks for your reply Scott.

The problem I'm facing here however is that the issues from all projects are already in a sprint (in the project itself), but I would like to combine those same issues in an overall sprint as well. Basically it should be a sprint, containing tickets that are already in another sprint in another project.

The thread you've mentioned isn't a solution for that problem unfortunately, if it can be resolved at all.

[Scott Theus]

Interesting...perhaps a bi-directional sync between the two projects that, essentially, copy the issues from Project A into Project B and maintains the status in both? It's more complicated than a dashboard, but here is an add-on called Backbone that will do that for you. Since the issues exist separately in both projects you can maintain separate sprints.

More info:

https://community.atlassian.com/t5/Marketplace-Apps-questions/Jira-Backbone-issue-quot-backsync-quot/qaq-p/742781

-Scott

[Deleted user]

@Bastiaan Rademakers,

As Scott mentions, this does sound like a use case where an issue synchronization solution such as Backbone Issue Sync could come in handy.

In your situation, you could use Backbone to synchronize the issues in the sprint between the two Jira projects. This would mean that the issues would exist separately in each project, but they would both always be up-to-date, because any changes made to an issue in one project would automatically be synchronized to the other project.

Because you'd be dealing with two separate issues, this means that you can work with the issues in sprints in both projects with full flexibility.

If you have any further questions about Backbone, just send an email to the K15t Software support team and we'll be happy to help.

Cheers, Tom.

[Bastiaan Rademakers]

Thanks for your reply, guys. Backbone sounds really useful for my problem, so I'll dive into that. 

[Scott Theus]

Bastiaan, could you accept the answer so the question is flagged as "Answered" and it is easier for others to find it?

Thanks,

Scott

[Bastiaan Rademakers]

Yes of course, sorry for forgetting that ;). I'm testdriving Backbone and it works nicely out of the box. I do have some challenges though, but I'm sure I can overcome them...