This mail is an automated notification from the task tracker
of the project: Savane.
/**************************************************************************/
[task #517] Latest Modifications:
Changes by:
Mathieu Roy <[EMAIL PROTECTED]>
'Date:
ven 28.05.2004 à 15:35 (Europe/Paris)
What | Removed | Added
---------------------------------------------------------------------------
Should Start On | | ven 28.05.2004 à 00:00
Should be Finished on | | dim 28.11.2004 à 00:00
Category | None | Backend
Priority | 3 - Normal | 4 - High
Summary | Reassigned item: CCMAIL in cvs ci to automatically close
bugs/tasks | cvs commitinfo support for closing items
/**************************************************************************/
[task #517] Full Item Snapshot:
URL: <http://gna.org/task/?func=detailitem&item_id=517>
Project: Savane
Submitted by: Paulevé Loic
On: ven 28.05.2004 à 15:34
Should Start On: ven 28.05.2004 à 00:00
Should be Finished on: dim 28.11.2004 à 00:00
Category: Backend
Priority: 4 - High
Resolution: None
Assigned to: None
Percent Complete: 0%
Status: Open
Effort: 0.00
Planned Release:
Summary: cvs commitinfo support for closing items
Original Submission: Is it possible to add a special CCMAIL in log message
from cvs commit to automatically close/reply a bug/task?
like
CCMAIL: [EMAIL PROTECTED]
is this already supported ? if yes what is the syntax of email adress ?
Thanks.
Commentaires :
------------------
-------------------------------------------------------
Date: ven 28.05.2004 à 15:34 By: yeupou
This item has been reassigned from the project Administration support tracker
to your tracker.
The original report is still available at support #234
Following are the information included in the original report:
[field #0] <font class="preinput"><font class="help" title="Unique item
identifier">Item ID: </font></font> 234<br>[field #1] <font
class="preinput"><font class="help" title="Unique project identifier">Group ID:
</font></font> 101<br>[field #2] <font class="preinput"><font class="help"
title="Current Status">Status: </font></font> Open<br>[field #3] <font
class="preinput"><font class="help" title="Impact of the item on the system
(Critical, Major,...)">Severity: </font></font> A - Undefined<br>[field #4]
<font class="preinput"><font class="help" title="Generally high level modules
or functionalities of the software (e.g. User interface, Configuration Manager,
etc)">Category: </font></font> Savane Tools<br>[field #5] <font
class="preinput"><font class="help" title="User who originally submitted the
item">Submitted by: </font></font> panard<br>[field #6] <font
class="preinput"><font class="help" title="Who is in charge of handling the
item">Assigned to: </font></font> None<br>[field #7] <font
class="preinput"><font class="help" title="Date and time of the initial
submission">Submitted on: </font></font> lun 24.05.2004 à 17:10<br>[field #8]
<font class="preinput"><font class="help" title="One line description of the
item">Summary: </font></font> CCMAIL in cvs ci to automatically close
bugs/tasks<br>[field #9] <font class="preinput"><font class="help" title="Full
description of the item">Original Submission: </font></font> Is it possible to
add a special CCMAIL in log message from cvs commit to automatically
close/reply a bug/task?<br />
like<br />
CCMAIL: [EMAIL PROTECTED]<br />
<br />
is this already supported ? if yes what is the syntax of email adress ?<br />
<br />
Thanks.<br>[field #11] <font class="preinput"><font class="help"
title="Characterizes the nature of the item (e.g. Crash Error, Documentation
Typo, Installation Problem, etc">Item Group: </font></font> None<br>[field #12]
<font class="preinput"><font class="help" title="Current resolution of the
item">Resolution: </font></font> None<br>[field #13] <font
class="preinput"><font class="help" title="Version of the System Component
impacted by the item">Component Version: </font></font> None<br>[field #14]
<font class="preinput"><font class="help" title="Name and version of the
platform impacted by the item">Platform Version: </font></font> None<br>[field
#15] <font class="preinput"><font class="help" title="How easy it is to
reproduce the item">Reproducibility: </font></font> None<br>[field #16] <font
class="preinput"><font class="help" title="Estimated size of the code to be
developed or reworked to handle the item">Size (loc): </font></font>
None<br>[field #17] <font class="preinput"><font class="help" title="Release in
which the item was actually implemented">Fixed Release: </font></font>
None<br>[field #18] <font class="preinput"><font class="help" title="Release in
which it is planned to have the item implemented">Planned Release:
</font></font> None<br>[field #19] <font class="preinput"><font class="help"
title="Number of hours of work needed to handle the item">Effort:
</font></font> 0.00<br>[field #23] <font class="preinput"><font class="help"
title="How quickly the item should be implemented (Immediate, Normal, Low,
Later,...)">Priority: </font></font> 5 - Normal<br>[field #26] <font
class="preinput"><font class="help" title="">Percent Complete: </font></font>
0%<br>[field #28] <font class="preinput"><font class="help" title="Release
(global version number) impacted by the item">Release: </font></font>
None<br>[field #53] <font class="preinput"><font class="help"
title="Customizable Select Box (pull down menu with predefined values)">Custom
Select Box #1: </font></font> None<br>[field #54] <font class="preinput"><font
class="help" title="Customizable Select Box (pull down menu with predefined
values)">Custom Select Box #2: </font></font> None<br>[field #55] <font
class="preinput"><font class="help" title="Customizable Select Box (pull down
menu with predefined values)">Custom Select Box #3: </font></font>
None<br>[field #56] <font class="preinput"><font class="help"
title="Customizable Select Box (pull down menu with predefined values)">Custom
Select Box #4: </font></font> None<br>[field #57] <font class="preinput"><font
class="help" title="Customizable Select Box (pull down menu with predefined
values)">Custom Select Box #5: </font></font> None<br>[field #58] <font
class="preinput"><font class="help" title="Customizable Select Box (pull down
menu with predefined values)">Custom Select Box #6: </font></font>
None<br>[field #59] <font class="preinput"><font class="help"
title="Customizable Select Box (pull down menu with predefined values)">Custom
Select Box #7: </font></font> None<br>[field #60] <font class="preinput"><font
class="help" title="Customizable Select Box (pull down menu with predefined
values)">Custom Select Box #8: </font></font> None<br>[field #61] <font
class="preinput"><font class="help" title="Customizable Select Box (pull down
menu with predefined values)">Custom Select Box #9: </font></font>
None<br>[field #62] <font class="preinput"><font class="help"
title="Customizable Select Box (pull down menu with predefined values)">Custom
Select Box #10: </font></font> None<br>
-------------------------------------------------------
Date: ven 28.05.2004 à 15:34 By: yeupou
(First "close #1231" cant work, for the simple reason that id are tracker
specific)
In fact, it does not have to involve cvsreport at all (it would be best if he
does not, to avoid getting savane to tighly bound to a specific program). It is
just a matter of having a backend on cvs.gna.org that can access db.gna.org and
do simple task like closing/reopening items after checking privileges, an
posting as the ChangeLog entry as comment. If can be very handy indeed.
It should be very complex to implement either, just one more backend script.
But this backend script should be clearly cleanly secured, as it won't be run
by us but by user (I do not mean that the other script are not secure at all,
but we definitely have to pay lot of attention when writing this one).
As this is clearly a feature that is missing in the Savane backend, I reassign
the item where it should be.
Regards,
-------------------------------------------------------
Date: jeu 27.05.2004 à 16:00 By: panard
Yes, I'm totally agree with you, there is a big security issue.
A command like 'close bug #1367' or 'close task #1230' is a very good idea, and
would as usefull as the CCMAIL.
-------------------------------------------------------
Date: mer 26.05.2004 à 19:33 By: zerodeux
This is handy and would be quite easy to provide, but I think there would be
some authentication issue : I'm not sure we would allow a Gna! user to close a
bug only by trusting the From: field of an e-mail. Although the latter would be
locally generated and the [EMAIL PROTECTED] 'gateway' could check that the
source is a Gna! machine.
Technically, cvsreport will have to be able to handle the 'ccmail:' request,
not a big deal. But that could be abused to spam if we don't check destinations
properly.
All considered, it would be easier for Gna! to implement the feature without
the e-mail gateway : a simple command like 'close #1367' could call the proper
backend, and the commit IS properly authenticated (thanks to SSH). This could
be a cvsreport plugin. What do you think ?
-------------------------------------------------------
Date: mer 26.05.2004 à 11:22 By: panard
In the commit log message, you can add :
CCMAIL: [EMAIL PROTECTED]
And this will close the bug 1367 with as an additional comment the content of
cvsreport.
I think that CCMAIL is really used as is, and its when you mail to [EMAIL
PROTECTED], that a 'daemon' close the bug and add the commentary.
Here is an example : http://bugs.yzis.org/show_bug.cgi?id=10
Perhaps CCMAIL command must be supported by cvsreport and a sort of daemon must
filter (bugs|tasks)-<number>[EMAIL PROTECTED] and do the appropriate action
with it.
I really love this feature, and I'll be really happy if gna! may support it.
I know that kde support it, the tools may perhaps already exist...
-------------------------------------------------------
Date: mer 26.05.2004 à 10:54 By: yeupou
No, this is not supported right now.
Can you details how it should work in your opinion?
For detailed info, follow this link:
<http://gna.org/task/?func=detailitem&item_id=517>
_______________________________________________
Message sent via/by Gna!
http://gna.org/
