Brett, thanks for the great feedback! Let me address each of them individually:

1. The LAD documentation descended from the EJQT documentation so you will need to help me better understand how it is less comprehensive than the EJQT guide. Credentials are covered in the Navigation section, Server Name(Jira Instance) is covered in the Query Configurations section under General Configurations, and the workflow set up is covered Workflow Configurations section.
2. Excellent point on the dates. I will be the first to admit that I don’t think as globally as I should. I will build in a configuration to allow the date formats to be configurable.
3. The times coming through as text is by design because I wanted to be able to distinguish between 0 and no value. When the field type is numeric 0 and no value are the same. I don’t see where the percentiles fail. Do you mean the percentiles are coming up with an incorrect number as a result?
4. The last column in the Queried Data field is used to by the Min Lead Time and Max Lead Time Filter configurations. This allows you to filter out anomalies in the data. For instance default configurations prevent any issue with a lead time of less than 5 minutes and greater than 15 weeks from being included in the processed data. Anything with a 1 in that column is excluded. If you don’t want any issue filtered then you can set both configurations to 0. This is covered in the Query Configurations section under General Configurations.
5. Can you explain what you mean by a real CFD? The CFD charts follow Vacanti’s 6 CFD properties. They only contain issues that have been completed.
6. That’s correct it starts the aging based on the create date of the issue. I considered making this configurable, but decided to hold off because it would have held up publishing the LAD to make the necessary changes. I will consider it for a future release. I am planning to release an updated version sometime next week. If I can fit this in I will.