JIRA iBridge - Create Issue operation

[Martyn Houghton]

I am at long last got some more time to try sort out integration with on on premise JIRA installation, which @TrevorKillick add the option for on premise as well as cloud based.

I ma having difficulty in getting the Create Issue operation, one in terms of having an example to follow, but more importantly where to look in order to debug the operation.

 

I have tried setting the Continue on Error to both Yes and No, but still get no feedback on the process either in the UI/timeline or in the log files.

I looked in the Server Log but do not seem to be able to locate the call or any error information.

Any ideas or pointers?

Cheers

Martyn

[TrevorKillick]

@Martyn Houghton

So I just had a look at your logs and the Operation is not being fired, in the logs should be a reference to iBridgeInvoke but nothing is showing so it looks like an issue with your Business Process flow. 

Any errors with this operation once triggered should be logged in the Server Service Log file. 

Kind Regards

Trevor Killick

[Martyn Houghton]

@TrevorKillick

Thanks for checking. I go back and double check the service setup. Least I know to look for iBridgeInvoke entry.

Cheers

Martyn

[Martyn Houghton]

@TrevorKillick

Something odd is happening. I have triple checked the Service configuration and the BPM. To be sure it is running my test BPM I have inserted a pre and post timeline update node around the integration node.

I can see them pre and post timeline updates but no error is given for the iBridge step.

Check log file and not reference to  iBridgeInvoke, it is like the node is just being skipped.

As we are problem the only ones who are trying to use the JIRA on premise option if there is something not quite right with the integration class?

Cheers

Martyn

 

[TrevorKillick]

@Martyn Houghton

I left some debugging in the integration so if you change the result reference of the integration node to jira:

Then in the subsequent update timeline node add the following to the update text: 

Jira HTTP Response: &[global["jira"]["httpResult"]]

Then let me know what gets posted to the timeline?

Kind Regards
Trevor Killick
 

[Martyn Houghton]

@TrevorKillick

I updated the workflow and also  the timeline post node before as a check the revised BPM is being used, but the same result no iBridge entry. I even double check that timeline filter is set to All.

Cheers

Martyn

 

[HHH]

Just check that noone has disabled the Jira user in Jira, something that happened to us when I set up our Jira integration.

A bit frustrating to say the least

 

[Martyn Houghton]

@HHH

Thanks for the pointer. I have checked and I can log in manually to our staging environment with the same credentials, so still a bit confused why it does not even seem to invoke or even error.

Cheers

Martyn 

[Martyn Houghton]

@TrevorKillick

Any further thoughts on this? The iBridgeInvoke is still not being triggered in the Server Log file.

Cheers

Martyn

[TrevorKillick]

@Martyn Houghton

Sorry for the late reply, I did some debugging and found the invocation of these operations are not actually logged in the server log which is really unhelpful. I have posted internally to see if there is any further debugging that can be added to aid in these situations.

I will update with any developments. 

Kind Regards

Trevor Killick

[Martyn Houghton]

@TrevorKillick

Thanks for the update. I see if I can get our JIRA administrator to see if there is any logs on there side as well.

Cheers

Martyn

[Martyn Houghton]

@TrevorKillick

Going back to basics, can I check whether the end point should be the base URL for the JIRA instance or include a sub url to the api etc?

Cheers

Martyn

[TrevorKillick]

@Martyn Houghton

This is an excerpt of code from the create issue operation. 

http.setOptions( { "basicAuthUser": credentials.username, "basicAuthPassword": credentials.password , "authType": "basic" } );
// HTTP Post to JIRA
var httpResult = http.post(credentials.endpoint +"/rest/api/latest/issue/",data,{"Content-Type":"application/json"});

The endpoint should be the full path to the Jira Instance, we add on /rest/api assuming that's correct. 

Kind Regards

Trevor Killick

[Martyn Houghton]

@TrevorKillick

The endpoint appear to be correct then, as we get a response.

Cheers

Martyn

[Martyn Houghton]

@TrevorKillick

We are using https, but I would presume the JIRA Cloud class this is based on also uses https as well, i.e. our url entered into the keysafe includes the https:// prefix.

Cheers

Martyn

[TrevorKillick]

@Martyn Houghton

The Integration will connect on whichever transport prefix is set it can be HTTP or HTTPS. Out of interest as its HTTPS does it have a valid SSL cert or is it self-signed, I ask as there is an option to disable SSL checks for self-signed certs which may be applicable in this case.

Kind Regards

Trevor Killick

[Martyn Houghton]

@TrevorKillick

I have PM'ed our endpoint. It is using a full valid SSL certificate, not a self signed one.

Cheers

Martyn

[Martyn Houghton]

@TrevorKillick

The is the current set of values I am using to try create a case in JIRA.

Cheers

Martyn

[Martyn Houghton]

Just an update on this issue, with the help of @TrevorKillick development/test harness we where able to track down the issue to being the project value being presented.

Unlike the other values that require the numeric ID value the project value need to be the textual project prefix key.

Hopefully this will help others who come to implement this latter.

Cheers

Martyn