Jump to content

Martyn Houghton

Hornbill Users
  • Content Count

  • Joined

  • Last visited

  • Days Won


Martyn Houghton last won the day on October 15

Martyn Houghton had the most liked content!

Community Reputation

273 Excellent


About Martyn Houghton

  • Rank
    Senior Member

Profile Information

  • Gender
  • Location

Recent Profile Visitors

2,861 profile views
  1. @PeterL Looks like you mail server is possibly terminating you connection. I would get the mail server administrator to check the server logs at their end and also the antispam/Denial of Service settings, as I think this is what is being triggered. Cheers Martyn
  2. @Steve G Thanks for the advice, I had indeed got the full URL as we do for the on premise version, so will give a re-test now I have just the endpoint name. Cheers Martyn
  3. @PeterL It looks like the mail server is applying restrictions on the frequency of 'Get' requests on the mailbox, hence the " Request is throttled" message, to protect itself. Whilst checking out the source mail server settings, you could increase the mail.importer.pollinterval to 240 seconds (4 mins) to avoid the frequency throttling to see if that alleviates the issue. Cheers Martyn
  4. Now got the list of priority id using endpoint rest/api/2/priority and id value 1 is valid. There are only five of them P1 to P5 with id's of 1 to 5. I try setting reporter next to see if that helps. Cheers Martyn
  5. @HHH Good point on the custom fields. I give that a go. I struggling to identify the ID for the priorities as the /rest/api/2/issue/createmeta endpoint does not seem to list priorities. Cheers Martyn
  6. I am now looking to integrate to a JIRA Cloud instance as well as on premises, but have struck a problem with creating a test request as the integration process is failing, but the error in the logs is not given any indication of the why. I can create a request manually using the same credentials with only specifying the Summary, Description and Priority. I suspect the issue is the priority value but cannot be sure as there is not detailed error/response information being provided. Is there any additional logging we can check to help diagnose where it is failing? Cheers Martyn
  7. @Adrian Simpkins Most of these are configured by the Service Manager - Settings beginning with "guest.ui.app.com.hornbill.servicemanager.operation.defaultVisibility". I suspect the one you are after is " guest.ui.app.com.hornbill.servicemanager.operation.defaultVisibility.update" Cheers Martyn
  8. @James Ainsworth @Steven Boardman Can you advise is there are any plans to address the issue of suspending and awaiting a 'Sub Status' change, as not currently having the ability to suspend the workflow and await the change from one sub-status to another under the same parent status is quite an problem for us for the new services we are bringing online this quarter. Trying to use suspend and await expiry to check to periodically if the sub status has changed is not efficient on the our instance resources and will quickly hit the maximum number of steps. Cheers Martyn
  9. To avoid having to hard code numerous 'Assign to Request Creator' nodes in our generic BPM workflow, can the 'Team' property on the node be enhanced to allow the insertion of variables as well as manual selection. I have tried assign it to the team before hand and leaving the value as 'Auto' but this does not work and causes the workflow to break. Cheers Martyn
  10. @HHH I believe you can use the % prefix to give you limited wild card searching, but would like to see this improved further. Cheers Martyn
  11. +1 for the Expire At option, to set a specific time rather than duration. We have also raised related enhancement to be able to insert variables in the the suspend nodes expiry values. Cheers Martyn
  12. @Daniel Dekel Thanks for the clarification and I can now indeed see/make visible Alternate Telephone 2 aka h_tel_3. I will keep an eye out for the update to include the Alternate Email 2 aka h_email_3. Cheers Martyn
  • Create New...