v6.3.0 native SDKs are built to provide additional support for Custom Issue Fields!
For running workflows and reports on user metadata, we recommend using this new method of implementation to directly pass through data as Custom Issue Fields into your Dashboard. Also, with this SDK, you are no longer limited to passing through metadata as single line text fields. You will now have the ability to send data from the SDK directly to Issues in the form of drop-down fields, booleans, numbers, checkboxes, and increments of time using Custom Issue Fields.
Please review our release notes to see the other additions and fixes this build has to offer:
Check out our November/December SDK Schedule and subscribe to our Helpshift SDK Twitter for release announcements.
Learn Custom Issue Fields Basics
We recommend reviewing the following updated articles so you can begin planning your transition to Custom Issue Fields. The specifics of your migration will depend on your unique use cases you’ve set up your workflows to support.
- What’s the difference between Metadata, Custom Issue Fields, and tags?
- Custom Issue Fields Guide
- How do I migrate to using Custom Issue Fields when I already have metadata And tags?
Observe Usage Patterns in Power BI
The Custom Issue Fields content pack is now available in Power BI. For more information, please see How do I enable Custom Issue Fields for reporting in Power BI?
If you have not y et upgraded to v6.2.0, please review our September/October 2017 SDKs for a full list of all deprecations and API changes before upgrading to v6.3.0.