nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Jira Project comments syncing

stephen.abiero

I have two projects on the same instance but closed(users who have access to A doesn't have access to and i would like to sync comments such that when a user comments on A it is visible on B and vice versa. however the closing of the issue can only be done from project B(Project B users are the ones who can validate if an issue is closed and when they do it should also close on A. project A users can close ticket on their end but should not close on .

i will really appreciate help on this

Comments

Syed Majid Hassan -Exalate-

Hi,

This is Majid @ Exalate.

It seems like you will need a synchronization app like Exalate in order to get this done. You can then control every aspect of how these two projects integrate, and will not need to change anything on the projects level itself.

Hope it helps.

Thanks

Majid

Thibaut Subra _Elements_

Hi @stephen.abiero

Indeed, syncing comments can be tricky so we tried to make it easier by developing Copy & Sync. The idea is that you can copy and synchronize issues between different projects, with fields, attachments, status, and of course, comments.

With Copy & Sync, you can choose exactly how the synchronization will work and what will be synchronized, by taking into account restrictions and rights.

Our app is free under 10 users and we have a 30-Day trial policy so feel free to give it a try!

Regards

Thibaut

Katarzyna Szumilas_Deviniti_

Hi @stephen.abiero

If you consider using a third-party (but still free of charge) app Issue Sync Pro can effectively address your use case by providing bidirectional synchronization of comments and issue statuses between two separate Jira projects within the same or on multiple Jira instances.

Here's how the app developed by my team can solve your specific requirements:

Comments Synchronization: When a user adds a comment to an issue in Project A, Issue Sync Pro can automatically replicate that comment and add it to the corresponding issue in Project B. Similarly, if a comment is added to an issue in Project B, it will be mirrored in the corresponding issue in Project A. This ensures that users in both projects stay informed about the ongoing discussions and updates.

Selective Issue Closure: Issue Sync Pro can be configured to allow selective issue closure. In your case, Project A users can close tickets on their end without affecting Project B. This means that when a user in Project A marks an issue as closed, it will remain open in Project B unless explicitly marked as closed by a user in Project B. However, when an issue is closed in Project B, it will also be marked as closed in Project A, ensuring that both projects remain synchronized.

If that sounds interesting, feel free to test the app or book a demo via our Calendly.

Best regards,
Kasia from Deviniti

Matthias Gaiser _K15t_

Hey @stephen.abiero

you're describing a classic scenario for issue sync apps. To get a list of all the various apps which can solve this use case head over to the Atlassian marketplace.

I'm part of the Backbone Issue Sync team.

Our configuration sounds similar to what Kasia mentioned:

You can turn on bidirectional comments synchronization. I'd recommend to use our enriched mapping so that you still know which user commented although they don't have permissions to the project.
For closing the tickets, you can model in Backbone which status changes should reflect on the other side. So in your case, you can configure it so that when the status switches to Closed in B, it will also switch to Closed in A.
To avoid invalid data states, I'd also recommend to modify the workflow you use in Project A, so that usual users can't close issues, only the project role "atlassian-addons-project-access" which allows apps to still perform this transition.

Let us know if you still want to discuss some requirements.

Hope that helps,
Matthias.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud