Bugs should be global to project members

corvex picture corvex on Mon 27 Jul, 2009 12:33:30 +0000

Hello,

first, thanks for the free service!

However ;) the bug system could be upgraded to “team compatible” with a simple(-looking) change. Currently, if a non-admin reports a bug, it’s only visible by himself. Even the admin can’t see/access it! In my opinion, bugs belong to the project, not to the reporter.

My suggestion would be the following:
- All members with read access can see all bugs.
- All members with write access can insert/edit/delete bugs, even set the “responsible” field.
- The “Bugs” list lists all bugs. Options/alternative views: owned bugs, non-closed bugs.

With this, xp-dev would gain a nice&simple bug tracking system where every team member could report bugs and fix the bugs they’re assigned to.

The masks are okay, it’s only the access control that’d change so I think it might not be so hard to implement.

(I reckon that the current system can be used as a todo-tracking app – but 1) its name is “bugs” so why not make it a bug tracker ;) 2) todo tracking can be done in a blog/wiki page easily, but bugtracking can’t be performed easily in other apps.)

(I think it’s half-way between a bug report and a feature request... I chose to put it here after I got an access denied error as the project admin when I tried to see the URL of a bug reported by a project member.)

Forum Topic Options

Feeds

Forum Topic and Comments

rs picture

rs on Tue 28 Jul, 2009

Thats really weird – that way that it works currently is that any project member who is a writer or owner can raise bugs and they can be seen by everyone who is a reader, writer or owner. I’ve just retested it and it works as expected.

Just one reminder – the project permissions is separate from the repository permissioning. Users who are readers or writers will see the project listed under their Permissioned Projects tab.

So, some pointers will be to ensure that:

  • The permissions are setup correctly for projects. Not the repository permissions
  • The bug is raised on the correct project

It sounds like the bug was raised on a project that you don’t have permission to (it could have been raised on a different project?).

My suggestion would be the following:
- All members with read access can see all bugs.
- All members with write access can insert/edit/delete bugs, even set the “responsible” field.
- The “Bugs” list lists all bugs. Options/alternative views: owned bugs, non-closed bugs.

Points 1 and 2 are already there (it should work as expected). Point 3 should be sorted out in the new version using filters – which are essentially save-able search queries on the database.

Do raise a support ticket and I can look into whether you have got permissions setup correctly. Do post the URL that you couldn’t access as well in the ticket.

corvex picture

corvex on Wed 29 Jul, 2009

Oops, sorry, it was my fault :) The writer user had an owned project with the same name. I’ve deleted it, created a bug at the right place, and it works well. (y)

Your comment helped a lot, I investigated further when I learnt that it should work :) I guess it’d be useful to extend the corresponding Wiki page with a short description of this functionality.

You do not have sufficient permissions to comment