ChiliProject is not maintained anymore. Please be advised that there will be no more updates.

We do not recommend that you setup new ChiliProject instances and we urge all existing users to migrate their data to a maintained system, e.g. Redmine. We will provide a migration script later. In the meantime, you can use the instructions by Christian Daehn.

Updating a ticket that was created by email forces a "change" of description (Bug #501)


Added by Ryan Briones at 2011-06-30 06:29 pm. Updated at 2011-07-01 07:28 pm.


Status:Closed Start date:2011-06-30
Priority:Normal Due date:
Assignee:Eric Davis % Done:

0%

Category:Mail Receiving
Target version:2.0.0
Remote issue URL: Affected version:unstable

Description

Version: ChiliProject 2.0.0 RC1

Scenario:
  1. Send an email that gets pulled in to ChiliProject as an "incoming email"
  2. Ticket is created
  3. Go to Web UI for newly created ticket
  4. Edit
  5. Change nothing
  6. Submit edit form
  7. Ticket shows "Description has changed" from "abc" to "abc";

I thought at first it was an Rich Text or HTML formatted email thing, but I sent a plaintext email and it did the same thing. My guess is the JournalFormatter related stuff, setup by register_on_journal_formatter(:plaintext, 'subject', 'description') is changing the value of description when journaling for the first time.


Associated revisions

Revision 32f92a50
Added by Eric Davis at 2011-07-01 09:25 pm

[#501] Ugly patch to stop creating journals when only line endings change

History

Updated by Eric Davis at 2011-07-01 05:22 pm

Confirmed. The first update creates a journal that says the description changed, even though it didn't. Looking into it now.

  • Assignee set to Eric Davis

Updated by Eric Davis at 2011-07-01 06:33 pm

It looks like the problem is from line endings. The mail is using "\n" in the description but when you update the issue the browser changes them to "\r\n" which makes a journal update. Really odd.

Updated by Eric Davis at 2011-07-01 07:28 pm

This was difficult to test and fix but I think I have a work around for now. When an issue is updated and the only change in the description is line endings, then the description will no longer be included in the journal.

32f92a5

  • Status changed from Open to Closed

Also available in: Atom PDF