Moving Tickets between two Subscriptions

[Nikayla Palomino]

Hi Everyone, 

Quick question: I would like to find out if there's a possibility if you can move a ticket from one project to another project (you client's jira board). So in other words it's not the same subscription, two different Organizations .

They would like to send work to us from their projects and I would like to know if this is possible?

Confusing question :/ I know...

[Scott Theus]

Hi @Nikayla Palomino,

There isa an add-on that will do this nicely. It is called "Backbone Sync." I've used it in the past, here is a post I wrote last spring about how I set it up.

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

Hope this helps,

-Scott

[Deleted user]

Thanks @Scott Theus for recommending Backbone Issue Sync!

Hey @Nikayla Palomino ,

I'm one of the developers behind Backbone. You can use our add-on to synchronize issues between Jira Server to Jira Server, Jira Server to Jira Cloud and Jira Cloud to Jira Cloud. In the end it means every organization (e.g. you and your partner organization) has their own issues in their system and Backbone takes care that the state of them stays in sync. Therefore you can sync fields (like summary, description, assignee, reporter and many more) as well as other things like comments and attachments. Let me know if I can help you or read more in our documentation here: https://help.k15t.com/backbone-issue-sync

[francis]

Hello all,

I'm part of the Exalate team, which is an issue synchronisation solution allowing to sync boards and all entities on that board, including epics, stories in the epics, sprints, versions, ranking ...

Here is a video showing how exalate can be used for this use c

https://youtu.be/U7dzYzwyL30

Check out more details here
https://docs.idalko.com/exalate/display/ED/Agile+project+sync

Francis

[Nic Brough -Adaptavist-]

If the boards are in the same system, then yes (although you don't "move between boards", you change the issue so that the current board no longer selects it, and the other board starts to.  Often this is just by moving the issue from one project to another using "move")

If they're in different systems, then no, they're separate.

My guess is when you say "subscription", you do mean "system".  Basically, for each "subscription", check the url - if the base url is different, they they are different systems (e.g. aaa.atlassian.net/... and bbb.atlassian.net/... are different systems)