Matthias Gaiser _K15t_ Community Champion

As an alternative of Exalate, you can also have a look at the other issue sync solutions in the marketplace which all solve the use case of combining different Jira instances with each other.

Hi John, you could also use an issue sync solution for that. You would configure integrations between all the projects where you want to share the copies of your issue and the solution will take care that all the issues stay in sync. You can furthermore control which fields you want to keep in sync and more config options…

Dave's arguments are valid and you have to decide for yourself which way you want to go - a big centralized instance or smaller distributed instances. In case you go for different instances and have the need to still share some issues between instances, I'd like to contradict Dave and say that there are some issue sync…

You could use an issue sync solution for it. You configure the solution to your needs so that all (or only some) tickets from the service desk get synchronized to the Jira Software project. This blog entry or help article describes such a scenario. Being a member of the Backbone Issue Sync team, I'm also happy to offer you…

It would be great if you can explain your use case in a bit more detail, then the community may come up with more suggestions than you thought of. Some questions to get you started: * Why do you want to export/import or copy Jira issues? * Are you doing it for archiving reasons? * Is it a one time copy? * Is it inside one…

Hi Mirco, as Nic mentioned, I'd also suggest that you setup a synchronisation between the Jira in your DMZ and the Jira in your internal work. Then you can synchronize the issues, based on certain conditions & configurations. I think, this matches the second level support use case described in this documentation. If you're…

Of course a web session and test is possible. We'll contact you via email. If anyone else reads this and is interested, let us know via support@k15t.com.

Of course. Let me explain it in some steps: * Install Backbone in your cloud instance. * Setup a Jira server instance (10 user is enough) and install Backbone in it. * Get a remote trial license from support@k15t.com and install it in the Jira server. * Create a dummy project in the Jira server with the same project key as…

Hi Jay, I am part of the product team of Backbone Issue Sync for Jira. My colleague just replied to you on a support ticket, but since you asked the question here, we also want to share the (possible) solution. In the usual setup of an integration between two cloud instances, Backbone also requires the installation on both…

Of course, Brett. You can link multiple projects from the Jiras to each other - in Backbone we call this link an integration between two projects. You could define the following integrations: * project A, Jira 1 <> project B, Jira 2 * project A, Jira 1 <> project C, Jira 2 * project D, Jira 1 <> project E, Jira 2 * ... If…

Hi Brett, to answer your questions 1 & 2: In order to link tickets between instances, you should have an application link setup between your instances. If you want the users from Jira 1 also comment on the tickets (internally) in Jira 2, the users need also a license there - but not a Jira Service Desk license, a basic…

I imagine by pulling the full history, you want to have the same history on the target issue as in the source issue, right? What Backbone does, it applies all changes on the target issue. As soon as the source issue is changed, the target issue will be changed and therefore a similar history in the target issue will be…

I'd also recommend you (as Jobin) to look into issue synchronization instead of federated Jira instances. In federated instances, you'd usually have the same user base which is probably different in your use case. Here's also a possible search for various issue syncing apps in the Atlassian marketplace. Since I'm working…

btw: unfortunately these endpoints are not available with other authentication methods than basic HTTP authentication. Please vote or comment here if you want to get these APIs officially.

Hi Michael, what is it that your users are really requesting? "Federating Jira" seems on a very high level. Some questions to get you thinking: * Do users want to access issues from other instances? Across all projects? Only of specific projects? * Do they want to link to issues of other projects? (Yes, according to your…

Francis mentioned a good point - are you talking about a single or multiple instances here? I'd assume a single one. If you actually want to move the issue (so that it does not exist in the old project anymore), I'd also recommend the standard move issue functionality. If you want to synchronize between projects (even…

Just as a little guidance for the community here. If you think an answer fits your question and is good for you, please accept the answer so that other users will also quickly find the one which helped you.

The Jira documentation lists you some ways how you can link existing issues to epics. On a Scrum board, I personally drag most of the times simply the issues onto an epic in order to assign them.

From the trello help: Once you've changed the board background, all other users that view that board will also see that same background. So, yes it is for the entire team.

And if you wonder what your external receiver is: This is some REST endpoint you would have to create yourself which does your POST into SFDC. I'd recommend using sth like AWS Lambda for this. There you don't have to maintain a server, you simply can enter your code and make it accessible via a REST endpoint (API Gateway).

Hi Hari, usually, you don't have to provide authentication headers when you use the AP.request method, see also the docs for this. It might be the problem that you didn't specify the corresponding scope, you'd need the WRITE scope for this one, see also the docs here. Cheers, Matthias

If you want to go a step further than simply create an issue on a certain condition, but also keep it synchronized with the original request afterwards, you could also choose an issue synchronization app from the marketplace. Since I'm working for K15t, I'd obviously recommend Backbone Issue Sync, but that's a choice you…

Hi Andreas, I don't know if you're still searching for solutions, but maybe other people do. I would think about having two different Jira/Confluence instances, one internal and one in the DMZ and copy to the DMZ only the information which you really like to expose. This way you can guarantee that no internal information…

As Nic mentioned, you can also use Backbone Issue Sync in order to do that. The structure is the same as Francis suggested. You don't have to replicate all the information to Jira A, you can limit it to the information which you actually need there. In order to start this off, you should create the duplicate projects…

Hi Caio, having only Jira Software & Service Desk in place, this is not possible. But you can accomplish this with one of the issue sync apps in the marketplace. You can configure these so that all issues from your help desk are automatically created in Jira Software and therefore appear in your board where you can work on…

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.

As far as I understand, the sprints belong to the board and not the project. The mentioned method will list the sprints of the current board. And these sprints can be used in multiple projects.

Hi Bob, yes, this is possible. You can accomplish this task with Backbone Issue Sync for JIRA. It allows you to configure which issue types, fields and workflows you want to map. There are also some other addons available which should do the job. Have a look here: https://marketplace.atlassian.com/search?query=issue+sync…

Hi Jessica, you can get the field names by adding an expand parameter to your search call. Assuming you use this endpoint, you can simply add "expand=names" to it. This gives you the list of names in the response as well. You can try e.g: https://k15t.jira.com/rest/api/2/search?maxResults=1&expand=names You still have to…

Not sure if this is still relevant for you, but you might want to try the Scroll PDF Exporter which supports more macros and has more styling options than the Confluence out of the box one. See also this entry which might be your use case.