You can subscribe to this list here.
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(6) |
Oct
|
Nov
|
Dec
(1) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2003 |
Jan
(14) |
Feb
(10) |
Mar
(20) |
Apr
(17) |
May
(2) |
Jun
(5) |
Jul
(8) |
Aug
(1) |
Sep
|
Oct
(1) |
Nov
(3) |
Dec
(6) |
| 2004 |
Jan
(8) |
Feb
(8) |
Mar
(1) |
Apr
(8) |
May
(3) |
Jun
|
Jul
(2) |
Aug
(3) |
Sep
|
Oct
(1) |
Nov
(8) |
Dec
(5) |
| 2005 |
Jan
(1) |
Feb
(8) |
Mar
(18) |
Apr
(22) |
May
(15) |
Jun
(17) |
Jul
(19) |
Aug
(27) |
Sep
(6) |
Oct
(8) |
Nov
(4) |
Dec
(4) |
| 2006 |
Jan
(2) |
Feb
(3) |
Mar
(6) |
Apr
|
May
(4) |
Jun
(10) |
Jul
(4) |
Aug
(3) |
Sep
(12) |
Oct
(16) |
Nov
(3) |
Dec
(1) |
| 2007 |
Jan
(1) |
Feb
(16) |
Mar
(4) |
Apr
(7) |
May
(3) |
Jun
(2) |
Jul
|
Aug
(15) |
Sep
(1) |
Oct
(1) |
Nov
(2) |
Dec
|
| 2008 |
Jan
(5) |
Feb
(4) |
Mar
(1) |
Apr
(4) |
May
(1) |
Jun
(5) |
Jul
(10) |
Aug
(13) |
Sep
(7) |
Oct
(7) |
Nov
(2) |
Dec
(2) |
| 2009 |
Jan
(24) |
Feb
(6) |
Mar
(16) |
Apr
(23) |
May
(97) |
Jun
(71) |
Jul
(37) |
Aug
(21) |
Sep
(21) |
Oct
(26) |
Nov
(12) |
Dec
(12) |
| 2010 |
Jan
(1) |
Feb
(2) |
Mar
(39) |
Apr
(59) |
May
(67) |
Jun
(64) |
Jul
(32) |
Aug
(45) |
Sep
(26) |
Oct
(3) |
Nov
|
Dec
(1) |
| 2011 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2013 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2014 |
Jan
|
Feb
|
Mar
(1) |
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| S | M | T | W | T | F | S |
|---|---|---|---|---|---|---|
|
|
|
1
|
2
(4) |
3
|
4
(2) |
5
|
|
6
(1) |
7
|
8
(2) |
9
|
10
(1) |
11
|
12
|
|
13
|
14
(1) |
15
(2) |
16
|
17
|
18
|
19
|
|
20
|
21
|
22
|
23
|
24
|
25
|
26
|
|
27
|
28
|
29
|
30
(4) |
|
|
|
|
From: Peter Bengtsson <mail@pe...> - 2003-04-30 17:13:01
|
At 16:36 2003-04-14 +0200, Reinelt, Wolfgang; ZFLS-GD ZEMF * wrote:
>Hi together,
>could somebody give me more details on how to create and deal with new
>properties? I use IssueTrackerProduct-0.5.0b 0.5.0b (Development)
>2003/04/03 100414 bytes from zope.org:
>
>This is what I did so far:
>1. create new property in "properties" tab.
> Q: is the "value" entry in this tab independent of the variables
> in the *.zpt files?
>Expample: define a string named "CustomerReference"
I see no reason to use the properties tab for this. If you want to add
another property to the issues, then you have to modify the sourcecode.
The properties tab is just a long list of constants basically.
It's out of scope for me to lengthly describe how to rewrite the code but
my simple yet effective advice is this:
Search the source code and zpt files for all occurances of the
issueproperty "url2issue". Then, for every line you find this, try to see
how you can squeeze in your customer reference property.
Even better is that you write a monkey patch like ZFIssueTrackerProduct
where you "add" the properties you'll need.
Hope this helps.
Peter
>2. define this property in submitform.zpt with copy and paste from
>another property, depending on if it's just a text field, a selection etc
>Example:
><input type="hidden" name="CustomerReference"
> tal:define="CustomerReference request/CustomerReference| emptystring"
> value="" tal:attributes="value CustomerReference">
>
>3. I add this to quickpreviewform.zpt or previewform.zpt (Do they have
>to be in both? Guess not, or?)
>Example:
> <tr>
> <td class="strong">Customer Ref:</td>
> <td colspan="3"><input name="CustomerReference"
> size="40" maxlength="70" value="" tal:define="CustomerReference
> request/CustomerReference |emptystring"
>tal:attributes="value CustomerReference"></td>
> </tr>
>
>4. I have to modify ShowIssueData.zpt in oder to see the stuff in the
>"Complete List" and the detailed view. This is what I do:
> <tr tal:define="CustomerReference request/CustomerReference |
> here/CustomerReference"
> tal:condition="python:test(CustomerReference!='')
> and not request.has_key('ChangeIssueAttributes')">
> <td class="strong">Customer Ref.</td>
> <td
> tal:content="CustomerReference">Customer Ref.</td></tr>
>
>So far, so good. When I press the preview-button, I can see what I typed
>in, but I don't see it in the normal view (that follows on saving the
>stuff). It looks to me, that the attribute "CustomerReference" is empty.
>When I change the ShowIssueData.zpt entry to
>
> <tr tal:define="CustomerReference request/CustomerReference |
> here/CustomerReference"
> tal:condition="python:test(CustomerReference=='')
> and not request.has_key('ChangeIssueAttributes')">
> <td class="strong">Customer Ref.</td>
> <td
> tal:content="CustomerReference">Customer Ref.</td></tr>
>
>I.e. when I force him to print empty entries, I see the entry (and it's
>indeed empty).
>Now, this is funny: aren't preview and view using the same zpt file for
>showing the contents, i.e. ShowIssueData.zpt? Or not? In any case: In the
>preview, the entry is definitely non-empty, while in the view, it is
>empty. Or am I mistaken?
>
>
>What am I doing wrong?
>Regards,
>Wolfgang
>
>
>
>-------------------------------------------------------
>This sf.net email is sponsored by:ThinkGeek
>Welcome to geek heaven.
>http://thinkgeek.com/sf
>_______________________________________________
>Issuetracker-development mailing list
>Issuetracker-development@...
>https://lists.sourceforge.net/lists/listinfo/issuetracker-development
|
|
From: Peter Bengtsson <mail@pe...> - 2003-04-30 17:13:01
|
At 08:39 2003-04-10 -0700, Jeremiah Dixon wrote: >Peter requested: > If you're using the mailing list, then write back to >me. ... This anonymous person wrote: >> "You need to describe, in ways >relative Zope newbies can understand, how to add the modules that make >incoming email work. ... That was me. At the time, I had followed your >instructions and had added MailHost at the root of the Zope installation. >Since then, I wiped out that Zope site and created a new one using the >Plone package. Within the basic Zope/Plone installation, I created another >instance of Plone (at the root level) and installed Issue Tracker inside >that Plone folder. Since Plone comes with MailHost pre configured, I don't >even have to think about it. And, sure enough, Issue Tracker works >wonderfully well inside Plone! As I mentioned before, I'm a relative >Zope/Plone newbie. That means that component dependencies, such as >MailHost, aren't "obvious" at all to me. I'm now trying to hook up Issue >Tracker's incoming mail option. Since the Python email module comes with >no installation advice, any tips you can provide on how to make email and >Strip-O-Gram work with Issue Tracker would be greatly appreciated. Thanks >for a great product! Thank you for the feedback. I'll try to make it clearer about the MailHost object since it's apparantly missable. The incoming email stuff was released as soon as the functionality was completed and I didn't wait for myself writing docs. Will come some day. Peter > >Do you Yahoo!? ><http://us.rd.yahoo.com/finance/mailsig/*http://tax.yahoo.com>Yahoo! Tax >Center - File online, calculators, forms, and more |
|
From: Peter Bengtsson <mail@pe...> - 2003-04-30 17:12:03
|
At 11:42 2003-04-15 +0200, Stephan Goeldi wrote: >I would like to let the completed issues disappear from the listings. I >cannot figure out how and where to achieve this. I think it would be a >simple dtml-unless anywhere, wouldn't it? >-- Unfortunatly you'll have to rewrite some templates. Look at zpt/main_tabs.zpt Comment out whatever you'll need to comment out. What you could do is to add a new property to the instance in which you don't want the Complete List tab and add some TAL code to that template. Peter >------------------------------------------------------- >This sf.net email is sponsored by:ThinkGeek >Welcome to geek heaven. >http://thinkgeek.com/sf >_______________________________________________ >Issuetracker-development mailing list >Issuetracker-development@... >https://lists.sourceforge.net/lists/listinfo/issuetracker-development |
|
From: Peter Bengtsson <mail@pe...> - 2003-04-30 17:12:01
|
At 11:40 2003-04-15 +0200, Stephan Goeldi wrote: >What is the safe way to upgrade an issuetracker instance (0.4.9b) to the >latest stable version? The last time I upgraded, it seems that I made it >the wrong way, because the issues were gone and copy and paste didn't >work. You shouldn't need to copy and paste. 1. Just unzip the latest release where appropriate. 2. Refresh the product from the Control Panel 3. Go to the Management tab of the instance(s) you have 4. Press "Deploy and preserve existing" (if you haven't made any changes to the standard objects, press "Complete redeployment") 5. Press "Assert properties" 6. Press "Update catalog" That should do it. Peter >------------------------------------------------------- >This sf.net email is sponsored by:ThinkGeek >Welcome to geek heaven. >http://thinkgeek.com/sf >_______________________________________________ >Issuetracker-development mailing list >Issuetracker-development@... >https://lists.sourceforge.net/lists/listinfo/issuetracker-development |
|
From: Stephan Goeldi <goeldi@go...> - 2003-04-15 09:42:33
|
I would like to let the completed issues disappear from the listings. I cannot figure out how and where to achieve this. I think it would be a simple dtml-unless anywhere, wouldn't it? -- |
|
From: Stephan Goeldi <goeldi@go...> - 2003-04-15 09:40:57
|
What is the safe way to upgrade an issuetracker instance (0.4.9b) to the latest stable version? The last time I upgraded, it seems that I made it the wrong way, because the issues were gone and copy and paste didn't work. |
|
From: Reinelt, Wolfgang; ZFLS-GD ZEMF *
<wolfgang.reinelt@zf...> - 2003-04-14 14:36:46
|
Hi together,
could somebody give me more details on how to create and deal with new
properties? I use IssueTrackerProduct-0.5.0b 0.5.0b (Development)
2003/04/03 100414 bytes from zope.org:
This is what I did so far:
1. create new property in "properties" tab.
Q: is the "value" entry in this tab independent of the variables
in the *.zpt files?
Expample: define a string named "CustomerReference"
2. define this property in submitform.zpt with copy and paste from
another property, depending on if it's just a text field, a selection etc
Example:
<input type="hidden" name="CustomerReference"
tal:define="CustomerReference request/CustomerReference|
emptystring"
value="" tal:attributes="value CustomerReference">
3. I add this to quickpreviewform.zpt or previewform.zpt (Do they have
to be in both? Guess not, or?)
Example:
<tr>
<td class="strong">Customer Ref:</td>
<td colspan="3"><input name="CustomerReference" size="40" maxlength="70"
value="" tal:define="CustomerReference request/CustomerReference
|emptystring"
tal:attributes="value CustomerReference"></td>
</tr>
4. I have to modify ShowIssueData.zpt in oder to see the stuff in the
"Complete List" and the detailed view. This is what I do:
<tr tal:define="CustomerReference request/CustomerReference |
here/CustomerReference"
tal:condition="python:test(CustomerReference!='') and not
request.has_key('ChangeIssueAttributes')">
<td class="strong">Customer Ref.</td>
<td tal:content="CustomerReference">Customer Ref.</td></tr>
So far, so good. When I press the preview-button, I can see what I typed
in, but I don't see it in the normal view (that follows on saving the
stuff). It looks to me, that the attribute "CustomerReference" is empty.
When I change the ShowIssueData.zpt entry to
<tr tal:define="CustomerReference request/CustomerReference |
here/CustomerReference"
tal:condition="python:test(CustomerReference=='') and not
request.has_key('ChangeIssueAttributes')">
<td class="strong">Customer Ref.</td>
<td tal:content="CustomerReference">Customer Ref.</td></tr>
I.e. when I force him to print empty entries, I see the entry (and it's
indeed empty).
Now, this is funny: aren't preview and view using the same zpt file for
showing the contents, i.e. ShowIssueData.zpt? Or not? In any case: In
the preview, the entry is definitely non-empty, while in the view, it is
empty. Or am I mistaken?
What am I doing wrong?
Regards,
Wolfgang
|
|
From: Jeremiah Dixon <jeremiahdixon@ya...> - 2003-04-10 15:39:01
|
Peter requested:> If you're using the mailing list, then write back to me. ... This anonymous person wrote:>> "You need to describe, in ways relative Zope newbies can understand, how to add the modules that make incoming email work. ...That was me. At the time, I had followed your instructions and had added MailHost at the root of the Zope installation.Since then, I wiped out that Zope site and created a new one using the Plone package. Within the basic Zope/Plone installation, I created another instance of Plone (at the root level) and installed Issue Tracker inside that Plone folder. Since Plone comes with MailHost pre configured, I don't even have to think about it. And, sure enough, Issue Tracker works wonderfully well inside Plone!As I mentioned before, I'm a relative Zope/Plone newbie. That means that component dependencies, such as MailHost, aren't "obvious" at all to me.I'm now trying to hook up Issue Tracker's incoming mail option. Since the Python email module comes with no installation advice, any tips you can provide on how to make email and Strip-O-Gram work with Issue Tracker would be greatly appreciated.Thanks for a great product! --------------------------------- Do you Yahoo!? Yahoo! Tax Center - File online, calculators, forms, and more |
|
From: Peter Bengtsson <mail@pe...> - 2003-04-08 11:13:12
|
At 12:17 2003-04-08 +0200, you wrote: >Hi, >is there anybody who has experience in integrating the issue tracking tool >into plone? I haven't. I did investigate a little bit what it would involve and it appears to be quite a take. Are you an expert with Plone and plone product development? >Christian > > > >------------------------------------------------------- >This SF.net email is sponsored by: ValueWeb: >Dedicated Hosting for just $79/mo with 500 GB of bandwidth! >No other company gives more support or power for your dedicated server >http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ >_______________________________________________ >Issuetracker-development mailing list >Issuetracker-development@... >https://lists.sourceforge.net/lists/listinfo/issuetracker-development |
|
From: Zandbergen Christian <Christian.Zandbergen@sw...> - 2003-04-08 10:17:33
|
Hi, is there anybody who has experience in integrating the issue tracking tool into plone? Christian |
|
From: Cigolian<ammasswealth@sa...> - 2003-04-06 07:54:58
|
SWYgWW91IFRSVUxZIE5FRUQuLi4uLi4gJDIsMDAwIHRvICQxMCwwMDAgb3IgTW9yZSANCldpdGhp biBUaGUgTmV4dCA3IERheXMuLi4uIA0KDQpXRSBIQVZFIFRIRSBTT0xVVElPTiEgIA0KDQpObyBT ZWxsaW5nISAgTm8gTUxNIG9yIE5ldHdvcmsgTWFya2V0aW5nISAgTm8gQm9hcmRzIQ0KTm8gTWF0 cml4ISAgTm8gQmluYXJ5ISAgTm8gTW9udGhseSBQdXJjaGFzZXMhDQoNCioqICBOZXchICoqICAg VEhJUyBJUyBOT1RISU5HIFlPVSBIQVZFIFNFRU4gQkVGT1JFIQ0KDQpJVCBJUyBTT01FVEhJTkcg VU5JUVVFTFkgRElGRkVSRU5ULi4uLg0KQW4gRXh0cmVtZWx5IFBvd2VyZnVsIENhc2ggTGV2ZXJh Z2luZyBTeXN0ZW0uLi4NClRoYXQgaXMgY2hhbmdpbmcgdGhlIHdvcmxkIG9uZSBmYW1pbHkgYXQg YSB0aW1lLg0KDQpJZiB5b3UgZmVlbCAkMiwwMDArIFBlciBEYXkgaXMgd29ydGggMiBtaW51dGVz IG9mIHlvdXIgDQp0aW1lLCBJIFdJTEwgTk9UIHRyeSB0byBjb252aW5jZSB5b3Ugb2YgYW55dGhp bmcuICBJJ2xsIG9ubHkNCnBhc3MgdGhlIGluZm9ybWF0aW9uIG9uIHRvIHlvdS4gIA0KDQpPbmx5 IFlPVSBjYW4gZGVjaWRlIGlmIHRoaXMgaXMgZm9yIHlvdS4uLi4NCk9ubHkgWU9VIGNhbiB0YWtl IHRoZSBuZWNlc3Nhcnkgc3RlcHMgdG8gSU1NRURJQVRFTFkNCmFuZCBEUkFNQVRJQ0FMTFkgY2hh bmdlIHlvdXIgZmluYW5jaWFsIGxpZmUhISENCg0KQSBXZWVrIEZyb20gTm93LCBZb3UgQ2FuIEhh dmUgVEhPVVNBTkRTIEluIFlvdXIgSGFuZHMgDQpPUiwgQmUgSnVzdCBBcyBZb3UgQXJlIFRvZGF5 LiAgVEhFIENIT0lDRSBJUyBZT1VSUyENCg0KMyBtaW51dGUgaW5mby4uLi4uLi4uLi4uIGNhbGwg MjEyLTQ2MS04NzY0ICANCllvdSBvd2UgaXQgdG8geW91cnNlbGYgQU5EIHlvdXIgZmFtaWx5IHRv IEFUIExFQVNUIA0KdGFrZSBhIHBlZWsgYXQgdGhpcyEhISAgDQoNCkknbGwgY29udGFjdCB5b3Ug YXMgc29vbiBhcyBJIGhlYXIgZnJvbSB5b3UuICBDYWxsOiBUT0xMIEZSRUUgIDEtODc3LTU3MS00 NTk4 |
|
From: Peter Bengtsson <mail@pe...> - 2003-04-04 22:43:08
|
Just uploaded to CVS:
Bug fixed: Dodgy emails wheren't ignored properly. Now they are.
Bug fixed: "(mail@...) bla bla" was converted to:
"<a href="mailto:(mail@...)">(mail@...)</a> bla bl"
but now that is fixed.
I have now successfully been able to send emails from MS Outlook Express,
Yahoo! Mail and Opera.
All of them except Opera required a fix to the inbound email code.
If you have problems sending emails in, contact me and maybe we can sort it
together.
Thank you Francois Meehan for already doing this. (I'm still waiting to get
my hands on a MS Outlook client I can trash away with)
Peter
|
|
From: Peter Bengtsson <mail@pe...> - 2003-04-04 18:20:52
|
Someone entered a bug in the survey. If you're using the mailinglist, then
write back to me.
This anonymous person wrote:
"You need to describe, in ways relative Zope newbies can understand, how to
add the modules that make incoming email work. Right now, I can run my
little demo of IssueTracker (sitting inside your IssueTrackers folder) and
proceed from Add Issue to Preview First. But when I click Save this issue
now, IE throws a runtime error:
'document.add_issue.subject' is null or not an object
This happens even though I have a subject ("Test Issue") entered in the
Subject box. On the IssueTracker page itself, I see:
Error Type: AttributeError
Error Value: MailHost
So I'm stuck. I'd like to demo this to my peers, but I can't show it to
them until I can enter some data.
Thanks! "
What's obviously the problem is that this person hasn't created a MailHost
object.
Peter
|
|
From: Peter Bengtsson <mail@pe...> - 2003-04-02 16:15:10
|
The stuff I uploaded to CVS yesterday had a bug that prevents you from creating new instances of the IssueTracker. It complains about DEFAULT_ALLOW_DESCRIPTION which was a typo, it should have been DEFAULT_ALLOW_SUBSCRIPTION. This has now been fixed and uploaded. Peter |
|
From: Peter Bengtsson <mail@pe...> - 2003-04-02 14:15:08
|
At 14:00 2003-04-02 +0200, Reinelt, Wolfgang; ZFLS-GD ZEMF wrote: >Hi together, > >I have another one: suppose I have crated new properties fpr my issues: >how do I convince IssueTracker to show these properties when adding a new >issue, listing them etc? Which are the dtml documents that I have to change? Without looking at the code I would guess it's all in zpt/ShowIssueData.zpt That's where the Sections, Urgency and Type is displayed. >Tnx & best regards, >Wolfgang > > > >------------------------------------------------------- >This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just >$79/mo with 500 GB of bandwidth! No other company gives more support or >power for your dedicated server >http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ >_______________________________________________ >Issuetracker-development mailing list >Issuetracker-development@... >https://lists.sourceforge.net/lists/listinfo/issuetracker-development |
|
From: Reinelt, Wolfgang; ZFLS-GD ZEMF
<wolfgang.reinelt@zf...> - 2003-04-02 12:01:00
|
Hi together, I have another one: suppose I have crated new properties fpr my issues: how do I convince IssueTracker to show these properties when adding a new issue, listing them etc? Which are the dtml documents that I have to change? Tnx & best regards, Wolfgang |
|
From: Peter Bengtsson <mail@pe...> - 2003-04-02 01:15:20
|
Dear all,
I have now CVSed up all the new features and fixes. The list of changes is
long.
I truly recommend that if you're using the CVSed version, you get this
latest one (except production status)
Especially if you're using the Inbound email functionality.
Attached is the CHANGES.txt file. Please have a look at it.
The most major things are:
1. Statuses are no longer hardcoded
2. When viewing an issue, at the bottom there is now a quick minimal form
for followups
3. Optionally, all email addresses are encoded to prevent spam-bots.
(default: switched off)
4. Download button and the Confidential & Hide me options are now by
default hidden.
5. Introduced a simple Statistics page for Managers
6. Inbound emails can optionally return confirmation messages
7. Many bug fixes to the inbound email methods that suppresses errors on
dodgy emails (like some spam)
And possible a memory leak fix when fetching lots of emails.
If I now can get some help from you guys with crunching the last bugs I'll
release a version to Zope.org
Best regards, Peter |