Bug Tracker Problem Topic is solved

[ustler]

Ok, im not familiar with SourceForge much.. But here is my problem.. I created a username

ustler

and wanted to answer and close some of the bugs. Ive already posted these in the forum, but other people have reposted them in the bugtracker.. Why cant i leave comments??? Plus the fact that others are posting my bug fix's from the forum in the bugtracker without leaving credit..

http://developer.joomla.org/sf/go/artf1064?nav=1

For example, was by me here way before the above fix was posted

http://forum.joomla.org/index.php/topic,6377.0.html

Also, file attachments??? Can i attach the patch files to other people's tickets??

Thank you, as i said, not familar with SourceForge bug tracking system.. I just want to see all those nasty bugs worked out..

Till i can figure this out, ill try posting them in forum.. Please hang in here with me..

ENJOY

[RobInk]

Moderator note; moved to correct forum; Support Zone, General Questions >> Other Forums, Joomla Forge

[Boomzilla]

Ustler - I see the problem. You are not a member of the Joomla! project you referenced and the defaul project permissions don't give you permission to create tracker artifacts unless you are logged in.

Defaul access permissions for th the Joomla! project are:

Not logged in - View tracker artifacts
All logged in users and create tracker artifacts and update them.

So - if you login to developer.joomla.org and go to the project you should be able to create new tracker artifacts and update those that exist.
If you continue to have problems please post back here and I'll do what I can to help out.

I am seeing other logged in users who are not members of the project creating tracker artifacts with no problem -- try logging in again and give it another try.

Col

[alwarren]

One difference I see here is that only the author of an artifact or a project member can leave comments on that artifact. In the old forge, I was able to help as a member of the community by posting fixes in tracker comments. Team members could then pick up the fix from the comments.

Being able to leave comments on artifacts gives the community a chance to participate in bug resolution.

While I'm on the subject. Where does the term artifact come from? I found it a bit confusing first time around.

[philmoz]

One difference I see here is that only the author of an artifact or a project member can leave comments on that artifact. In the old forge, I was able to help as a member of the community by posting fixes in tracker comments. Team members could then pick up the fix from the comments.

Being able to leave comments on artifacts gives the community a chance to participate in bug resolution.

While I'm on the subject. Where does the term artifact come from? I found it a bit confusing first time around.

This would be a handy option...
CASE:-
I submitted a 'bug' in template issued with Joomla 1.
When template maker went to post the required fix on my submtted artifact, he had no priveledges to add, so he had to opened a new artifact...
..Now my original artifact has been closed ( as it should be) due to duplicate artifact report(which could have been avoided)

[Boomzilla]

Re: "...only the author of an artifact or a project member can leave comments on that artifact..."

Actually, the role-based access control (RBAC) rules say that only users with Tracker Admin, Submit/View or
Edit/View permissions can update a tracker artifact. Each project has a set of default access permissions that apply to non-logged in, all logged in users, all project members etc. Each project also has a set of explicitly defined roles. A project member can be assigned 0 or more roles (if 0 are assigned then the default access permissions take effect).

In the case of the project of which you are writing, you have not been granted to comment on an artifact. It is is the responsibility  of the project admin to set permissions that suit the needs of their project. Now, since this permission system is new to the majority of users, I suspect that your lack of ability to post to the tracker is not intentional - it's just that the project admin is still learning how RBAC works :-)

And let me ask the obvious question of myself: "Isn't this role based access control system too complicated? The old way worked fine" - Indeed the old way did work -- however you'll find (and project admins especially will find) that this level of control allows for much better filtering of comments, feedback, assistance etc. And - if a project admin does not want to you it - they can set their default project permissions to the same level of access as with MamboForge as a one-time activity and will never have to touch permissions again.

Re: "While I'm on the subject. Where does the term artifact come from? I found it a bit confusing first time around."

A project may support multiple trackers. Each entry within a tracker is an "artifact".
Since as long as I can remember, entries in SourceForge Trackers have been called artifact - and my expereince dates back to SourceForge 2.4. I don't know from where the term comes, however.

Col

[alwarren]

Ok. I've dug and dug and experimented on my project. I just don't see any way to allow logged in users to comment on tracker artifacts if they are not the artifact author or project admin. That is, individual fields don't seem to have any access settings. Am I missing something or does the RBAC just not reach down to the field level?

[Boomzilla]

Re: "..I just don't see any way to allow logged in users to comment on tracker artifacts if they are not the artifact author or project admin..."

Two ways users can comment if they are not the artifact author or project admin:

1. Project Admin set's default access permissions such that the defined scope of users can view/submit/edit artifacts (scope can be "all users", "All logged in users", "all project members" etc);
2. Project Admin defines a role with view/submit/edit permissions and grants that role to named project members;

You are corrected re: level of granularity - role based access control's maximum level of granularity (for trackers at least) is per artifact - no per artifact field level of control - all files in an artifact are controlled by the RBAC settings for that tracker. You can define multiple trackers per project, each with different role settings.

Col

[mcjamison]

Re: "..I just don't see any way to allow logged in users to comment on tracker artifacts if they are not the artifact author or project admin..."

Two ways users can comment if they are not the artifact author or project admin:

1. Project Admin set's default access permissions such that the defined scope of users can view/submit/edit artifacts (scope can be "all users", "All logged in users", "all project members" etc);
2. Project Admin defines a role with view/submit/edit permissions and grants that role to named project members;

You are corrected re: level of granularity - role based access control's maximum level of granularity (for trackers at least) is per artifact - no per artifact field level of control - all files in an artifact are controlled by the RBAC settings for that tracker. You can define multiple trackers per project, each with different role settings.

Col

Unfortunately, it looks like alwarren is right - there's no current way to give edit permission to users beyond those who have it via role access (and thus project membership).  You can only give "view" and "submit/view" to non project members.  This was a decision made for the enterprise market; I definitely see the benefit of such a capability for a community site like this, though.  We should consider this for a future release...

-- Jamie

[Boomzilla]

Gatcha - because we didn't want non project members posting comments and horking up the work of the project members.
So - the answer is - request project membership with permissions to allow you to post to tracker artifacts.

Col

[Predator]

I guess the lack in here is the result of the different concepts for the Forges:

SF was developed for many Projects and many User/Developer in an public area.

SFEE for an intranet or an nonpublic area.

So the need in SFEE was not given to allow non Project Members to comment on the trackers, but to make even SFEE useable in the future to handle it in a similare way as the SF it should be setable to allow it the same way.

[Boomzilla]

Er... yes. I think.

Your are correct there there were different design goals set for SFEE. However the underlying engine would quite happily support the permisisons model that folks are used to with SF.net and older instances of SourceForge. We've noted the request for the capability for non project members to post to tracker artifacts. Likley a change (expansion) to the default project permissions would take care of this.

Col

[alwarren]

Glad to hear it. I for one, having done my time in the trenches for a paycheck, make it somewhat of a hobby of tracking down the odd glitch and bug when I can. It's just my fun way of giving something to the project. Personally, I wouldn't mind being on the maintenance team. I have the skills and time. I certainly have this uncanny perverted ability to scan code for hours on end. Friends say I'm nuts. But hey, it's what I enjoy. So I look forward to having the privilage - and I mean privelage as an honor to be able to help out the guys in the trenches. Been there done that and just hope to be able to give a little something back. And for the record - no I don't own a pocket protector. I do however still have my trusty slide rule. 

[Boomzilla]

And we certainly appreciate your help in answering questions etc on this forum. One of the problems from which I suffer (and my problems are legion) is that I'm so close to SourceForge sometimes I can't see the wood for the trees. It's often very valuable to have a fresh pair of eyes to Post things that will pass me by without my noticing.

Thanks!

Col