Sorry for using bug tracker for a feature request but wasn't sure where this belongs. We haven't figured out (there might be a way) how to disable change note about attribute changes from tracker emails. In external "client" interface we would not life those to be visible and in internal trackers they would be most convenient.

If there is no configurable way to decide if assignedto, status, priority etc. changes are appended to tracker emails, would it be possible to have a per instance confuration option for that.

Since we weren't smart enough to figure out how to override current behaviour from the per instance extensions/, we ended up doing like this:

19c19
< # $Id$
---
> # $Id: roundupdb.py,v 1.1 2006/07/17 12:05:51 root Exp $
322,323c322,323
<         if note:
<             m.append(note)
---
>         #if note:
>         #    m.append(note)

Huge thanks for considering this!

This patch addresses this RFE by adding a 'mute' parameter to
roundupdb.IssueClass.nosymessage that omits the change note.

It allows one to omit non-journaled *Link properties from an issue
change note by setting a 'quiet' parameter in nosymessage() that reaches
generate[Create|Change]Note().

It also addresses http://psf.upfronthosting.co.za/roundup/meta/issue249
and this RFE by allowing one to hide any non-*Link properties by setting
an attribute 'do_journal=False' on them. This affects both change notes
and history (in templating).

Example usage in schema.py:
nosy_count = Number()
nosy_count.do_journal = False
issue = IssueClass(db, "issue",
                   type=Link('issue_type'),
                   [...]
                   nosy_count=nosy_count)

Here's a cleaner version of the support for quiet properties (the
downstream issue).

Example usage in schema.py:
nosy_count = Number()
nosy_count.quiet = True
issue = IssueClass(db, "issue",
                   type=Link('issue_type'),
                   [...]
                   nosy_count=nosy_count)


If there is still interest in an option to mute/omit selected properties
when calling roundupdb.IssueClass.nosymessage, I can update that part too.

Could you update an option to mute/omit selected properties
when calling roundupdb.IssueClass.nosymessage?

Thanks a ton!

This patch also looks useful even in its current state
where changes to a property will not be included in a
nosymessage by default if the quiet flag is set.

Daniel, did you ever generate a patch to suppress property
change reports for particular properties when calling
roundupdb.IssueClass.nosymessage?

Committed as: 8901cc4ef0e0

I updated the patch so that:

  prop=String(quiet=True)

works as well as:

  prop=String()
  prop.quiet=True

It also works when using the anydb backend.

Also the history) command in templating allows showall=True 
argument to ignore the quiet setting for properties.