How to sync (story, task and sub-task) between two different confluence?

[Ammar]

we have an confluence for the team, and another one for the costumer.
the project manager decided if we have a story ,task or sub-task from the costumer confluence side, we should have the same information for the team confluence.
I don't have the experience to solve this problem because I am new in Atlassian community.
Thank you in advance.

[Deleted user · Accepted solution]

Hi @Ammar,

synchronizing stories, tasks and sub-tasks between two different Confluence instances is not possible. But I assume you want to synchronize these things between two different Jira instances, right?

You have two options:

a) use a single Jira / Confluence instance for you and your partner, i.e. give them direct access to your systems. I guess this might not be a valid option for you, because you probably want to separate the two instances for reasons like security. I can understand that :-) Hence think about the second option...

b) use two Jira instances (e.g. Jira A and Jira B) and connect them to your Confluence systems (e.g. using an app link, Confluence A is connected with Jira A and Confluence B is connected with Jira B). Then you can use an issue synchronization add-on from the Atlassian marketplace to have the same issue data in both Jira instances. (You don't have to synchronize the whole instance, but you can select which data you want to synchronize) The good thing is now that you have two separated Jira instances and only exchange the data which is really necessary for your customer. However, please keep in mind that you can not synchronize any Confluence data with these add-ons, they only work for Jira. Disclaimer: I'm working for the team behind Backbone Issue Sync, one of the suggested sync solutions. Just let me know if you have any questions.

[Vasiliy Zverev]

@Ammar, hi!

If stories, tasks and sub-tasks are stored into Jira, you could sync each confluence with Jira.

Also you could have a look to have single Confluence instance for all and use different spaces for team and costomer.

[Ammar]

Thank you @Vasiliy Zverev

[francis]

Hi @Ammar,

Stories, tasks and sub-tasks are Jira entities.  
(We're the developer of the Exalate Jira Issue Sync app)

What you're describing is a pretty common use case for our app.

You'll be able to synchronise any issue data of one of your instances over to the other instance.

This will happen in real-time. That way, you'll always be in the loop on progress status, comments, attachments (and even work-logs or change history)!

You'll be able to easily customise exactly what you'd like to sync and who you'd like to sync it with.

Like the following example:

If you want, I can show you exactly how it would work for your use case through a one-on-one demo. You can book one here: Book A Demo.

Does this answer your question?

Francis