Return-Path: X-Original-To: apmail-incubator-allura-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-allura-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 1CD9410EC8 for ; Fri, 28 Feb 2014 10:14:37 +0000 (UTC) Received: (qmail 2813 invoked by uid 500); 28 Feb 2014 10:14:35 -0000 Delivered-To: apmail-incubator-allura-dev-archive@incubator.apache.org Received: (qmail 2744 invoked by uid 500); 28 Feb 2014 10:14:34 -0000 Mailing-List: contact allura-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: allura-dev@incubator.apache.org Delivered-To: mailing list allura-dev@incubator.apache.org Received: (qmail 2701 invoked by uid 99); 28 Feb 2014 10:14:32 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 28 Feb 2014 10:14:32 +0000 X-ASF-Spam-Status: No, hits=-0.1 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of noreply@sourceforge.net designates 216.34.181.60 as permitted sender) Received: from [216.34.181.60] (HELO smtp.ch3.sourceforge.com) (216.34.181.60) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 28 Feb 2014 10:14:27 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sourceforge.com; s=x; h=Date:References:In-Reply-To:Message-ID:Subject:Reply-To:From:To:MIME-Version:Content-Type; bh=5AAkRtZa0K1n+F2IxfWlyAv53u12D3ZRDd6ZUcMv/S4=; b=IBFodMrRvhKQcvFsoGEUbAgIsj2b+ZO4MMFA+pTBh1C4vD+9hJ2GmNawUeUNok/8cmt2LUFOofuFTcTQk0IPgmv6BdZB/upamYzvOIe1sVJSXgr7c4uujHRqqBu/rvcd1IlQnxiQzqgrphTU0vy75alufRcRRwh9it0ipfecxB0=; Received: from localhost ([127.0.0.1] helo=sfs-alluradaemon-3.v29.ch3.sourceforge.com) by sfs-alluradaemon-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WJKSF-0004yF-Bc for allura-dev@incubator.apache.org; Fri, 28 Feb 2014 10:14:07 +0000 Content-Type: multipart/related; boundary="===============2365641713190991134==" MIME-Version: 1.0 To: allura-dev@incubator.apache.org From: "Igor Bondarenko" Reply-To: "[allura:tickets] " <6305@tickets.allura.p.re.sf.net> Subject: [allura:tickets] #6305 Merge email notifications when possible Message-ID:

In-Reply-To: <51a77a24b9363c3d02538493.tickets@allura.p.sourceforge.net> References: <51a77a24b9363c3d02538493.tickets@allura.p.sourceforge.net> Date: Fri, 28 Feb 2014 10:14:07 +0000 X-Virus-Checked: Checked by ClamAV on apache.org --===============2365641713190991134== Content-Type: multipart/alternative; boundary="===============5209264935558066183==" MIME-Version: 1.0 --===============5209264935558066183== MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Closed #535. `je/42cc_6305` --- ** [tickets:#6305] Merge email notifications when possible** **Status:** code-review **Labels:** p3 support 42cc **Created:** Thu May 30, 2013 04:11 PM UTC by Chris Tsai **Last Updated:** Mon Feb 17, 2014 02:25 PM UTC **Owner:** nobody [forge:feature-requests:#117] >When more than one change is done to a ticket at the same time, e.g. changing the ticket status and posting a comment, I would like these changes to be sent in a single email notification rather than as two separate emails. >Update: This applies not only to the email notifications; discussion posts should also be merged. Look for example at the first two posts for ticket [forge:feature-requests:#97]. They belong together and should have been merged into a single entry. I agree 100% --- Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list. --===============5209264935558066183== MIME-Version: 1.0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: 7bit

Closed #535. je/42cc_6305


[tickets:#6305] Merge email notifications when possible

Status: code-review
Labels: p3 support 42cc
Created: Thu May 30, 2013 04:11 PM UTC by Chris Tsai
Last Updated: Mon Feb 17, 2014 02:25 PM UTC
Owner: nobody

[forge:feature-requests:#117]

When more than one change is done to a ticket at the same time, e.g. changing the ticket status and posting a comment, I would like these changes to be sent in a single email notification rather than as two separate emails.

Update: This applies not only to the email notifications; discussion posts should also be merged. Look for example at the first two posts for ticket [forge:feature-requests:#97]. They belong together and should have been merged into a single entry.

I agree 100%


Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.

--===============5209264935558066183==-- --===============2365641713190991134==--