Java Rest API : BMC Remedy API and JIRA Integration

Question

I'm integrating BMC remedy and JIRA to solve a problem.

Task: I run a rest service and it raises automatic JIRA after reading BMC remedy if there are any records which are of type hotfix. So basically few fields from BMC will be mapped to JIRA when JIRA are created.

Problem : Because Remedy API accepts only one search criteria (which is "hotFix" in my case), Every time my service runs it reads remedy and fetches all the data which are of type "hotFix" even the ones I've already created JIRAs for which is expected. But now i need to resolve this because I don't want to raise duplicate JIRAs for them.

I don't want store all these things in database due to some reason. (Well infra cost).

Is there any way I can import this data without creating duplicates?

Have you tried filtering by date created and using the last time you synchronized as criteria? I don't see an easy way to do this short of comparing directly with JIRA to see if the issue is already there. — zero298, Jun 05 '18 at 18:49
@zero298 thanks for the reply actually I can filter based on only one qualification parameter which is "hotFix" in my case. As the BMC emedy do not accept more than one qualification parameter. — Saurabh Sharma, Jun 06 '18 at 09:55

score 0 · Answer 1 · answered Jun 05 '18 at 18:39

0

in your service before creating a JIRA ticket(I assume its an api call), check if already one exists (by using GET api from JIRA).

Based on your constraints for querying bmc remedy, seems this extra call to JIRA, to check if its a duplicate is an option.

answered Jun 05 '18 at 18:39

Anil Bachola

289
2
5

hey Anil, Yes I've thought about it however was little reluctant to make an other search on JIRA before insert as it might impact service performance. – Saurabh Sharma Jun 06 '18 at 09:59
1

Looking at your constraints, thats the only option you have, its a tradeoff that u need accept – Anil Bachola Jun 06 '18 at 16:58
1

Also looking at this JIRA community currently there is no way to stop creating duplicate issues. https://community.atlassian.com/t5/Jira-questions/I-would-like-to-know-if-it-s-possible-to-check-for-duplicate/qaq-p/156723 – Anil Bachola Jun 06 '18 at 17:15

score 0 · Accepted Answer · edited Jun 07 '18 at 13:36

Okay! I'm using a flat file.

As an alternative solution I've used a flat file to store the "date created" of last remedy incident with "HotFix" label (only one record !!! this gets updated every time my service gets a hit if there are new remedy incidents) and while fetching the data from remedy I'm ordering it based on date created and storing the most updated date (which would effectively serve me as a parameter for comparison when i hit my service next time to check if JIRAs till this particular date/time has already been created.) in this file.

This has resolved my issue.

Java Rest API : BMC Remedy API and JIRA Integration

2 Answers2