Jump to content

TrevorKillick

Administrators
 View Profile  See their activity

  • Posts

    780

  • Joined

  • Last visited

  • Days Won

    33

 Content Type 

Everything posted by TrevorKillick

  1. TrevorKillick
    @yelyah.nodrog I have just had a look and i noticed something in the logs, have you got runtime parameters set for the report in question? Kind Regards Trevor Killick
  2. TrevorKillick
    @Dan Munns Apologies for this one, i can confirm the missing paging is now fixed and available. Kind Regards Trevor Killick
  3. TrevorKillick
    @clampj In the Configuration file under "OrgLookup" should be an option "OnlyOneGroupAssignment" set this to true and it will remove any existing memberships so that only one group is associated. https://github.com/hornbill/goLDAPUserImport Kind Regards Trevor Killick
  4. TrevorKillick
    @samwoo HTTP Response 401 Unauthorised makes sense here, do you have any option to allow basic auth for office 365 and Microsoft Flow? The only authentication we support from an outgoing webhook is basic. If not you are likely going to need some glue code to sit in the middle somewhere and accept the webhook even and then pass it off with some authentication over to Microsoft Flow. Kind Regards Trevor Killick
  5. TrevorKillick
    @Martyn Houghton I have updated the wiki page and GitHub documentation. Kind Regards Trevor Killick
  6. TrevorKillick
    @Martyn Houghton Perfect ill stop looking at adding a translation function into the import now them Kind Regards Trevor Killick
  7. TrevorKillick
    @Martyn Houghton I have pinged out cloud team and victor someone should get back to your shortly, apologies for the inconvenience . Kind Regards Trevor Killick
  8. TrevorKillick
    @Martyn Houghton Country Code in hornbill expects a 2 character text string the list of accepted codes can be found here: https://api.hornbill.com/_types/countryCodeType Quick google suggests you country codes are in ISO 3166-1 numeric and we are expecting ISO 3166-1 alpha-2 is ISO 3166-1 numeric a standard in AD? If so i can add a option to replace numeric with alpha 2 on country code? Kind Regards Trevor Killick
  9. TrevorKillick
    This is something we are looking at introducing within the next 90 days, as soon as we have any further updates i will post back. Kind Regards Trevor Killick
  10. TrevorKillick
    @Rohit Govind We recommend marking the user as archived, they will stop consuming a licence and all the data is kept in the system, deleting a user can cause various issues if they have workspace interactions. Kind Regards Trevor Killick
  11. TrevorKillick
    @Martyn Houghton So i have added a new KeySafe authentication type of Jira Authentication which differs to Jira Cloud Authentication as the endpoint expects a FQDN. What we then do is append /rest/api/latest/ to the end of the endpoint before calling an API, this is available on Live now along with a separate set of Jira iBridge methods for on Premise, they are an exact copy of the Jira Cloud methods just they point only at the endpoint URL. As we are unable to rest Jira On Premise please post back any issues and we can take a look at them, also any suggested additions or changes to the integrations are more than welcome. Kind Regards Trevor Killick
  12. TrevorKillick
    @Martyn Houghton Sorry i don't we just spun up a free Trial in June and used that to base the integrations from, if they share the same API what we can easily do is add a KeySafe credential for On Prem Jira which would allow you to set the FQDN to an endpoint of your instance and from there you can try out the integrations and if needed we can look at separating them if there are any issues that would require changes to the integration. I am on leave tomorrow but back in the office tomorrow then off for the rest of the year, i will try and get the new KeySafe Credential type added tomorrow which will be instantly available and then you should be able to try them out in your own time. Kind Regards Trevor
  13. TrevorKillick
    @Martyn Houghton I would be more concerned about versions of the on prem API Changing, the Cloud Rest API is versioned and we currently support V2. Here is an example of the integration we have for create issue using Rest 2 API. https://docs.atlassian.com/software/jira/docs/api/REST/1000.1568.0/#api/2/issue-createIssue Kind Regards Trevor Killick
  14. TrevorKillick
    @samwoo I have just gone through and resolved the issue with Continue on Error not working from a BPM Integration Node, there are a few Server released on their way before this makes it to live as soon as its available i will let you know, just a warning this might not be until early January as we tend to stop pushing new releases as the year ends and we have people on leave. Kind Regards Trevor Killick
  15. TrevorKillick
    @Joyce In the Output Formats tab if you make sure only CSV is checked then the report will only generate the CSV file required by Power BI, to ensure backwards compatibility the default is to generate PDF and CSV if no optional outputs are selected. Kind Regards Trevor Killick
  16. TrevorKillick
    @Martyn Houghton Its potentially possible but would be impossible for us to test and confirm its working. Are the API's exactly the same for the on-prem version? What happens with regards to updates on the on-prem version is there a possiblity we update our integrations in the future to make any changes to JIRA cloud and then the on premise version would stop working? Kind Regards Trevor Killick
  17. TrevorKillick
    @chrisnutt Thanks for the confirmation, Dev took a look at the blank error message presented and fixed the issue so in the future a more friendly error will be presented that should point you in the right direction. Kind Regards Trevor Killick
  18. TrevorKillick
    @chrisnutt Looking at your logs it appears ADFS is failing to sign you in, if you go to https://admin.hornbill.com/INSTANCENAME/?ESPBasic=true you can login and bypass the SSO configuration. For some reason we do not appear to be correctly outputting the ADFS error but at a guess i would imagine the signing certificate as expired. If you go into your SSO Profile (Admin Home -> System -> Security -> SSO Profiles) and update the affected SSO Profile with the refreshed certificate and your all set. Here are a couple of useful links. https://wiki.hornbill.com/index.php/Single_Sign_On_with_SAML_2.0https://wiki.hornbill.com/index.php/SSO_Example_Config_Microsoft_ADFS_2.0_for_User_Accounts Kind Regards Trevor Killick
  19. TrevorKillick
    @mfoster The report outputs have been updated to now be generated in https://eurapi.hornbill.com/INSTANCENAME/dav/reports/REPORTID/REPORTNAME_RUNID.csv However older reports will still be accessed from the old path. Ideally reporting::reportRunGetStatus should be used to obtain the file output for a given report run https://api.hornbill.com/reporting/?op=reportRunGetStatus , reportRun->csvLink is populated with the file name of the CSV to maintain backwards compatibility however there is also and array of output files added to support the additional file types now supported in reporting. Kind Regards Trevor Killick
  20. TrevorKillick
    @SJEaton You can report on h_msg_messages where h_msg_date = CURDATE(); select * from h_msg_messages where h_msg_date = CURDATE(); You could do this as a measure using h_msg_date as a date ranging column with a refresh rate of daily. Filtering by mailbox will be a little tricky as you would need to get the list of folderId for a given mailbox and use where h_folder_id in (x,y,z); Kind Regards Trevor Killick
  21. TrevorKillick
    All, We have released two new iBridge Utility Methods, one returns the current day of the week as a string the other returns the ISO Date String for the next occurrence of a particular day of the week. Our Service Manager team are looking at a change to support putting a request on hold by passing in a date time string instead of a duration, hopefully these changes are beneficial to you all. Kind Regards Trevor Killick
  22. TrevorKillick
    @Martin.bowman Just to update you all customers can now run reports again, there is still a known ongoing issue with the output of dates in reports. This is currently being investigated by our platform team and we hope to get a fix out for this issue as soon as possible. Again Apologies for any Inconvenience caused Kind Regards Trevor Killick
  23. TrevorKillick
    @Martin.bowman We are working on correcting the failed report runs now. The missing dates we are currently investigation. Apologies for the inconvenience. Kind Regards Trevor Killick
  24. TrevorKillick
    @carlt A file was missing from our build we are working on getting this applied to each customer right now. Kind Regards Trevor Killick
  25. TrevorKillick
    @lee mcdermott @Paul Alexander Can you please try running your reports again? Kind Regards Trevor Killick
×
×
  • Create New...