Bug 1 is a web2py bug, not an issue tracker bug, and it is fixed in trunk.
On Oct 4, 9:10 pm, Tsize <tsiz...@gmail.com> wrote: > On Oct 4, 2:29 pm, petrasadi <petras...@gmail.com> wrote: > > > I am currently working on a project meant to improve the current > > Web2Py Issue Tracking System. > > Are there any features that could use touch-ups or new features that > > should be implemented? > > Looking forward to your suggestions. > > I assume your are referring to the recently posted issue tracking > app. I have found one bug and a have a couple of other smaller > requests. > > Bug > > 1. When I entered multiple projects with multiple issues each I had a > problem with the export to csv function. From the main page if I use > this it gives me a listing of projects but no other data or options > (say just open items or items closed in a given time frame). If I > request a csv be exported from within a project the csv is empty which > is a defect to me. I want to be able to specify the exported csv > provide only select data at all levels. > > Wishes > > 1. Some comments were made about being able to pull over web2py > projects automatically. While this is OK I work as an electrical > engineer and only a few of my issues are program related. I would > like to be able to use this both for my web2py project as well as for > a general issue tracker. > > 2. Like quite a few people using an issue tracker I will need to > start with the program as released and then make a couple of > modifications. In my case I will need to add a couple more fields > that will be used to help with tracking my projects and setting > priorities. Documentation released with this program covering common > modifications would be nice. I actually need something similar to the > roundup default interface. > > If I think of anything else over the next couple of days I will add > some more comments. > > Best regards, > Thomas > > 3.
