I am pretty sure those things are pretty easy to implement... Why not just add them in the issue on google code and if someone has time he could just work on it.
Massimo can't support all the app he create to show us the way to go and ask for poeple to take "paternity" of project to make sure they stay usable with the new versions of web2py. Also, I try i-Tracker, it much more usable I admit, but there a couples of things that I don't like. 1) sometimes the UI is not pretty easy to understand, 2) it not use the RBAC, so can't just export/import in csv my user from one db to the other, 3) search don't seems to work, 4) it not up to date in order to take advantage of the web2py new feature like SQLFORM.grid for example. Richard On Thu, Jul 5, 2012 at 5:58 PM, Derek <[email protected]> wrote: > It's got a lot more issues than that. It's pretty unusable at the moment. > After you get it working, then you have to assign projects to people via ID > number, and vice versa. You have to edit the database to get all new people > loaded into the system (ie - there is no custom admin module to promote > users to managers, etc). It's not a viable project, only there to show you > what you can do if you half-ass a project to complete a poorly designed > issue tracker. > > On Thursday, July 5, 2012 8:38:36 AM UTC-7, Richard wrote: >> >> Hello, >> >> Here a patch for web2py_issuetracker... >> I didn't read the whole app, so I hope it still works as intended. >> >> >> # HG changeset patch >> # User Richard Vézina <[email protected]> >> # Date 1341502246 14400 >> # Node ID d4a6372008825fa571f3f7b021b3e7**9fab7e7df4 >> # Parent **e4535bcdef395d6e8b1f777e8466e1**fc74a2d0d1 >> Fix not working app >> >> diff -r e4535bcdef39 -r d4a637200882 controllers/default.py >> --- a/controllers/default.py mar nov 01 08:23:10 2011 -0500 >> +++ b/controllers/default.py jeu jui 05 11:30:46 2012 -0400 >> @@ -18,11 +18,15 @@ >> >> >> def projects(): >> - COLUMNS=('project.name','**project.author','project.repo'** >> ,'project.license') >> - LINKS=[lambda row: A('issues',_href=URL('issues',**args=row.id))] >> + FIELDS=[db.project.name, >> + db.project.author, >> + db.project.repo, >> + db.project.license, >> + db.project.created_by] # created_by seems to be required in >> the fields list >> + LINKS=[lambda row: A('issues', _href=URL('issues', args=row.id))] >> def check(row): return (row.created_by == auth.user_id) >> - grid = SQLFORM.grid(db.project,**editable=check,deletable=**check, >> - columns = COLUMNS,links=LINKS) >> + grid = SQLFORM.grid(db.project, editable=check, deletable=check, >> + fields = FIELDS, field_id=db.project.id, >> links=LINKS) >> return dict(grid=grid) >> >> def issues(): >> @@ -49,13 +53,17 @@ >> auth.user.email in (project.members_email or [])): >> db.issue.owner.writable = False >> db.issue.status.writable = False >> - COLUMNS=('issue.status','**issue.summary','issue.created_**on', >> - 'issue.author','issue.labels') >> - LINKS=[lambda row: A('issue',_href=URL('issue',**args=row.uuid))] >> - grid = SQLFORM.grid(query, columns = COLUMNS,links=LINKS, >> - details=False,editable=False, >> + FIELDS=[db.issue.status, >> + db.issue.summary, >> + db.issue.created_on, >> + db.issue.author, >> + db.issue.labels, >> + db.issue.uuid] # uuid seems to be required in the fields list >> + LINKS=[lambda row: A('issue', _href=URL('issue', args=row.uuid))] >> + grid = SQLFORM.grid(query, fields = FIELDS, links=LINKS, >> + details=False, editable=False, >> deletable=project.created_on=**=auth.user_id, >> - >> create=auth.user_id,args=[pro**ject.id<http://project.id> >> ], >> + create=auth.user_id, args=[project.id], >> oncreate=lambda form:do_mail([db.issue(form.** >> vars.id <http://form.vars.id>)])) >> return dict(grid=grid, project=project) >> >> >> I will open a ticket on google code and post it there too, in case this >> mail get lost. >> >> Richard >> >> On Sat, Jun 2, 2012 at 3:26 PM, Anthony <[email protected]> wrote: >> >>> Yes, that's one of Julio's, creator of http://www.qa-stack.com/ **and >>> http://pyforum.org/. All three are listed on the Powered By site. >>> >>> Anthony >>> >>> >>> On Saturday, June 2, 2012 3:13:40 PM UTC-4, Massimo Di Pierro wrote: >>>> >>>> I had not seen it. Looks really slick. >>>> >>>> On Friday, 1 June 2012 23:49:31 UTC-5, Bruce Wade wrote: >>>>> >>>>> i-track is the winner I already have it integrated into my project and >>>>> will build off of it. >>>>> >>>>> On Fri, Jun 1, 2012 at 7:01 AM, Bruce Wade <[email protected]>wrote: >>>>> >>>>>> issue tracker there is an error when you click on projects on the >>>>>> demo not a good example :D >>>>>> i-track looks like a very good starting point if we want to build of >>>>>> an existing product. >>>>>> >>>>>> >>>>>> On Fri, Jun 1, 2012 at 12:37 AM, Jason (spot) Brower < >>>>>> [email protected]> wrote: >>>>>> >>>>>>> issue tracker I know of... >>>>>>> I am looking at itracker now >>>>>>> Thanks. :) >>>>>>> >>>>>>> >>>>>>> On Fri, Jun 1, 2012 at 10:31 AM, stefaan <[email protected]>wrote: >>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> I have noticed one other tracker in web2py, but I couldn't demo it. >>>>>>>>> >>>>>>>>> Have you seen these? >>>>>>>> >>>>>>>> http://code.google.com/p/**web2p**y-issuetracker/<http://code.google.com/p/web2py-issuetracker/> >>>>>>>> http://www.i-track.org/ >>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> -- >>>>>> Regards, >>>>>> Bruce Wade >>>>>> http://ca.linkedin.com/in/**bruc**elwade<http://ca.linkedin.com/in/brucelwade> >>>>>> http://www.wadecybertech.com >>>>>> http://www.fittraineronline.**co**m <http://www.fittraineronline.com>- >>>>>> Fitness Personal Trainers Online >>>>>> http://www.warplydesigned.com >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> -- >>>>> Regards, >>>>> Bruce Wade >>>>> http://ca.linkedin.com/in/**bruc**elwade<http://ca.linkedin.com/in/brucelwade> >>>>> http://www.wadecybertech.com >>>>> http://www.fittraineronline.**co**m <http://www.fittraineronline.com>- >>>>> Fitness Personal Trainers Online >>>>> http://www.warplydesigned.com >>>>> >>>>> >>
