Requirement is to pull data from Remedy also require the integration between Remedy & JIRA.

 

1 answer

0 votes

Ok, you're going to need to find or write a connector to get the systems to talk to each other.

There are a couple in the marketplace on the JIRA side, I'd suggest you start there.

For your "integration" - this is a brilliant example of a "suitcase word" - it carries a lot of implied meaning, but tells us absolutely nothing of any practical use.  You're going to need to define what you want from an "integration".

Here integration means, suppose if i am doing any updation in the incident in JIRA then it should reflects in Remedy.For example if i am changing the status of the incident, then it should reflect in Remedy as well. Or say if i am adding any comments in JIRA, then it should reflect in Remedy as well. And it should be both way communication.Is it possible ?

Possible, yes, easy - not necessarily.

If you can't find a pre-written connector that suits you, then you'll need to code stuff for yourself (or engage a partner or expert to do it for you).  Have a look in the marketplace, there are a couple in there, although the ones I'm thinking of are generic - not "Remedy/JIRA" but more "Generic system/JIRA".

Most places I've worked with tend to be moving off Remedy though, rather than "integrating", so I'm not completely up to date with what's in the marketplace.

Nic, Unfortunately it is sometimes required to live in both Remedy and Jira, at least for long enough to convince certain portions of the company that the millions they spent on Remedy were wasted. smile

My company ended up building a 2 way integration between Remedy and JIRA from scratch. Deep knowledge of both tools is required because they have fundamentally different ways of working.

One of the bigger development challenges is that Remedy's assignment and workflow models are significantly different from Jira's. For example: In JIRA you can reassign an issue to a different person pretty much at any time. In Remedy, if you change an issue assignment, the status always moves back to "Assigned". This is one example of case where a change entered on JIRA and propagated to Remedy causes other state changes which must then be reflected back in JIRA. Without strong understanding of the two models and careful design, endless change loops are all too possible

Another significant challenge in any 2-way interface is designing for resilience and re-sync after either system is down, whether from a planned or unplanned outage.

A one-way integration is relatively straightforward. A Bi-directional is a challenge, but possible, 

Yeah, I know, I've worked with Remedy a few times, and I know very well that it's a legacy system that will take time to move off on to sensible systems.

You do need a full understanding of both ends of an "integration" of course, and that's why I recommend going for add-ons first - someone else has hopefully done some of that for you!

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Monday in Jira Ops

Jira Ops Early Access Program Update #1: Announcing our next feature and a new integration

Thanks for signing up for Jira Ops! I’m Matt Ryall, leader for the Jira Ops product team at Atlassian. Since this is a brand new product, we’ll be delivering improvements quickly and sharing updates...

500 views 0 9
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you