Martyn Houghton Posted November 8, 2021 Share Posted November 8, 2021 @Steve G Though iBridge logging was added to the ESPServer Log back in January 2019 (see linked post), I am struggling to get JIRA on premises working on our instance. I had asked Support for a copy of the iBridge logs as you had referenced these in a earlier post when we had issues to see if I could sort out what's going on. However I was told this is not possible as they are shared logs and I have to raise any questions on the forum. I suspect is something on our side but all I can find in the ESP Server Log is below, which does not appear to give any clue to the issue. It does not show the value we are passing or what the response is from the node/endpoint. ======== record data ======== 1: flowcode-cdfe35d9 2: 4 3: 2021-11-08 15:55:29 4: {"id":"BPM20211108000195","application":"com.hornbill.servicemanager","name":"jira-test","currentStage":"4a2e5015-4bf4-bc96-b090-1a35b65c323b","currentNode":"flowcode-cdfe35d9","suspended":true,"cancelled":false,"failureMessage":"","stages":{"4a2e5015-4bf4-bc96-b090-1a35b65c323b":{"number":0,"displayName":"Investigation","translatedDisplayName":[{"text":"Investigation","language":"en-GB","tooltip":""}],"status":"inProgress","items":{"4be938f6-40f3-3ba7-f102-473e8cc59c4c":{"displayName":"Investigation Started","translatedDisplayName":[{"text":"Investigation Started","language":"en-GB","tooltip":""}],"required":false,"state":true,"position":0},"871c9a1b-39e5-3afe-3b6d-d3e310c567eb":{"displayName":"Investigation Complete","translatedDisplayName":[{"text":"Investigation Complete","language":"en-GB","tooltip":""}],"required":false,"state":false,"position":1}}}},"TASKS":{"4a2e5015-4bf4-bc96-b090-1a35b65c323b":{"task-67b55159":{"type":"task","threshold":100,"tasks":[{"assignee":"martyn.houghton","weight":100,"grouping":"cf59570d-e9e3-4b91-8796-af25bc9debcc","request":{"result":{"@status":true,"params":{"taskId":"TSK20211108001468"}}},"response":{"result":{"@status":"ok","params":{"status":"complete","title":"JIRA Tasks","details":"Log new JIRA?","options":{"timeSpent":"true","enforceProgressForCompletion":"false","hideReason":"false","enforceTimeSpentForCompletion":"false"},"priority":"normal","appointment":"false","reference":"bpmTask","createdOn":"2021-11-08 15:55:01Z","createdBy":"SYS_BPM_MANAGER","timeSpent":"0","timeBillable":"false","progress":"100","assignedTo":"urn:sys:user:martyn.houghton","owner":"idoxsd","outcomes":"NewJIRA,LinkJIRA,UpdateTicket,NoJIRA","outcomeInfo":[{"outcome":"NewJIRA","displayName":{"text":"Log New JIRA","language":"en-GB"},"buttonColor":"success","requiresReason":"false","customFields":[{"id":"TicketTitle","label":{"text":"Ticket Title","language":"en-GB"},"isSummary":"false","isMandatory":"true","isVisible":"true","isReadOnly":"false","showIfEmpty":"false"},{"id":"TicketDesc","label":{"text":"Ticket Description","language":"en-GB"},"isSummary":"false","isMandatory":"true","isVisible":"true","isReadOnly":"false","showIfEmpty":"false"},{"id":"TicketProject","label":{"text":"Ticket Project","language":"en-GB"},"isSummary":"false","isMandatory":"true","isVisible":"true","isReadOnly":"false","showIfEmpty":"false","dropdownSelectDynamic":{"dataProvider":"JIRA_Project_Key","dataProviderAppName":"com.hornbill.servicemanager","dataProviderSortBy":"itemName","dataProviderSortDir":"ascending","isStoredQueryProvider":"false"}},{"id":"TicketType","label":{"text":"Ticket Type","language":"en-GB"},"isSummary":"false","isMandatory":"true","isVisible":"true","isReadOnly":"false","showIfEmpty":"false","dropdownSelectDynamic":{"dataProvider":"JIRA_TypeId_keys","dataProviderAppName":"com.hornbill.servicemanager","dataProviderSortBy":"itemName","dataProviderSortDir":"ascending","isStoredQueryProvider":"false"}},{"id":"TicketPriority","label":{"text":"Ticket Priority","language":"en-GB"},"isSummary":"false","isMandatory":"true","isVisible":"true","isReadOnly":"false","showIfEmpty":"false","dropdownSelectDynamic":{"dataProvider":"JIRA_PriorityId_Keys","dataProviderAppName":"com.hornbill.servicemanager","dataProviderSortBy":"itemName","dataProviderSortDir":"ascending","isStoredQueryProvider":"false"}}]},{"outcome":"LinkJIRA","displayName":{"text":"Link Existing JIRA","language":"en-gb"},"buttonColor":"info","requiresReason":"false","customFields":{"id":"ExistingJIRAKey","label":{"text":"Existing JIRA Key","language":"en-GB"},"isSummary":"false","isMandatory":"true","isVisible":"true","isReadOnly":"false","showIfEmpty":"false"}},{"outcome":"UpdateTicket","displayName":{"text":"Update JIRA","language":"en-gb"},"buttonColor":"primary","requiresReason":"false","customFields":[{"id":"UpdateJIRAKey","label":{"text":"JIRA Key to add comment to","language":"en-GB"},"placeholderText":{"text":"JIRA Key of existing issue, you wish [TRUNCATED] 5: BPM20211108000195 2021-11-08 15:55:29Z [INFO]:[SQL]:[464] UPDATE h_bpm_instance SET h_current_node = ?, h_current_state = ?, h_last_updated = ?, h_state = ? WHERE h_id = ? [5402 us] 2021-11-08 15:55:29Z [INFO]:[SQL]:[464] INSERT INTO h_bpm_timeplan_events (h_instance_id, h_stage, h_time, h_event_type, h_time_plan, h_time_plan_slc) VALUES ('BPM20211108000195', '4a2e5015-4bf4-bc96-b090-1a35b65c323b', '2021-11-08 15:55:29', 'processPause', NULL, NULL) [2578 us] 2021-11-08 15:55:29Z [INFO]:[SQL]:[464] INSERT INTO h_bpm_instance_log (h_bpm_instance_id, h_timestamp, h_timepoint, h_host_proc_id, h_host, h_caller_transaction_id,h_transaction_id, h_caller, h_log) VALUES ('BPM20211108000195', '2021-11-08 15:55:29', 731841510147, 4088, 'mdh-p01-node3', '', 'a7f6951f91104133bd3e04e04591967c', 'task/taskComplete', ' 0.000008s [INFO] Workflow processing started, processId=BPM20211108000195 workflow=com.hornbill.servicemanager/jira-test (revision=9, type=businessProcess) 0.008831s [INFO] Process Execute startNode=0 reason=erResumeTask 0.009033s [INFO] Called by: task/taskComplete (host=mdh-p01-node3) 0.009035s [INFO] Transaction ID: a7f6951f91104133bd3e04e04591967c 0.039316s [INFO] Process Wakeup/Check event ''Raise JIRA'' (id=task-67b55159, type=HumanTask) 0.044826s [INFO] Execution session is ''U20211108156360745.240165'', user is ''martyn.houghton'' 0.044828s [INFO] Execution reason is ''erResumeTask'' 0.044844s [DEBUG] Max exec loop count is set to 1000 0.044847s [INFO] Execution Step: currentStage=''4a2e5015-4bf4-bc96-b090-1a35b65c323b'', currentNode=''task-67b55159'', suspended=''true'' 0.048563s [INFO] Task completed (stage-id=4a2e5015-4bf4-bc96-b090-1a35b65c323b, node-id=task-67b55159), Outcome is ''NewJIRA'' 0.048589s [INFO] Process Flow Transition from ''Raise JIRA'' (id=task-67b55159, type=HumanTask) to ''Decision'' (id=decision-5749bc9c, type=Decision) 0.053981s [INFO] Unsuspending process at node ''Decision'' (id=decision-5749bc9c) 0.062348s [INFO] Execution Step: currentStage=''4a2e5015-4bf4-bc96-b090-1a35b65c323b'', currentNode=''decision-5749bc9c'', suspended=''false'' 0.064699s [INFO] Decision ''Decision'' (id=decision-5749bc9c), evaluating 3 branch expressions 0.064712s [DEBUG] Evaluating expression: ''outcome== "NewJIRA"'' 0.064714s [INFO] Expression matched: [outcome== "NewJIRA"], forwarding to target node: integrationMethodCall-cff1f979 0.064724s [INFO] Process Flow Transition from ''Decision'' (id=decision-5749bc9c, type=Decision) to ''Create Issue'' (id=integrationMethodCall-cff1f979, type=Integration) 0.195775s [INFO] Execution Step: currentStage=''4a2e5015-4bf4-bc96-b090-1a35b65c323b'', currentNode=''integrationMethodCall-cff1f979'', suspended=''false'' 0.302914s [INFO] Suspending process at node ''Create Issue'' (id=integrationMethodCall-cff1f979) 0.619862s [INFO] Process Wakeup/Check event ''Create Issue'' (id=integrationMethodCall-cff1f979, type=Integration) 0.627111s [INFO] Execution Step: currentStage=''4a2e5015-4bf4-bc96-b090-1a35b65c323b'', currentNode=''integrationMethodCall-cff1f979'', suspended=''true'' 1.142854s [INFO] Unsuspending process at node ''Create Issue'' (id=integrationMethodCall-cff1f979) 1.142866s [INFO] Process Flow Transition from ''Create Issue'' (id=integrationMethodCall-cff1f979, type=Integration) to ''Decision'' (id=decision-8217329f, type=Decision) 1.156734s [INFO] Execution Step: currentStage=''4a2e5015-4bf4-bc96-b090-1a35b65c323b'', currentNode=''decision-8217329f'', suspended=''false'' 1.157086s [INFO] Decision ''Decision'' (id=decision-8217329f), evaluating 2 branch expressions 1.157090s [DEBUG] Evaluating expression: ''(global["integration"]["key"]!=undefined && global["integration"]["key"]!=null && global["integration"]["key"]!='''')'' 1.157092s [DEBUG] Evaluating expression: ''true'' 1.157094s [INFO] Expression matched: [true], forwarding to target node: flowcode-4ced9a01 1.157109s [INFO] Process Flow Transition from ''Decision'' (id=decision-8217329f, type=Decision) to ''Log Request Failed.'' (id=flowcode-4ced9a01, type=HornbillAutomatiomn) 1.169340s [INFO] Execution Step: currentStage=''4a2e5015-4bf4-bc96-b090-1a35b65c323b'', currentNode=''flowcode-4ced9a01'', suspended=''false'' 1.169350s [INFO] Unsuspending process at node ''Log Request Failed.'' (id=flowcode-4ced9a01) 1.595746s [INFO] Unsuspending process at node ''Log Request Failed.'' (id=flowcode-4ced9a01) 1.595767s [INF[TRUNCATED] Can you advise how we should diagnose issues like this? Cheers Martyn Link to comment Share on other sites More sharing options...
Martyn Houghton Posted November 8, 2021 Author Share Posted November 8, 2021 As per my other post, I not sure it is even reaching our JIRA instance. Link to comment Share on other sites More sharing options...
Steve G Posted November 8, 2021 Share Posted November 8, 2021 Hi @Martyn Houghton, An error should be thrown when the integration node fails, which should give you a detailed description of what the failure was. Is this not happening, or have you got Continue On Error set to Yes (which would skip the error)? All new iBridge integrations now handle the trapping of failures much more gracefully, and have status and error output params as a minimum with relevant information output to help diagnose issue, but the Jira integrations were built before this process was implemented. We'll add those in when we get chance, I'll let you know once released. The endpoint URL should be in the format: https://your.jira.url I'll add that example to the wiki page. Cheers, Steve Link to comment Share on other sites More sharing options...
Martyn Houghton Posted November 8, 2021 Author Share Posted November 8, 2021 @Steve G I had Continue on Error set to Yes, as we check the Cloud Automation success parameter after the node so the workflow does not crash. Turning this off, I can now see the error, which is down to the reporter field no being on the Create Issue page. Would it be possible to have the error code passed back as a response parameter so that we can insert it into the timeline of the request to make it easier to debug? Cheers Martyn Link to comment Share on other sites More sharing options...
Martyn Houghton Posted November 8, 2021 Author Share Posted November 8, 2021 @Steve G We are now trying to update the reporter after creating but getting the error about the field no being on the page. I know when you create an issue the form only has specific fields on it, but for updating I would have thought you would be able to update any field subject to the users permissions? Cheers Martyn iBridge Method: /Atlassian/Jira/Update Issue.m Error: Jira Error: reporter: Field 'reporter' cannot be set. It is not on the appropriate screen, or unknown.... Link to comment Share on other sites More sharing options...
Steve G Posted November 9, 2021 Share Posted November 9, 2021 Hi @Martyn Houghton, I'll add the error code into an output parameter in the next release of the iBridge content pack, will let you know once that's done. Re: the reporter field, that's just how Jira works as far as I'm aware - the field being updated needs to be on the process appropriate screen even when updating via the API. There's nothing we can do about that I'm afraid Cheers, Steve 1 Link to comment Share on other sites More sharing options...
Steve G Posted November 11, 2021 Share Posted November 11, 2021 Hi @Martyn Houghton, FYI Cheers, Steve Link to comment Share on other sites More sharing options...
Martyn Houghton Posted November 11, 2021 Author Share Posted November 11, 2021 @Steve G Thanks for adding the new operation and the error handing, that will help a lot. Cheers Martyn 1 Link to comment Share on other sites More sharing options...
Martyn Houghton Posted November 18, 2021 Author Share Posted November 18, 2021 @Steve G I have been testing the new error control on the JIRA iBridge item. I noticed that the error parameter does not persist only the status, so if I branch based on the status I seem to lose the ability to use the error parameter. Cheers Martyn Link to comment Share on other sites More sharing options...
Steve G Posted November 22, 2021 Share Posted November 22, 2021 @Martyn Houghton Seems to work ok for me? I've added an update timeline automation after the decision, which is writing the iBridge returned error into the timeline: Do you have the correct variable reference in the request update automation? Cheers, Steve Link to comment Share on other sites More sharing options...
Martyn Houghton Posted November 26, 2021 Author Share Posted November 26, 2021 @Steve G I give it another go and let you know. Cheers Martyn Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now