Working with 2/3 Jira Server

[Peter Jehle]

Hello

Our customer has a Jira server and we schould work on a subproject. Our plan is to extract only relevant tickets from this server and work on them on our server.

The customer don't have assesss to our server.

Only part of the ticktes should be merged back to the customer. The idea is that the Descrption/comment starts with an @xyz_customer tag.

Is there a possibility to solve this available?

Also we need to peplicate our Jira server to another Jira server,

[Mikael Sandberg]

You may want to take a look at Backbone Issue Sync, it should be able to sync specific issues between the servers.

[Matthias Gaiser _K15t_]

As @Mikael Sandberg suggested, you can do this with Backbone Issue Sync. You can use our UI to select which fields you want to expose to your customer.

If you want to share only some comments with your customer, I'd recommend that you use comment restrictions as described in this help article.

[francis]

<shameless plug>

An alternative is Exalate - issue sync for JIRA and Cloud.

Exalate provides flexibility through groovy scripts allowing for fine grained implementations of almost any business case.

To ensure that only comments containing the @xyz_customer mentions are synchronized towards the other side, you would specify in your data filter

replica.comments = issue.comments.findall { comment -> comment.body.contains("@xyz") }

Give it a try, and let us know how we can help.

Francis

</shameless plug>