* [CHD-2767] [Mail/Reports/Worklists] Added an 'is broadcast' field to message worklists.  Messages can now be filtered based on whether or not they were sent in bulk as part of a broadcast.  This field can be used by Virtual Attendant behavior, dashboards, and reports to ignore messages that were sent automatically.  For example, when reporting on worker replies it is often desirable to not include messages that were sent in a marketing broadcast as part of a worker's totals.  It's also possible that a dashboard may now report on _only_ messages that were sent in a broadcast.
* [CHD-2565] [Mail/Compose/Owner] When composing mail, an owner may be added in a single step.  Previously an owner could only be assigned once the ticket was created.  This required hunting down the new ticket, which is a productivity killer.
[Code Cleanup] Moved 'response time' to string.xml
* [CHD-3078] [Support Center/Knowledgebase] Fixed an issue with the Knowledgebase in the Support Center where starting a new search didn't reset to the first page of results.

Signed-off-by: Jeff Standen <jeff@webgroupmedia.com>
* [CHD-2787] [Mail/Compose] Fixed an issue where a worker wasn't associated with composed messages that they sent through the Broadcast feature.  This generally wasn't an issue, but it logged a NOTICE in the error log.  It had a happy consequence of not polluting worker reply totals with automated messages, but that's been addressed with the new 'is broadcast' field in 6.1+.
* [CHD-3075] [Virtual Attendants/Usability] Fixed an issue where Virtual Attendant behaviors were displayed alphabetically even if they were previously dragged into a different order.
6.0.6 checkpoint
Merged 6.0.6 -> 6.1
6.1-beta checkpoint
[Code Cleanup]
Merged 6.0.6 -> 6.1
[Code Cleanup/Messages] The 'is broadcast' and 'is outgoing' fields will now render 'yes/no' in worklists rather than 0/1.
[Code Cleanup/Workspaces/Dashboards] Fixed the extension id of chart widgets.  They needlessly used 'calendar' in the namespace due to early testing.
[Code Cleanup/Workspaces/Dashboards] Fixed an issue with dashboards where a search parameter with an '%' could break the widget queries. Escaped % to %%
[Code Cleanup/Workspaces/Dashboards] Float values on chart plots will now format to two decimal places.  If auto-detected as a whole number the decimal places will be dropped.
* [Devblocks/Plugins/Cache] The Devblocks Cache service can now set an expiration on content that is cached to disk.  This was always possible with the memory-based Memcached engine.
* [Dashboards/Widgets/URL] Gauge and Counter widgets on dashboards can now specify an external URL as a data source. This data can be provided in JSON, XML, or Plaintext format.  A cache option is provided so external HTTP requests aren't generated (creating latency) for every impression.  This feature allows you to bring in reporting metrics from any external system, using any backend technology.  By using the HTTP protocol there are several inherent benefits: HTTP authentication, caching, query parameters, etc.  For example, real-time metrics like website traffic or sales stats can be shared with the helpdesk through a simple HTTP script.  In the simplest implementation, the URL just needs to return a quantitative value (a number or decimal) in the response.
* [Workspaces/Dashboards/Counters] Added Counter widgets to dashboards.  A counter displays a single quantitative value -- similar to a gauge, but without specifying thresholds or goals.  The data on a counter can come from a manual value, worklists, sensors, or external URLs.  The counter text is automatically resized to efficiently use the available space.  The text color, data type, prefix, and suffix may be configured.  Data types include numbers, decimals, and time elapsed in seconds (formatted like "2 hours, 13 mins").  There are many uses for counters.  For example, they can display the current response time average, total number of @mentions on Twitter, the overdue task count, real-time website traffic, unpaid invoice totals, etc.
6.1-rc1 checkpoint
6.1-release checkpoint