Jump to content

Steve G

Hornbill Developer
  • Content Count

  • Joined

  • Last visited

  • Days Won


Steve G last won the day on March 27

Steve G had the most liked content!

Community Reputation

49 Excellent

About Steve G

  • Rank
    Senior Member

Profile Information

  • Gender
  • Location
    Hull, UK

Contact Methods

  • Website URL

Recent Profile Visitors

1,140 profile views
  1. Hi @HHH, The Jira and Jira Cloud integrations for Create Issue and Update Issue now support custom fields of type array. On the integration methods, there is a new Request Parameter called Custom Fields (Arrays) , which when configured will add the relevant custom field data to the API call to Jira. For example, this will set the First Option and Third Option values against the multi-select item with the key of 10028 against any new issues created: As you can see in the issue generated: And the custom field defined as: The data types available to array-type custom fields are MultiGroupPicker, MultiSelect, MultiUserPicker and VersionPicker, as defined by Jira and should match the type of your custom field. See the Jira documentation for more information: https://developer.atlassian.com/server/jira/platform/jira-rest-api-examples/ Let me know how you get on with these enhancements. Thanks, Steve
  2. Hi @Dan Munns, That's done and released to Github . There's a new boolean property as part of the Schedule in the config: DayOfMonthANDDayOfWeek Setting this to false will use the existing crontab standard expression parser. Setting this to true will use the existing parser, but will also check to see if the day of week AND day of month both match before executing the API call. Let me know how you get on with this. Cheers, Steve
  3. Hi Dan, After looking at the code and re-reading the crontab specification, this is working as expected: http://pubs.opengroup.org/onlinepubs/7908799/xcu/crontab.html From the examples: I may be able to add some extra logic in the tool to cater for your use case though. I'll let you know once I've come up with a solution. Cheers, Steve
  4. Hi @Dan Munns, I've been able to replicate this, it looks like the day of week and day of month values in the expression are applied with an OR instead of an AND. I'm just looking into the cron package now to see if there's anything we can do about that, will let you know when I have an answer. Cheers, Steve
  5. Hi @Martyn Houghton, That's a good shout, I'll raise the suggestion and let you know the outcome. Cheers, Steve
  6. Hi @Martyn Houghton, I've just released v1.3.0 of the Hornbill Request Import tool, with the following features: Added support to import Releases Added MySQL 8.x support Can now map and resolve Catalog Items for Services, and to use the Catalog Item BPM workflow should one exist Can now set default Catalog Item if default Service is applied Can now set default owner alongside default team Added version flag for cross-compiling script support It's documented on its wiki page, and you can get the OS and architecture specific zips from Github. Notes regarding a couple of the points you requested: Add the additional custom fields which now go up to h_custom_t and h_custom_30. This is already supported, you just need to add the additional fields to the CoreFieldMapping and AdditionalFieldMapping columns Extend current supported request types, Incident & Service Request, to include all other types, i.e. Change, Problem, Known Error and Release. Aside from Release, this was already supported. You just need to copy & paste one of the other objects from within the RequestTypesToImport array and configure accordingly Support the import and matching of Sub Status, only current supports parent status. There's a lot of logic in Service Manager that handles stuff happening on the back of sub status changes, so this should be built into your workflows instead Support the import and matching of Service Level Agreement and Service Level's. Same as the Sub Status comment, above. Simplify the historic updates import section, to provide separate fields to indicate source, visibility, user etc, rather than using the Supportworks native bitwise format. This is legacy stuff to support Supportworks imports, and providing of the correct bitwise flag can be done in the SQL, so I'll add an example to the documentation rather than hard-code it in the tool Cheers, Steve
  7. Hi @Martyn Houghton, Apologies, it looks like the build script missed the copy of the conf file. The release has been updated to include that now. Cheers, Steve
  8. Hi @Izu, This has now been released. The OS and architecture specific release ZIPs can be downloaded from here: https://github.com/hornbill/goHornbillCleaner/releases/latest Note: this requires Service Manager build of at least 1459 to be running on your instance. Cheers, Steve
  9. Hi @Joanne, This has now been fixed, you can now use square brackets to wrap column names for SQL Server column names that include spaces, or back-ticks to wrap column names for MySQL/MariaDB column names that include spaces. MS SQL Server example: MySQL/MariaDB example: Note, the left-hand property in the mapping is the Report column name property, and the right-hand values are the Database column name where the record values will be written in to. The Report column name properties can include spaces and don't need to be wrapped by any [] or `` characters. The latest release ZIPs can be found here: https://github.com/hornbill/goHornbillDataExport/releases/latest You just need to download the ZIP that is relevant to your operating system and architecture. Let me know how you get on with this. Cheers, Steve
  10. Hi @Dan Munns, There was a duplicate task bug with the Go cron library used to build this tool, but was only evident on certain Windows builds - this was probably what was causing your issue. I've just released v1.2.1 of the tool that contains the latest cron library, which includes a fix for that issue. Could you download the OS-specific release ZIP from here and let me know if this fixes the issue for you? https://github.com/hornbill/goAPIScheduler/releases/tag/1.2.1 Cheers, Steve
  11. Hi @Dan Munns, I'll have a look to see if I can replicate this, will get back to you with the results. Cheers, Steve
  12. Hi @Martyn Houghton, This is because the tool is expecting the Service Manager Priority names to be entered in the property values (on the right-hand side of the PriorityMapping properties), and not the primary keys. I have noticed an enhancement that I need to make to that code though, which I'll include in the next release. I'm going through the other required changes currently, so should hopefully have a new release of this tool out in the next day or so. I'll let you know once released. Cheers, Steve
  13. Hi @Martyn Houghton, I'm not able to replicate this issue locally with a properly defined configuration, connecting to a MySQL 8.0 data source (as I've been updating the source to work with this - should have a release out in the next couple of days) I'm able to pull and import all records from my test database. Do you have the tool configured to connect to the data source directly, or via ODBC? It's unlikely to be reserved characters causing the issue, as the driver should still be able to get at those records, and if not then an error would be written to the log during the unmarshalling of the record data. One scenario which may see this behaviour would be if the tool detects that the request record already exists in memory (as there's code to prevent duplication of imported requests). So if the value of the column defined in the RequestReferenceColumn property is not unique. What do you have defined in your incident import config, as does that match the request reference column in your source data? Thanks, Steve
  14. @Martyn Houghton You would indeed be correct If the request being imported is in a cancelled, resolved or closed state, the BPM is not spawned. Cheers, Steve
  15. Hi @Martyn Houghton, That's correct, the on-hold date/time should be added to the h_dateclosed field. Cheers, Steve
  • Create New...