Comments
-
HI @anusha t , This is Majid @ Exalate. This guide gives you a low down on how to go about doing this integration. If you are looking for alternatives, I would urge you to look at Exalate. It has a bit of everything for everyone from the zero-code Visual mode for non-coders, and the scripting engine for the ones who are…
-
Hi Aneesh, This is Majid @ Exalate. You have a few options when it comes to connecting these two, but depends on the exact use case that you are looking to address. Please have a look at Exalate that helps to sync issues and PRs from GitHub to any Jira flavour. Hope it helps! Thanks Majid
-
Hi Jessie, This is Majid @ Exalate. I think this is by design as you need to use the Notify action to achieve this - as you already know. However, this is something that works out of the box with integrations apps such as Exalate. Please give us a shout out if you are interested in exploring it further. Thanks Majid
-
Hi Andrea, This is Majid @ Exalate. This is very possible to do using Jira Automations within the same instance, but if you would like to get similar functionality across Jira instances (or within the same), you would need an issue synchronisation app such as Exalate. You can map statuses in a customised manner and can…
-
Hi Keith, This is Majid @ Exalate. To give a proper recommendation, I would need some more details about the use case such as what entities you are looking to integrate etc. But I think you should definitely have a look at Exalate to see if it fits your needs. Thanks Majid
-
Hi, This is Majid @ Exalate. You should be able to get the endpoint from this post. Also, if you are interested in taking the pain out of the development and maintenance of the custom solution that you are building, I would urge you to have a look at Exalate. Please let me know if you are interested in learning more and I…
-
Hi @Kamala Geetha Francis Fernando This is Majid @ Exalate. In order to sync data between two independent Jira instances, you will need to use a synchronization app such as Exalate. You can choose exactly what data to share and in what direction, and the integration should be fairly simple to setup as both sides are jira…
-
I do not really have a step by step for the API solution, as it would be a huge project in itself. I am not sure if you would even be able to Google such a guide, but here is a starting point mainly: https://developer.atlassian.com/cloud/jira/platform/rest/v3/intro/#version…
-
Hi, This is Majid @ Exalate. I believe this might be a known issue and support might be able to help you here. Jira and Zendesk integration has come a long way from basic field sync to a single Jira instance. Integration apps such as Exalate now allow you the ability to customize the integration to a very granular level…
-
Hi @Sarah Green This is Majid @ Exalate. I believe the most efficient way of doing this would be via an integration app like Exalate. The endless customization available there would also you to tune the integration exactly as you want. Thanks Majid
-
Hi @suren This is Majid @ Exalate. If you take plugins out of the equation, then that would basically leave you with a couple of options only: * Use the native connectors provided on the two platforms (depends on your subscription model) * Build an integration yourself based on REST APIs provided by both systems. It would…
-
Hi @Morten Dieckmann-Keden This is Majid @ Exalate. This is very possible, but it really depends on the target system that you are planning to interface it. Jira definitely provides all the requisite tools that are needed for the push or pull, and I believe most ITSM systems would also provide the same. You could very well…
-
Hi @AmandaB This is Majid @ Exalate. Is it a one time copy or a copy that needs to remain in sync? If this is the former, then I believe Jira automations would do the job sufficiently, but if you are interested in the latter or if you want to customize aspects of this copy operation, I would urge you to look at a…
-
Hi @Yatish Madhav This is Majid @ Exalate. You are literally spoilt for choice when it comes to options to connecting between Salesforce and Jira, but yes there are only a few free options available. With Exalate's Basic mode, you can use the integration for free forever if you want. It should be able to sync across…
-
Hi @brett anderson This is Majid @ Exalate. I am not sure what type of integration you are using and hence, cannot really comment on the additional webhook hunch. But you can do this and much more via our app Exalate. It should be pretty straight forward to configure and here is something to get you started. Thanks Majid
-
Hi @Sreenivasaraju P This is Majid @ Exalate. I have seen that you have posted the same question to our community site. Let us continue the conversation there as I will need several pieces of information in order to troubleshoot the issue. Attachments should work out of the box with Exalate, and as you say, they are…
-
It really depends on the config, and yes sure, I would be willing to take a quick look to see if I can help. Thanks Majid
-
Hi, This is Majid @ Exalate. The use case you have described should be very possible to do with an issue sync app like Exalate. You can customize the fields you want to copy over and just hit a button to trigger the Bulk Copy. Please let me know if you have any questions. Thanks Majid
-
Hi, This is Majid @ Exalate. As already explained by several folks here, you would need an app to achieve this. The choice of app would be governed by your particular requirements, but here at Exalate we believe that any integration solution must be fully secure, reliable and robust. You can achieve your Epic copy use case…
-
Hi, This is Majid @ Exalate. A few questions here please: * Is this a one time effort, or would you want updates on tickets to flow between the two projects? * Are the source and target projects on the same Jira or different? Thanks Majid
-
Hi, This is Majid @ Exalate. This can be achieved in two ways mainly i.e.: * Use Jira Automation to set this up and create rules accordingly. * Use a synchronization app (paid/free) t o map the fields accordingly. Exalate does offer a free version that could be sufficient to your needs (but I dont know the exact needs…
-
Hi Alex, This is Majid @ Exalate. There are many ways to achieve this (as discussed earlier). It depends on the effort you are willing to put in and how flexible a solution you want. A DIY approach here would be a valid way to do it, but expensive I think, or you could essentially "outsource" the problem to a…
-
Hi Scott, This is Majid @ Exalate. The way I would do this would be an automatic issue creation in Github for the technical debt, and then have that issue synced over to Jira for further processing. You can then choose to keep the two issues in sync (preferred) or let them go their own way. This should be achievable by…
-
Apparently, it is an error in the JQL statement, but where are you writing this statement or is it being auto-generated by some app? Can you provide some more details please, and maybe we can help. Thanks Majid
-
I believe there should be two efficient methods to achieve this: * Jira automation - a very viable solution and has been discussed at length above. * Issue sync solution - you can use an app like Exalate to achieve this either in 2 projects on the same Jira (your use case) or 2 projects in 2 different Jira instances. Hope…
-
Hi @Istvan Fay This is Majid @ Exalate. As has been pointed out, issue synchronization apps such as Exalate, specialize in performing this Jira to Jira collaboration between two independent instances. In our experience, the most important factors to consider in such cases are security, granular control over data and…
-
Hi @Tmz Welcome to the community. This is Majid @ Exalate. As Mathias already explained, the way to do it would be to use an synchronization solution such as Exalate to set up a cross-company collaboration between the two independent Jira instances so that only selective data and selective projects are in the picture. This…
-
Hi Bill, This is Majid @ Exalate. I think Option 1 that you mentioned is very feasible, but the step that you are missing here is Jira automations. If you couple the automations with the linked issues, you should be able to get a feasible solution here. If you would rather "outsource" the problem totally, an issue…
-
Hi, This is Majid @ Exalate. Are you simply looking to somehow replicate the live SNOW reports in Jira dashboards? If that is the only requirement, I believe something like EasyBI is the way to go. If you would rather replicate the actual SNOW dataset (incidents/change requests/ problems) within Jira, then you should be…
-
Hi @John Holloway Welcome to the community. This is Majid @ Exalate. It seems that the AccountID from Salesforce is being sent over to Jira i.e. it would be meaningless for Jira. There are several ways to do what you are looking for: * Create a mapping of Salesforce AccountIDs and Jira AccountIDs so that Jira "knows" who…