PDA

View Full Version : Commit ChangeLog (Build 663 to 687) - Reports, Watcher Attachments, Importers, Fixes


jstanden
08-06-2008, 08:46 AM
* [Mail] CHD-740 Deleting ticket sends closed autoresponse

* [Mail] Closed ticket auto-responses always sending now (instead of honoring the 600-second wait period for other auto responses)

* [Importer] Progress on ticket imports in the Cerb4 universal importer

* [Reports] Refactored the reports page. Plugins like Time Tracking or CRM can now contribute their own Report Group and Report extensions to the main reporting page. This makes the reporting area much more reusable, and opens up the ability to create detailed reports for specific needs without cluttering the app.

* [Reports] Added a Group Rosters report.

* [Platform] Added a logging service to DevblocksPlatform.

* [Scheduler] The /cron controller can now accept '&reload=' and '&loglevel=' query parameters. By default, /cron will no longer auto-refresh or show output. This will allow people to use the crontab error reporting properly instead of sending all output to /dev/null and never knowing about trouble. With &reload you can specify the number of seconds to auto-refresh the page when running scheduled tasks in the browser -- which is especially helpful for attended imports. With &loglevel you can specify the minimum priority of logging events to display. Typical levels would be 3 (errors and worse), 5 (warnings and worse), 6 (info and worse) or 7 (full debug and everything).

* [Scheduler] In line with the /cron and logging changes, the Config->Scheduler area will automatically provide /cron URLs with the &loglevel and &reload set to contextually-useful values.

* [Pre-Parser Rules] CHD-722: Auto-check header rule checkbox upon typing in the field

* [Usability] CHD-742: "Close" button in pop-up windows may lead to confusion with actually closing tickets (Jeff@WGM: Changed the buttons to "Cancel")

* [Usability] CHD-757: 'Updated' column is only being refreshed with current timestamp after moving ticket from display page. (Jeff@WGM: Fixed the inconsistency. On inbound/outbound messages will change the "Updated" column. Moving the ticket from Display Ticket will no longer reorder lists sorted on the Updated column.)

* [Ticket Field] CHD-743: Creating long field names will result in "blank" entries in the database (Jeff@WGM: Updated the max length to 128 characters. Added a MAXLENGTH attribute to text input fields.)

* [Group Config] CHD-746: Enforce email validation on Group Email Preferences e-mail address. (Jeff@WGM: The sender address in Group Config is now validated on form submit. Invalid values are discarded so the valid helpdesk defaults will take over.)

* [Overview] CHD-744: Last action incorrect after merge (Jeff@WGM: The most recent action and sender of the merges will now be used on the destination ticket.)

* [Parser] CHD-673: Autoreply marks tickets as non-spam (Jeff@WGM: Autoreplies will no longer be automatically marked as notspam when outgoing mail is sent. Tickets will still be trained as notspam when workers normally reply.)

* [Search] CHD-478: Using a decimal in a date search param breaks the view (Jeff@WGM: The ticket search will now translate periods into dashes for date entry. Completely invalid input, such as random words, will be converted to a 'from' of the earliest possible date and a 'to' of the current time.)

* [Mail] CHD-683: Preserve whitespace formatting in comments

* [Mail] Message content, sticky notes and ticket comments now all use a fixed-width font to preserve whitespace formatting. Source code fragments, HTML snippets and structured data like XML should now display with much more readability.

* [Notifications] CHD-291: Watcher e-mail attachments (Jeff@WGM: Attachments on incoming mail will now be proxied out to the watchers. The auto-generated original_message.html part is currently ignored.)

* [Notifications] Watcher e-mail bounces will now route back to the helpdesk via the ReturnPath header, rather than sending to the original requester list.

* [Notifications] You can now use watcher commands like [take] or [close] by replacing the entire subject line in your watcher response -OR- by appended the [command] to the end of the subject line.

* [Notifications] CHD-578: Emailing Comments -- allow comment submission by email (Watcher Subject Command: [comment]) (Jeff@WGM: You can now instruct Cerb4 to treat your watcher reply as a comment by appending [comment] at the end of the subject line in your response, or by making "[comment]" alone the entire subject.)

* [Tasks] CHD-613: Allow deletion of tasks (Jeff@WGM: You can now delete a task from the popup if you're the owner or a superuser.)

* [Platform] CHD-593: If you invalidate the database login/pass and clear cache the installer will try to run instead of an error.

* [Platform] Added better error reporting in the Devblocks Database Service if the database login details have changed externally.

* [Parser] Improved the HTML to Text conversion for incoming e-mail that doesn't provide a plaintext part.

* [Demo Mode] CHD-771: You can still manipulate POP3 mailboxes in demo mode. (Jeff@WGM: Fixed. I also made sure the POP3 password isn't displayed in the HTML form.)

* [Usability] CHD-304 textarea tags causing issues in part of the helpdesk

* [Usability] Typo in um.core/templates/portal/sc/internal/contact/step2.tpl.php

* [Support Center] CHD-733: Handle reply address on a single contact situation

* [Importer] Implemented full ticket importing (tickets with meta, messages, content, comments, attachments).

* [Importer] Implemented worker importing

* [Reports] Added the 'Average Response Time' report

* [Reports] Added custom date range choosers to applicable reports, date validation

* [Importer] Improved error handling and logging when parsing import XML files. Imported tickets will now be filed in their requested Group and Bucket. Currently, the recommended process is having the exporter create a new temporary Group in Cerb4 for each source (e.g. Gmail, Cerb3, Cerb2). The original folders/queues/buckets in the source are treated as buckets under the tentative group in Cerb4. We'll be providing functionality to quickly move these imported tickets into the local helpdesk structure without triggering mail rules or events (which will be much faster, and won't generate a bunch of needless mail). We also now base64 encode the content blocks on imported tickets to work around issues with nested XML in message bodies, or non-UTF8 characters like MS Word's apostrophes.

brendonhatcher
08-07-2008, 03:42 PM
Hi

In the latest version, the configuration screen where you get the cron url to add to crontab is a bit misleading.

The text says http://xxxxxx/index.php/cron
However, if you copy the url, it says http://xxxx/index.php/cron?loglevel=3

So, depending on your approach, you end up copying a different url.

If I understand the process completely, cron urls for lynx have no log level parameter, but do not need to be dumped to /dev/null because the cron generates no output.

With the loglevel parameter, the url generates output based on the log level you select.

So, lynx -dump http://xxxxxx/index.php/cron will be fine?

Thanks
Brendon

Correct

Hildy
08-07-2008, 10:22 PM
You probably want the loglevel=3 so it will print messages on errors (which cron should then mail you) so you can check them out.

jstanden
08-08-2008, 03:40 AM
I'm pretty sure all he was saying is the link is different than the text:
<a href="link">text</a>

@Joe that's an easy "improvement" task in JIRA.

joegeck
08-08-2008, 03:55 AM
I'm pretty sure all he was saying is the link is different than the text:
<a href="link">text</a>

@Joe that's an easy "improvement" task in JIRA.

That simple huh :) Added to our tracking portal.

http://www.wgmdev.com/jira/browse/CHD-785
[Interface] Cron URL text displayed in Helpdesk scheduler links to a a URL appended with ?loglevel=3