Hello admins/devs of the BugTracker!
ED had given me admin permissions for the BugTracker, in order to check its settings, and I think, as they are now, most of the troubles reported in FS#245 are fixed.
Nevertheless, I ask you to please go through this my evaluation, to answer remaining questions concerning the BugTracker.
And, if I am certain, that I am fully aware of the BugTracker, I offer to you to update its documentation/help at http://pandorawiki.org/Reporting_bugs accordingly.
Regards, Stefan Nowak from Vienna (porg)
---
!! Global versus project-based user groups
This is the status quo at http://bugs.openpandora.org :
* User groups are configured for "All projects" (=globally).
* The particular projects seem to have no user groups set up, and simply use the global user groups.
I think this is a good principle, as OpenPandora is an open source approach. Distinct user groups per project seem to only make sense for security/secret projects. The only other reason, I could think of, is as a workaround to achieve fine-grained notifications.
But the setup as of now seems pretty reasonable as it is.
!! User groups & registration
Active user groups:
* Admin: Can do everything.
* Developer: Can do almost anything. (Only non-granted permissions: Project Manager, View event log)
* Basic: As the name already tells. I looked at this group's permissions, and it seems that my inquiry FS#245 is almost solved by how this group's settings are.
Default global group for new users: Basic.
These user groups have no members, seem to be un-used:
* Pending
* Reporters
What was/is their purpose?
Any intentions to use them still/again?
I guess the thought behind this was:
* Give freshly registered users enough trust (can create and delete their own content, but not edit/delete others' content), so the worst which could happen is if they report redundantly, write inpolitely, or spam.
* For the case that this setup does not work so fine, you will change auto-assignment of new users to "Pending" (which has no rights at all, even less than the anonymous user who can at least view), and approve new users manually.
Right?
!! Permissions
!!! Permissions granted to Basic
Members can login
View history
View tasks
Open new tasks
Modify own tasks # Part of fixing FS#245.
Close own tasks # Part of fixing FS#245.
View comments
Add comments
Edit own comments # Part of fixing FS#245.
Create attachments
Assign tasks to self if not already assigned
Assign others' tasks to self
Add self to assignees
!!! Permissions only granted to Developer and Admin
Modify tasks that are not user's own
Close tasks that are not user's own
Edit comments
Delete comments
Delete attachments
Edit assignments
Show as assignees
Can Vote for tasks
!! Basic user - Open questions concerning FS#245
!!!! Delete own attachments
I think basic users should have the ability to "Delete own attachments". I do not see this particular permission within FlySpray. I only see the permission "Delete attachments", but we can't grant this to basic users.
So as it seems, attachments once uploaded cannot be removed anymore. Right?
If it is like this, I would like to add this info to http://pandorawiki.org/Reporting_bugs
!!!! Assignment
Basic currently has these permissions:
* Assign tasks to self if not already assigned
* Assign others' tasks to self
* Add self to assignees
Basic currently lacks these permissions:
* Edit assignments
* Show as assignees
These are my arising questions:
* My observation: The basic user can either assign a task to an Admin, a Developer or to him/her-self, but not to other Basic users. One of the developers is called "openpandora", who I guess shall be assigned if the Basic user is uncertain, or if the Developers decide to assign a shared responsibility. Are my assumptions correct? If so, I would like this to also be documented at: http://pandorawiki.org/Reporting_bugs
* If the basic user assigns a task to him/her-self, can he/she later un-assign her/him-self?
* What does "Show as assignees" mean? That the user shows as a possible choice for "Assigned To" within the task submission form? Or that a user is shown as assignee in task listings or detailed task views? The English noun "assignee" is ambiguous, thus a short remark in German between porg and EvilDragon which may helps to get to a clear understanding: Wir haben in Deutsch die Möglichkeit zu sagen "Zugeteilter" (=hat die Verantwortung übernommen, "assigned person") oder "Zuteilbarer" (=steht zur Verfügung um die Verantwortung zu übernehmen "assignable person").
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#265 - MiniMenu: Flawed tab display of sub-categories if they have a common string beginning
User who did this - Stefan Nowak (porg)
----------
Just to be certain, that you did not misunderstand me:
The bug occurred with no asterisk character being involved at all !!!
I just used the asterisk as a denotation in the report!
If you understood it that way, and were indeed writing in the sense that you actually have an "asterisk flaw" in your code, then I would say forbidding asterisks in sub/category strings is an understandable standard, if you cannot figure out a solution with a control character, which undeniably would be the best solution.
Users will live with the limitation of not using an asterisk character much better than having to abstain from using strings which share the same beginning, which is the current limitation due to the bug.
----------
More information can be found at the following URL:
http://bugs.openpandora.org/index.php?do=details&task_id=265#comment369
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has been re-opened:
FS#265 - MiniMenu: Flawed tab display of sub-categories if they have a common string beginning
User who did this - Stefan Nowak (porg)
More information can be found at the following URL:
http://bugs.openpandora.org/index.php?do=details&task_id=265
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task is now closed:
FS#265 - MiniMenu: Flawed tab display of sub-categories if they have a common string beginning
User who did this - Jeff (skeezix)
Reason for closing: Fixed
More information can be found at the following URL:
http://bugs.openpandora.org/index.php?do=details&task_id=265
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#265 - MiniMenu: Flawed tab display of sub-categories if they have a common string beginning
User who did this - Jeff (skeezix)
----------
Investigating the code .. okay, so I very deliberately did this, as a side effect of how I did it internally (a quick hack ;)
-- ie: it appends subfolder name to parent folder name, with a * separator (which is normally not allowed in this sort of thing)
-- this explains why * buggers up
-- this explains the weird behaviour of filtering bring up multiple similar names subfolders, due to how its calculating which part of the name to look at
I should probably block '*' from allowable characters .. or at least strip it out, to avoid _this_ problem (by creating another, since you might want *.. but you shouldnt' use that, so thats probably more acceptible.)
I could use another character but that just displaces the problem. I could use a control or otherwise unprintable character, but need to do a code review about that, and I'm al ittle tight for time so can worry about that later.
For now I am mapping * to _ when entered into 'register custom subcategory' and 'register cvustom category'.
The multiple tabs showing up in a subfolder view is now fixed.
http://git.openpandora.org/cgi-bin/gitweb.cgi?p=pandora-libraries.git;a=com…
----------
More information can be found at the following URL:
http://bugs.openpandora.org/index.php?do=details&task_id=265#comment368
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task is now closed:
FS#263 - MiniMenu with "Auto discover pnd apps?" set to NO hangs in endless loop! Even after reboot!
User who did this - Jeff (skeezix)
Reason for closing: Fixed
Additional comments about closing: This is a use-case I try to keep working, though few if any will try it; my goal was to allow for directory browser use case even when no apps are being pulled in (which is an odd case, since the base firmware usually includes some apps.) Recent changes for the .desktop mode wirh pnd-mode turned off brought in this regression. All fixed now :)
Thanks for the report :)
More information can be found at the following URL:
http://bugs.openpandora.org/index.php?do=details&task_id=263
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#263 - MiniMenu with "Auto discover pnd apps?" set to NO hangs in endless loop! Even after reboot!
User who did this - Stefan Nowak DevTest (testporgdev)
----------
THIS IS A TEST. Ignore it. Just testing whether adding a comment as an dev user works.
----------
More information can be found at the following URL:
http://bugs.openpandora.org/index.php?do=details&task_id=263#comment367
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#263 - MiniMenu with "Auto discover pnd apps?" set to NO hangs in endless loop! Even after reboot!
User who did this - Stefan Nowak Testing (testporg)
----------
THIS IS A TEST. Ignore it. Just testing whether adding a comment as an basic user works.
----------
More information can be found at the following URL:
http://bugs.openpandora.org/index.php?do=details&task_id=263#comment366
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#263 - MiniMenu with "Auto discover pnd apps?" set to NO hangs in endless loop! Even after reboot!
User who did this - Stefan Nowak (porg)
----------
Testing to add a comment as it was reported that comments don't work on the bug tracker.
----------
More information can be found at the following URL:
http://bugs.openpandora.org/index.php?do=details&task_id=263#comment365
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has been changed. The changes are listed below. For full information about what has changed, visit the URL and click the History tab.
FS#263 - MiniMenu with "Auto discover pnd apps?" set to NO hangs in endless loop! Even after reboot!
User who did this: Stefan Nowak (porg)
Assigned To: [-] -> Jeff
More information can be found at the following URL:
http://bugs.openpandora.org/index.php?do=details&task_id=263
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.