I want to integrate 2 JIRA instances through email, one uses Jira 4.2.1 and the other uses 4.3.3.
Please provide your thoughts.
Hi,
this was discussed here: https://answers.atlassian.com/questions/37711/how-to-connect-two-jira-instances-for-sync-issues-between-them
and here: https://answers.atlassian.com/questions/27168/how-to-synchronize-two-jira-instances
Maybe you find a solution there
Best regards
Thomas
integrate what through email?
one instance has certain custom fields, another has certain custom fields, both of the JIRA instances has to interchange the issue details, updates of the issue, through email. i.e both has to be in sync.
For Example
1) if an issue is created in Instance 1, a mail will be triggered and using that email, Instance 2 will create an issue there.
2) Also, if there is a update for an issue in Insance1 then a mail will be triggered to Instance 2 which will update the same issue in Instance 2.
Hope it clears !!
Thanks for the context.
You don’t have to rely on emails to do that they rely on notifications , you can use listeners in JIRA
https://developer.atlassian.com/display/JIRADEV/Plugin+Tutorial+-+Writing+JIRA+event+listeners+with+the+atlassian-event+library
within your listeners you can use any method/mechanism you prefer to keep what you want to keep in sync
i want all the issues created in one instance of (JIRA-1) to be in sync with the JIRA-2.
Also, how to process the incoming mails to JIRA-2, that triggers from JIRA-1 when an issue is created/updated in JIRA-1?
I want to do the same in vice versa also, i.e, process the incoming mails to JIRA-1, that triggers from JIRA-2 when an issue is created/updated in JIRA-1?
How to map the custom fields?
Is it possible using the listeners.
Above, people are advicing to use JEMH & CLI !!
It depends on what you want to do, how complex it is, and whether you've got the resources to write the listeners.
You can do this "integration" without any code really, by setting up a simple loop where one Jira uses the standard notifications to include the send of mail to the other Jira, which is then configured to use the standard create-or-comment handlers to update its own side. This is very basic, but does work. All it can do is comment though, there's no way to amend fields, progress issues etc. To build on it, you need something more complex. JEMH is an excellent extension for email that does allow you to do significantly more clever updates. It might be able to do what you need. If it doesn't, then you need to write listeners that will cope with the incoming data and do more updates based on that. If you're using listeners (or the CLI), then you aren't limited to using email as the data exchange transport, you can look at other methods.
Nic Thanks a lot for the suggestion.
I am very much new to JEMH.
Regarding Custom Fields:::
My custom fields are different in each of the JIRA instances.
i.e. in instance1 if i have a field called type_id it has to be mapped with problem_id in the instance 2.
Similiary i have lot of fields to map.
Regarding emails::::::
The body of the mail received from the JIRA-2 instance to JIRA-1 is in XML format.
So, the JIRA-1 instance has to process the email send by JIRA-2, and send back the response as email.
For the above 2 scenarios, will JEMH will be helpful for me?
If not, give your thoughts.
To sumup everything in a single line, all i am going to do is create a middleman who talks with 2 JIRA instances and does the following
1) process the data whatever the two JIRA instances sends.
2) to keep both the instances in SYNC (updated).
It looks like you're new here. Sign in or register to get started.
