issuetracker-development Mailing List for IssueTrackerProduct (Page 18)
Brought to you by:
peterbe
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
|
From: Peter B. <ma...@pe...> - 2003-02-13 00:39:56
|
Just uploaded to CVS: Bug fixed: Searching for name or email was before assumed AND, but now it assumes OR. New feature: File attachements to followups. See Properties tab. Bug fixed: Improved getRoot() even more since last bug fix was not sufficient. Bug fixed: When pressing the Delete button you no longer get a Javascript error. Bug fixed: Improved getRoot() when using Virtual Hosts |
From: Peter B. <ma...@pe...> - 2003-02-07 01:04:51
|
Matthew, Thank you very much for the support. I set up a virtual host monster too and tested and fixed. The getRoot() method relied on a REQUEST URL. Silly. If you're not using CVS, replace the attached file with the one you already have and it should work. Peter PS. Matthew, I strongly suggest that you sign up the mailinglist on http://lists.sourceforge.net/lists/listinfo/issuetracker-development At 16:52 2003-02-06 -0500, Matthew Wilbert wrote: >Peter, > >Thanks for looking into this. > >I think the message provided most of the information. This is just >ZServer running >without Apache or anything else in front of it. I am using the mapping >tab of the VirtualHostMonster to remap the URL from: > >http://netmanager.env.state.ma.us/help > >to > >http://help.env.state.ma.us > >so the mapping table entry looks like > >help.env.state.ma.us/help > >Both the IssueTracker instance and the HostMonster are in the root >folder. > >If you want any additional information, let me know, and thanks again, >both >for the IssueTracker product and for your help. > >Matt >----------------- > >In Thu, 06 Feb 2003 00:57:37 +0000, "Peter Bengtsson" <ma...@pe...> >said: > > Thank you Matt, > > > > I can only guess what the problem is. I've set up a VirtualHost so that I > > can test it and fix it. > > The VirtualHost will take some time to take affect so it will have to > > wait > > until tomorrow (or some other day soon). > > > > Can you please tell me how you did the actual config? Apache? OS? Monster > > settings? > > > > Peter > > > > At 17:00 2003-02-04 -0500, Matthew Wilbert wrote: > > >I have IssueTracker (v.49b) installed in the root folder /help. > > >I have a VirtualHostMonster set up to map a second host name "help" to > > >/help. (using the > > >Mappings tab) This is running under Zope 2.6.1b. > > > > > >If I try to access IssueTracker through the normal url with a /help at > > >the end, it works fine. > > > > > >If I try to access it through the mapped URL, it works, in the sense the > > >the IssueTracker home page comes up when I use the help url, but if I try > > >to look at an actual issue, I get the traceback at the end of this > > >message. > > > > > >Is it a known thing that using virtual hosts breaks some products? Is > > >there a standard workaround? > > > > > >Thanks, > > > > > >Matt Wilbert > > >-----------------------TRACEBACK---------------------------- > > >Module ZPublisher.Publish, line 150, in publish_module > > >Module ZPublisher.Publish, line 114, in publish > > >Module Zope.App.startup, line 182, in zpublisher_exception_hook > > >Module ZPublisher.Publish, line 98, in publish > > >Module ZPublisher.mapply, line 88, in mapply > > >Module ZPublisher.Publish, line 39, in call_object > > >Module Products.IssueTrackerProduct.IssueTracker, line 2323, in > > >index_html > > >Module Shared.DC.Scripts.Bindings, line 252, in __call__ > > >Module Shared.DC.Scripts.Bindings, line 283, in _bindAndExec > > >Module Products.PageTemplates.PageTemplateFile, line 96, in _exec > > >Module Products.PageTemplates.PageTemplate, line 95, in pt_render > > ><PageTemplateFile at /help/Issue0022/> > > >Module TAL.TALInterpreter, line 200, in __call__ > > >Module TAL.TALInterpreter, line 244, in interpret > > >Module TAL.TALInterpreter, line 703, in do_useMacro > > >Module TAL.TALInterpreter, line 244, in interpret > > >Module TAL.TALInterpreter, line 477, in do_setGlobal_tal > > >Module Products.PageTemplates.TALES, line 217, in evaluate > > >URL: StandardLook > > >Line 5, Column 4 > > >Expression: <PythonExpr here.getRoot().title_or_id()> > > >Names: > > >{'container': <IssueTrackerIssue instance at 8d59798>, > > > 'default': <Products.PageTemplates.TALES.Default instance at 0x8947484>, > > > 'here': <IssueTrackerIssue instance at 8d59798>, > > > 'loop': <SafeMapping instance at 8bc9748>, > > > 'modules': <Products.PageTemplates.ZRPythonExpr._SecureModuleImporter > > > instance at 0x891f3f4>, > > > 'nothing': None, > > > 'options': {'args': ()}, > > > 'repeat': <SafeMapping instance at 8bc9748>, > > > 'request': <HTTPRequest, > > > URL=http://help.env.state.ma.us/Issue0022/index_html>, > > > 'root': <Application instance at 8b16bb8>, > > > 'template': <PageTemplateFile at /help/Issue0022/>, > > > 'traverse_subpath': [], > > > 'user': Anonymous User}Module Products.PageTemplates.ZRPythonExpr, line > > > 48, in __call__ > > >__traceback_info__: here.getRoot().title_or_id() > > >Module Python expression "here.getRoot().title_or_id()", line 2, in f > > >AttributeError: 'None' object has no attribute 'title_or_id' (Also, an > > >error occurred while attempting to render the standard error message.) > > > > > >_______________________________________________ > > >Zope maillist - Zo...@zo... > > >http://mail.zope.org/mailman/listinfo/zope > > >** No cross posts or HTML encoding! ** > > >(Related lists - > > > http://mail.zope.org/mailman/listinfo/zope-announce > > > http://mail.zope.org/mailman/listinfo/zope-dev ) > > > > |
From: Peter B. <ma...@pe...> - 2003-02-06 01:13:43
|
Just uploaded to CVS: Bug fixed: When pressing 'Save Changes' in the Properties tab the page was returned completely blank. Now it "redirects" back to the Properties tab as expected. Bug fixed: ShowIssueData and the 'change these attributes' action link was misspelled. Now fixed. |
From: Peter B. <ma...@pe...> - 2003-02-06 01:13:43
|
Thank you Matt, I can only guess what the problem is. I've set up a VirtualHost so that I can test it and fix it. The VirtualHost will take some time to take affect so it will have to wait until tomorrow (or some other day soon). Can you please tell me how you did the actual config? Apache? OS? Monster settings? Peter At 17:00 2003-02-04 -0500, Matthew Wilbert wrote: >I have IssueTracker (v.49b) installed in the root folder /help. >I have a VirtualHostMonster set up to map a second host name "help" to >/help. (using the >Mappings tab) This is running under Zope 2.6.1b. > >If I try to access IssueTracker through the normal url with a /help at >the end, it works fine. > >If I try to access it through the mapped URL, it works, in the sense the >the IssueTracker home page comes up when I use the help url, but if I try >to look at an actual issue, I get the traceback at the end of this >message. > >Is it a known thing that using virtual hosts breaks some products? Is >there a standard workaround? > >Thanks, > >Matt Wilbert >-----------------------TRACEBACK---------------------------- >Module ZPublisher.Publish, line 150, in publish_module >Module ZPublisher.Publish, line 114, in publish >Module Zope.App.startup, line 182, in zpublisher_exception_hook >Module ZPublisher.Publish, line 98, in publish >Module ZPublisher.mapply, line 88, in mapply >Module ZPublisher.Publish, line 39, in call_object >Module Products.IssueTrackerProduct.IssueTracker, line 2323, in >index_html >Module Shared.DC.Scripts.Bindings, line 252, in __call__ >Module Shared.DC.Scripts.Bindings, line 283, in _bindAndExec >Module Products.PageTemplates.PageTemplateFile, line 96, in _exec >Module Products.PageTemplates.PageTemplate, line 95, in pt_render ><PageTemplateFile at /help/Issue0022/> >Module TAL.TALInterpreter, line 200, in __call__ >Module TAL.TALInterpreter, line 244, in interpret >Module TAL.TALInterpreter, line 703, in do_useMacro >Module TAL.TALInterpreter, line 244, in interpret >Module TAL.TALInterpreter, line 477, in do_setGlobal_tal >Module Products.PageTemplates.TALES, line 217, in evaluate >URL: StandardLook >Line 5, Column 4 >Expression: <PythonExpr here.getRoot().title_or_id()> >Names: >{'container': <IssueTrackerIssue instance at 8d59798>, > 'default': <Products.PageTemplates.TALES.Default instance at 0x8947484>, > 'here': <IssueTrackerIssue instance at 8d59798>, > 'loop': <SafeMapping instance at 8bc9748>, > 'modules': <Products.PageTemplates.ZRPythonExpr._SecureModuleImporter > instance at 0x891f3f4>, > 'nothing': None, > 'options': {'args': ()}, > 'repeat': <SafeMapping instance at 8bc9748>, > 'request': <HTTPRequest, > URL=http://help.env.state.ma.us/Issue0022/index_html>, > 'root': <Application instance at 8b16bb8>, > 'template': <PageTemplateFile at /help/Issue0022/>, > 'traverse_subpath': [], > 'user': Anonymous User}Module Products.PageTemplates.ZRPythonExpr, line > 48, in __call__ >__traceback_info__: here.getRoot().title_or_id() >Module Python expression "here.getRoot().title_or_id()", line 2, in f >AttributeError: 'None' object has no attribute 'title_or_id' (Also, an >error occurred while attempting to render the standard error message.) > >_______________________________________________ >Zope maillist - Zo...@zo... >http://mail.zope.org/mailman/listinfo/zope >** No cross posts or HTML encoding! ** >(Related lists - > http://mail.zope.org/mailman/listinfo/zope-announce > http://mail.zope.org/mailman/listinfo/zope-dev ) |
From: Robert A. <rallyn@AllynConsulting.com> - 2003-02-03 23:40:54
|
That fixed it. - Robert At 10:51 PM 2/3/2003 +0000, Peter Bengtsson wrote: >At 11:55 2003-02-03 -0800, Robert Allyn wrote: >>When I select a single IssueTracker instance to view from the list at the top and click Save I get: >> >>Error Type: NameError >>Error Value: global name 'context' is not defined > >Oops. >My fault. > >Have updated the CVS but no new release on sourceforge. >For those not using CVS, see the attached file. Just replace your existing one called MassContainer.py > >Peter > > > >>Minor- Issue tracker notifiable container icon is missing/not showing. Might be just my install. >> >>- Robert >> >>At 01:32 AM 1/31/2003 +0000, Peter Bengtsson wrote: >>>To all administrators or the IssueTrackerProduct. >>> >>>Remember the IssueTrackers general masscontainer? >>>http://www.zope.org/Members/peterbe/IssueTrackerProduct/issuetrackers_masscontainer_first_release >>>http://www.zope.org/Members/peterbe/IssueTrackerProduct/issuetrackers.zexp/view >>> >>>Now I've put this together as a proper python product instead. >>>It's called IssueTrackerMassContainer and has only been released on SourceForge yet. >>> >>>Download it from >>>http://sourceforge.net/project/showfiles.php?group_id=60145 >>>Or from these CVS commands >>>$ cvs -d:pserver:ano...@cv...:/cvsroot/issuetracker login >>>[when asked for password, press ENTER] >>>$ cvs -z3 -d:pserver:ano...@cv...:/cvsroot/issuetracker co IssueTrackerMassContainer >>> >>>If you don't already use the folder 'issuetrackers', just install it and create an instance of it. Then create all your issue tracker instance inside this object. >>> >>>If you already have a folder with lots of issuetracker instances, install the product, create an instance and copy all the instances from the old folder to this new object. >>>HOWEVER, because you're copying ZCatalogs the references within them are incorrect. You'll need to do a UpdateCatalog. >>>For this to be efficient, you must download the latest CVS version of IssueTrackerProduct like this >>> >>>$ cvs -d:pserver:ano...@cv...:/cvsroot/issuetracker login >>>[when asked for password, press ENTER] >>>$ cvs -z3 -d:pserver:ano...@cv...:/cvsroot/issuetracker co IssueTrackerProduct >>> >>>This latest version (not yet released) has a much improved UpdateCatalog() method. >>> >>>Then use the 'automate' python script that was created in the new mass container object to go through the UpdateCatalog() method for each instance. >>> >>> >>>I would very much like to have some functional feedback on this before I release it to Zope.org >>>Does it work? >>>Feedback? >>> >>>Peter >>> >>> >>> >>> >>> >>> >>> >>>------------------------------------------------------- >>>This SF.NET email is sponsored by: >>>SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! >>>http://www.vasoftware.com >>>_______________________________________________ >>>Issuetracker-development mailing list >>>Iss...@li... >>>https://lists.sourceforge.net/lists/listinfo/issuetracker-development >> >>---------------------------------------------- >>Robert Allyn >> Voice (206)706-7063 Fax (206)783-7795 >> ra...@al... ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ Issuetracker-development mailing list Iss...@li... https://lists.sourceforge.net/lists/listinfo/issuetracker-development > > ---------------------------------------------- Robert Allyn Voice (206)706-7063 Fax (206)783-7795 ra...@al... |
From: Peter B. <ma...@pe...> - 2003-02-03 22:53:53
|
At 11:55 2003-02-03 -0800, Robert Allyn wrote: >When I select a single IssueTracker instance to view from the list at the >top and click Save I get: > >Error Type: NameError >Error Value: global name 'context' is not defined Oops. My fault. Have updated the CVS but no new release on sourceforge. For those not using CVS, see the attached file. Just replace your existing one called MassContainer.py Peter >Minor- Issue tracker notifiable container icon is missing/not >showing. Might be just my install. > >- Robert > >At 01:32 AM 1/31/2003 +0000, Peter Bengtsson wrote: >>To all administrators or the IssueTrackerProduct. >> >>Remember the IssueTrackers general masscontainer? >>http://www.zope.org/Members/peterbe/IssueTrackerProduct/issuetrackers_masscontainer_first_release >>http://www.zope.org/Members/peterbe/IssueTrackerProduct/issuetrackers.zexp/view >> >>Now I've put this together as a proper python product instead. >>It's called IssueTrackerMassContainer and has only been released on >>SourceForge yet. >> >>Download it from >>http://sourceforge.net/project/showfiles.php?group_id=60145 >>Or from these CVS commands >>$ cvs -d:pserver:ano...@cv...:/cvsroot/issuetracker login >>[when asked for password, press ENTER] >>$ cvs -z3 -d:pserver:ano...@cv...:/cvsroot/issuetracker >>co IssueTrackerMassContainer >> >>If you don't already use the folder 'issuetrackers', just install it and >>create an instance of it. Then create all your issue tracker instance >>inside this object. >> >>If you already have a folder with lots of issuetracker instances, install >>the product, create an instance and copy all the instances from the old >>folder to this new object. >>HOWEVER, because you're copying ZCatalogs the references within them are >>incorrect. You'll need to do a UpdateCatalog. >>For this to be efficient, you must download the latest CVS version of >>IssueTrackerProduct like this >> >>$ cvs -d:pserver:ano...@cv...:/cvsroot/issuetracker login >>[when asked for password, press ENTER] >>$ cvs -z3 -d:pserver:ano...@cv...:/cvsroot/issuetracker >>co IssueTrackerProduct >> >>This latest version (not yet released) has a much improved >>UpdateCatalog() method. >> >>Then use the 'automate' python script that was created in the new mass >>container object to go through the UpdateCatalog() method for each instance. >> >> >>I would very much like to have some functional feedback on this before I >>release it to Zope.org >>Does it work? >>Feedback? >> >>Peter >> >> >> >> >> >> >> >>------------------------------------------------------- >>This SF.NET email is sponsored by: >>SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! >>http://www.vasoftware.com >>_______________________________________________ >>Issuetracker-development mailing list >>Iss...@li... >>https://lists.sourceforge.net/lists/listinfo/issuetracker-development > >---------------------------------------------- >Robert Allyn > Voice (206)706-7063 Fax (206)783-7795 > ra...@al... > ------------------------------------------------------- This SF.NET email > is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = > Something 2 See! http://www.vasoftware.com > _______________________________________________ Issuetracker-development > mailing list Iss...@li... > https://lists.sourceforge.net/lists/listinfo/issuetracker-development |
From: Robert A. <rallyn@AllynConsulting.com> - 2003-02-03 19:55:47
|
<html> <body> When I select a single IssueTracker instance to view from the list at the top and click Save I get:<br><br> <b>Error Type: NameError<br> Error Value: global name 'context' is not defined<br><br> <br> </b>Minor- Issue tracker notifiable container icon is missing/not showing. Might be just my install.<br><br> - Robert<br><br> At 01:32 AM 1/31/2003 +0000, Peter Bengtsson wrote:<br> <blockquote type=cite class=cite cite>To all administrators or the IssueTrackerProduct.<br><br> Remember the IssueTrackers general masscontainer?<br> <a href="http://www.zope.org/Members/peterbe/IssueTrackerProduct/issuetrackers_masscontainer_first_release" eudora="autourl">http://www.zope.org/Members/peterbe/IssueTrackerProduct/issuetrackers_masscontainer_first_release</a><br> <a href="http://www.zope.org/Members/peterbe/IssueTrackerProduct/issuetrackers.zexp/view" eudora="autourl">http://www.zope.org/Members/peterbe/IssueTrackerProduct/issuetrackers.zexp/view</a><br><br> Now I've put this together as a proper python product instead.<br> It's called IssueTrackerMassContainer and has only been released on SourceForge yet.<br><br> Download it from<br> <a href="http://sourceforge.net/project/showfiles.php?group_id=60145" eudora="autourl">http://sourceforge.net/project/showfiles.php?group_id=60145</a><br> Or from these CVS commands<br> $ cvs -d:pserver:ano...@cv...:/cvsroot/issuetracker login<br> [when asked for password, press ENTER]<br> $ cvs -z3 -d:pserver:ano...@cv...:/cvsroot/issuetracker co IssueTrackerMassContainer<br><br> If you don't already use the folder 'issuetrackers', just install it and create an instance of it. Then create all your issue tracker instance inside this object.<br><br> If you already have a folder with lots of issuetracker instances, install the product, create an instance and copy all the instances from the old folder to this new object.<br> HOWEVER, because you're copying ZCatalogs the references within them are incorrect. You'll need to do a UpdateCatalog.<br> For this to be efficient, you must download the latest CVS version of IssueTrackerProduct like this<br><br> $ cvs -d:pserver:ano...@cv...:/cvsroot/issuetracker login<br> [when asked for password, press ENTER]<br> $ cvs -z3 -d:pserver:ano...@cv...:/cvsroot/issuetracker co IssueTrackerProduct<br><br> This latest version (not yet released) has a much improved UpdateCatalog() method.<br><br> Then use the 'automate' python script that was created in the new mass container object to go through the UpdateCatalog() method for each instance.<br><br> <br> I would very much like to have some functional feedback on this before I release it to Zope.org<br> Does it work?<br> Feedback?<br><br> Peter<br><br> <br><br> <br><br> <br><br> -------------------------------------------------------<br> This SF.NET email is sponsored by:<br> SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!<br> <a href="http://www.vasoftware.com/" eudora="autourl">http://www.vasoftware.com</a><br> _______________________________________________<br> Issuetracker-development mailing list<br> Iss...@li...<br> <a href="https://lists.sourceforge.net/lists/listinfo/issuetracker-development" eudora="autourl">https://lists.sourceforge.net/lists/listinfo/issuetracker-development</a><br> </blockquote> <x-sigsep><p></x-sigsep> ----------------------------------------------<br> Robert Allyn<br> Voice (206)706-7063 Fax (206)783-7795<br> ra...@al...</body> </html> |
From: Peter B. <ma...@pe...> - 2003-02-03 04:28:19
|
First of all:: I send out this message to the issuetracker mailinglist and to all people who have shown interest in the IssueTrackerProduct via email. If I've double-emailed you or you do not want to get any more emails from me about the IssueTracker I sincerely appologise and you can tell me so. Prolog:: Judging from the results of the survey I have, and still am, conducted a lot of people seem to want to be able to use more advanced teamwork features. Mainly it's to be able to assign things to people and add a few more permission layers of authenticated people and what they can do. Sure I say! But these are the conditions: 1. These features will be by default switched off 2. One must be able to swich back and forth between these features without breaking anything 3. Authentication must be basic Zope authentication, with the option of Remember Me Below these different new features (NF) are discussed. Please chip in with feedback. No deadlines are yet promised. NF1:- store log of how issues change status:: Something like this [{'status':'open', 'changedate':ZopeTime('2003-01-30'), 'actor':'peterbe'}, {'status':'completed', 'changedate':ZopeTime('2003-02-11'), 'actor':'Some Stranger <str...@ho...>'}, ...] This way, one could inspect the historical development of an issue. and measure the time between two changes. NF2:- assignees/stored users Assignees will basically be a set of different Zope Roles (great, then we can use acquisition!). To be able to integrate this seamlessly without breaking anything I intend not to use the builtin security mechanisms. Rather I'd just use that as a storage base. ACL users do not have any other information than userid and password but the email address is important, therefore I suggest a matching property that can look this this:: {'peterbe':{'email':'ma...@pe...', 'name':'Peter'}, 'fred':{'email':'fre...@as...', 'name':'Fred Blogs'}, ...} It's expected to be unlikely that an ACL user is not associated with an email address. Most likely this will happen when a zope Manager Views the issue tracker. Tough luck I say, then we can fall back on cookies like it is today. I will define a bunch of Roles for all instances. What about these:: - Manager Can do everything outside the ZMI. (this role the real Zope Manager will be assumed to take) Access to certain statistical conclusions. - Worker Can do everything except Deleteing and Changing already defined issue attributes. - Client Just like Zope Anonymous works today. Setting these up will create special objects. That way, if you decide, you can call a Manager "Project Manager" or "Boss" instead if that suits your environment better. Suggestions will be available when you create them. I would like to be able to have this completely up to the administrator of the issue tracker but I'd both provide suggestions and some pre-created ones. The Remember Me would require that you store a cookie with the user, and do an automatic Basic Authentication login. What about register/signing up? Should only Zope administrators be able to control this? Or should it be possible for a say Managers to create registration templates for people who have not yet signed up? The note NF1 above can be used to conclude whether certain assignees can do certain things to issues. I.e. if you're only a "Worker" you should only be able to Complete- or Delete- or both issues that you yourself created. NF3:- due dates:: Will obviously require a cronjob attached to the issue tracker. Don't like this idea but it has to be so, maybe I can nick code from the Xron Method Product to make the issue tracker product non-dependable. When you add an issue you're supposed to be able to select a date when an issues must reach a certain status, and optionally for whom. I.e. this issue should be completed by John by the 11th of June. This requires a calendar widget of some kind. I suggest a javascript calendar which pops up with an input field. Code can be nicked from the Calendar Tag or CMFCalendar/CMFPlone. (Maybe somebody can help me extract the appropriate code from CMFPlone for me?) Another thing. What do I call this new feature project? I'd like to be see this particular word as a Tab in the ZMI. Suggestions:: - Teamwork - Team - People - Users - Advanced Permissions - Collaboration - - Best regards, Peter |
From: Peter B. <ma...@pe...> - 2003-01-31 02:00:38
|
Just uploaded to CVS: Bug fixed: UpdateCatalog() now clears the catalog before it reindexes all objects. New feature: added showURL2Issue() which concatenates too long URLs in ShowIssueData. |
From: Peter B. <ma...@pe...> - 2003-01-31 02:00:38
|
To all administrators or the IssueTrackerProduct. Remember the IssueTrackers general masscontainer? http://www.zope.org/Members/peterbe/IssueTrackerProduct/issuetrackers_masscontainer_first_release http://www.zope.org/Members/peterbe/IssueTrackerProduct/issuetrackers.zexp/view Now I've put this together as a proper python product instead. It's called IssueTrackerMassContainer and has only been released on SourceForge yet. Download it from http://sourceforge.net/project/showfiles.php?group_id=60145 Or from these CVS commands $ cvs -d:pserver:ano...@cv...:/cvsroot/issuetracker login [when asked for password, press ENTER] $ cvs -z3 -d:pserver:ano...@cv...:/cvsroot/issuetracker co IssueTrackerMassContainer If you don't already use the folder 'issuetrackers', just install it and create an instance of it. Then create all your issue tracker instance inside this object. If you already have a folder with lots of issuetracker instances, install the product, create an instance and copy all the instances from the old folder to this new object. HOWEVER, because you're copying ZCatalogs the references within them are incorrect. You'll need to do a UpdateCatalog. For this to be efficient, you must download the latest CVS version of IssueTrackerProduct like this $ cvs -d:pserver:ano...@cv...:/cvsroot/issuetracker login [when asked for password, press ENTER] $ cvs -z3 -d:pserver:ano...@cv...:/cvsroot/issuetracker co IssueTrackerProduct This latest version (not yet released) has a much improved UpdateCatalog() method. Then use the 'automate' python script that was created in the new mass container object to go through the UpdateCatalog() method for each instance. I would very much like to have some functional feedback on this before I release it to Zope.org Does it work? Feedback? Peter |
From: Peter B. <ma...@pe...> - 2003-01-30 18:00:54
|
At 07:24 2003-01-30 -0800, Robert Allyn wrote: >I think links in plain text are fine, and useful. I am trying to think of >when that would be a problem. What am I missing? I agree. Couldn't really figure out when it would be a problem. However, if it says plain text then maybe it should be plain text. Will leave it the way it is then for the moment. Peter >- Robert > >At 02:40 PM 1/30/2003 +0000, Peter Bengtsson wrote: > >When submitting an issue you can either have plain text or structured text. > >At the moment with both of them hyperlink-look-a-like-text is converted > to hyperlinks. > >Maybe this shouldn't happen on plain text. > >What do you think? > > > >Peter > > > > > > > >------------------------------------------------------- > >This SF.NET email is sponsored by: > >SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! > >http://www.vasoftware.com > >_______________________________________________ > >Issuetracker-development mailing list > >Iss...@li... > >https://lists.sourceforge.net/lists/listinfo/issuetracker-development > >---------------------------------------------- >Robert Allyn > Voice (206)706-7063 Fax (206)783-7795 > ra...@al... > > > >------------------------------------------------------- >This SF.NET email is sponsored by: >SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! >http://www.vasoftware.com >_______________________________________________ >Issuetracker-development mailing list >Iss...@li... >https://lists.sourceforge.net/lists/listinfo/issuetracker-development |
From: Robert A. <rallyn@AllynConsulting.com> - 2003-01-30 15:25:48
|
I think links in plain text are fine, and useful. I am trying to think of when that would be a problem. What am I missing? - Robert At 02:40 PM 1/30/2003 +0000, Peter Bengtsson wrote: >When submitting an issue you can either have plain text or structured text. >At the moment with both of them hyperlink-look-a-like-text is converted to hyperlinks. >Maybe this shouldn't happen on plain text. >What do you think? > >Peter > > > >------------------------------------------------------- >This SF.NET email is sponsored by: >SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! >http://www.vasoftware.com >_______________________________________________ >Issuetracker-development mailing list >Iss...@li... >https://lists.sourceforge.net/lists/listinfo/issuetracker-development ---------------------------------------------- Robert Allyn Voice (206)706-7063 Fax (206)783-7795 ra...@al... |
From: Peter B. <ma...@pe...> - 2003-01-30 15:00:37
|
When submitting an issue you can either have plain text or structured text. At the moment with both of them hyperlink-look-a-like-text is converted to hyperlinks. Maybe this shouldn't happen on plain text. What do you think? Peter |
From: Peter B. <ma...@pe...> - 2003-01-24 01:05:32
|
I've recently (too) understood the power of Plone. Now it's time we develop whatever needs to be developed so that you can run the Issue Tracker Product in Plone. Who knows a lot about this? Products that do the same? Things to think about? Are there any other obvious integrations worthy to consider? Peter |
From: Peter B. <ma...@pe...> - 2003-01-24 00:33:57
|
Just uploaded to CVS: Bug fixed: Search highlight does now not mess with tags. Try searching for 'strong' or 'p'. Before it looked odd. Bug fixed: Latest issues on homepage is now latest issues. Before it used cookie sortorders. |
From: Peter B. <ma...@pe...> - 2003-01-23 01:18:45
|
I'm happy to anncounce IssueTrackerProduct 0.4.9b See the announcement on http://www.zope.org/Members/peterbe/IssueTrackerProduct/IssueTrackerProduct-0.4.9b_release Main new features: * ZCatalog searchable in Zope2.6.1b1 * CompleteList * Comments and file attachments searchable * Improved batchlinks * The Properties Wizard (see Properties tab) * Filter Options hidden * Sortorder remembered * No cache * 'Allow issue attribute change' (see Properties tab) * Replace Email (see Management tab) And lots of bug fixes. The announcement also mentions the IssueTrackerSurvey at http://survey.issuetracker.peterbe.com Please have a look at that too. Regards, Peter |
From: Robert A. <rallyn@AllynConsulting.com> - 2003-01-22 00:47:38
|
The "Issues Apparantly Interesting For Me" would be of interest. I could see a direct use of this. The XML and news feeds are of little use to me at this time, but sound interesting. Notes inline: At 11:16 PM 1/21/2003 +0000, Peter Bengtsson wrote: >:: Issues Apparantly Interesting For Me :: > >Interface:: > >I don't know yet where exactly to put this link/button, but let's call it a link for now. >"Show me all issues I've been asked to have a look at" > > >Function:: > >This would list unique issues (sorted by when each tell-a-friend was applied) where my email address has been passed through the Tell-a-friend feature. >Maybe even return two lists: > one with those I haven't got involved in > one with those I have got involved in > Both options would be great. >Technical:: > >Technically it's possible by introducing a variable to all issues that looks something like this: > >[ {'when':ZopeTime('2003/01/21'), > 'fromemail':'pe...@gr...', > 'toemail':['jo...@se...', 'fo...@ba...'], > 'msgsent':"""Hey fellas\n have a look at this issue please""" >,....] > >Or, how about storing if jo...@se... or fo...@ba... has looked at the issue? By modifing this issues property like this: > >[ {'when':ZopeTime('2003/01/21'), > 'fromemail':'pe...@gr...', > 'toemail':['jo...@se...', 'fo...@ba...'], > 'msgsent':"""Hey fellas\n have a look at this issue please""", > 'viewed':['fo...@ba...'] >,....] > > >Considerations:: > >No security restrictions. I.e. if you trick about you can see which issues so...@el... were asked to have a look at. Not a big deal here >No cookies nor sessions needed >What should happen if someone insists on the tell-a-friend and asks a buddy to visit an issue for a second time? And maybe this second time to different receipiants and a different msg. Hmmmm.. I was first thinking the message didn't matter as long as you knew you were supposed to look at it. I can see that the message would be useful to determine why someone asked you to look at the issue. Not sure how best to handle this. >So, can you please give me some feedback on this? >At least if you like the idea or not. Will it cloak the interface and make it confusing? > ---------------------------------------------- Robert Allyn Voice (206)706-7063 Fax (206)783-7795 ra...@al... |
From: Peter B. <ma...@pe...> - 2003-01-21 23:20:18
|
Almost all features of the issue tracker product come from you guys. The real users. I seldomly add features just because they can be cool to have. However this is something I came up with myself, and I'm a user too aren't I? :: Issues Apparantly Interesting For Me :: Interface:: I don't know yet where exactly to put this link/button, but let's call it a link for now. "Show me all issues I've been asked to have a look at" Function:: This would list unique issues (sorted by when each tell-a-friend was applied) where my email address has been passed through the Tell-a-friend feature. Maybe even return two lists: one with those I haven't got involved in one with those I have got involved in Technical:: Technically it's possible by introducing a variable to all issues that looks something like this: [ {'when':ZopeTime('2003/01/21'), 'fromemail':'pe...@gr...', 'toemail':['jo...@se...', 'fo...@ba...'], 'msgsent':"""Hey fellas\n have a look at this issue please""" ,....] Or, how about storing if jo...@se... or fo...@ba... has looked at the issue? By modifing this issues property like this: [ {'when':ZopeTime('2003/01/21'), 'fromemail':'pe...@gr...', 'toemail':['jo...@se...', 'fo...@ba...'], 'msgsent':"""Hey fellas\n have a look at this issue please""", 'viewed':['fo...@ba...'] ,....] Considerations:: No security restrictions. I.e. if you trick about you can see which issues so...@el... were asked to have a look at. No cookies nor sessions needed What should happen if someone insists on the tell-a-friend and asks a buddy to visit an issue for a second time? And maybe this second time to different receipiants and a different msg. So, can you please give me some feedback on this? At least if you like the idea or not. Will it cloak the interface and make it confusing? :: RSS/RDP/XML feeds :: Interface: None that you can see. _Maybe_ as very small links in the footer. Function: Several XML feeds. RSS 0.91, RSS 0.92, RSS 2.0, RDF using default batchsizes and sorts by creationdate (or changedate). Maybe even my very own XML feed where I can choose the nodes myself. (feedback on this?) Something like ListIssues.xml and CompleteList.xml Technical: I'll have to look at each spec of feeds to see what features I can include. I have already developed the RSS 0.91 for testing purposes. Looks nice in effbot.exe but lacks some functionality. One would reach them by the URL like http://server.com/mytracker/rss-0.91.xml Considerations: Creating the XML is trivial. But what about when an issue is updated by a comment? Should that be an entry? The vanilla XML feed should obviously not have batching and should include all information possible. Or? Should I only focus on a few to prevent confusion? Like RSS 0.91 and XML only. Should it maybe have cache settings since they are looked at "anonymously". Phew! Long email considering that I should be studying for my exams in software engineering instead of actually doing software enginerring :) Peter |
From: Peter B. <ma...@pe...> - 2003-01-09 03:20:19
|
Please see these new News about the Issue Tracker Caching https://sourceforge.net/forum/forum.php?forum_id=242160 Changing issue properties after created https://sourceforge.net/forum/forum.php?forum_id=242159 |
From: Lewie K. <lew...@ec...> - 2003-01-03 16:48:10
|
I got issuetracker downloaded and installed. It showed up in my product folder but isn't in list of objects to choose from. Do I have to do something else. Thanks Lewie |
From: Lewie K. <lew...@ec...> - 2003-01-03 00:14:47
|
I loaded it up on a linux machine. It showed up fine in the products folder in the control panel but nothing additional is listed for selection. in my folders? Any Ideas Thanks Lewie |
From: Lewie K. <lew...@ec...> - 2003-01-02 17:35:13
|
I downloaded and installed issuetracker but it didn't add an object into my list???? Thanks Lewie |
From: Lewie K. <lew...@ec...> - 2002-12-31 23:58:27
|
I downloaded issuetracker but i couldn't gunzip it? are there some installation instructions? Thank you Lewie |
From: Peter B. <ma...@pe...> - 2002-09-24 13:49:27
|
In CVS I have now uploaded the latest changes to enable file attachments and nicer URLs. Visit to see this in action. http://fry-it.com:8088/test/dummy/ On this page no_fileattachments is set to 3. 0 would turn the feature off. In List Issues, click to sort on Urgency twice and you'll notice the much nicer URL. Cachability was the main concern here. Peter |
From: Peter B. <ma...@pe...> - 2002-09-19 19:44:33
|
What do you all think about Rogers feature request posted on https://sourceforge.net/tracker/index.php?func=detail&aid=611658&group_id=60145&atid=493216 Thanks for your input. Remember that not all features are beneficial if they compensate usability and raise the level of complexity too much. Peter |