LSAD Updates

I have made a number of updates to the LSAD that make it easier to diagnose configuration issues as well as provided a work around for an issue with the Jira sprint field:

• Specific errors will now be thrown when there are no sprints returned for a given board id, there are no sprints within the configured time range, and/or there are no issues returned for a given set of sprints. This will make it easier to determine what specific configuration is in error. Previously the errors were generic making it difficult to determine the root cause
• A data validation was added to the Jira Instance URL configuration that will prevent the protocol prefix (https://) from being included in the entry. Some people didn’t realize this and had gotten stuck so now the validation will prevent the prefix from being included
• It turns out that the field used to contain the sprint information can vary from instance to instance in Jira. Previously I had thought it was customfield_10281 for Jira Server and customfield_10021 for Jira Cloud, but apparently it is not limited to those two fields. To work around the issue I implemented a configuration that allows you to specify what field that is being used in your particular instance. The configuration is documented in the LSAD Guide.
• I added a section to the LSAD Guide that explains the Available Fields configuration. The majority of the time you don’t need to touch this section other than the new configuration mentioned above, but in case you have customized fields in your instance that the LSAD uses this will explain how to adjust the Available Fields configuration accordingly

The updated version of the LSAD is available on the Agile Creatives Tools Page