MantisBT

View Issue Details Jump to Notes ] Wiki ] Related Changesets ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0010884mantisbtcustomizationpublic2009-08-27 10:272013-04-06 09:26
Reportercmfitch1 
Assigned Todhx 
PrioritynormalSeverityfeatureReproducibilityN/A
StatusresolvedResolutionfixed 
PlatformOSOS Version
Product Version 
Target Version1.3.xFixed in Version1.3.x 
Summary0010884: Make 'edit', 'delete', and 'make private' buttons on bugnotes independently configurable
DescriptionCurrently, it is only possible to configure whether a user can edit and delete his/her bugnotes. It would be nice if each action that can be taken on a bugnote was configurable independently of the others. For example, it would be useful to allow users to edit their bugnotes, but not to delete them or make them private.
Tags2.0.x check, patch
Attached Filespatch file icon issue_10884.patch [^] (7,399 bytes) 2009-08-27 10:46 [Show Content]
patch file icon issue_10884_a.patch [^] (7,176 bytes) 2009-09-25 20:51 [Show Content]

- Relationships
related to 0015721new Functionality to consider porting to master-2.0.x 
child of 0010964confirmed Anonymous account problems at 'reporter' access level (no bugnote_edit_threshold, public/private problems) 

-  Notes
User avatar (0022979)
dhx (developer)
2009-09-19 13:27

Ah, I was just looking for something like this. Thanks!

I see you've implemented these checks as boolean on/off switches whereas they really should be thresholds. This would allow for much greater flexibility with respect to anonymous accounts where we need to have the ability to disallow anonymous users from editing bugnotes (but registered users can). If you want to disable something, just set the access level to NOBODY and that effectively turns the feature off. If you want to give everyone access to a feature (highly unlikely...) then there is ANYBODY for that purpose.
User avatar (0023033)
cmfitch1 (reporter)
2009-09-25 20:54

I have uploaded a second patch to convert my original work into thresholds. Apply the first patch followed by the second to get everything.
User avatar (0023407)
dhx (developer)
2009-10-27 08:17

Thanks. I'll get onto this soon. I haven't forgotten :)
User avatar (0023979)
Zamolxis (reporter)
2009-12-23 21:09

Hi. I am interested in this feature as well. Thanks cmfitch1 & dhx. ;)
User avatar (0024179)
dhx (developer)
2010-01-17 07:24

I've rewritten this patch with some changes and improvements, and committed it to the 1.3.x branch. Please try it out and let me know if there are any problems (or things that you weren't expecting).

Thanks for your initial patches :)
User avatar (0036517)
grangeway (developer)
2013-04-05 17:57

Marking as 'acknowledged' not resolved/closed to track that change gets ported to master-2.0.x branch

- Related Changesets
MantisBT: master da6c133f
Timestamp: 2010-01-17 08:43:08
Author: dhx
Details ] Diff ]
Issue 0010884: Improve granularity of bugnote permissions

Currently it's only possible to use a single
$g_bugnote_allow_user_edit_delete setting to turn ON or OFF the ability
for users to be able to edit/delete their own bugnotes.

This patch provides improvement to the granularity of bugnote
permissions to make the following possible:
1) Separate edit and delete permissions
2) Thresholds instead of boolean switches
3) Ability for users to change the view state of their own bugnotes

On the topic of view states, the $g_set_view_status_threshold setting
controls whether a user can make a bug or bug note private at the time
of reporting/posting. The existing $g_change_view_status_threshold
setting allows users to change the view state of any bug or bug note
after they've been reported/posted. This patch introduces
$g_bugnote_user_change_view_state_threshold which allows administrators
to give users the the ability to make their own bugnotes public or
private as they choose, at any time.

$g_bugnote_user_edit_threshold is a new setting that can be changed to
allow users the ability to edit their own bugnotes.
$g_bugnote_user_delete_threshold is a new setting that can be changed to
allow users the ability to delete their own bugnotes. You may be
wondering why there is a difference when a user could simply edit and
blank their bugnote. The answer lies with bugnote revisions and the
ability for users to see a revision history of each bug that has been
edited.

Many thanks to Chris Fitch for the original idea and an initial patch
from August 2009. This patch is a rewrite of his earlier work with a
number of additional changes and improvements.
mod - config_defaults_inc.php Diff ] File ]
mod - lang/strings_english.txt Diff ] File ]
mod - bugnote_add.php Diff ] File ]
mod - manage_config_work_threshold_set.php Diff ] File ]
mod - bugnote_delete.php Diff ] File ]
mod - bugnote_update.php Diff ] File ]
mod - docbook/adminguide/en/page_descriptions.sgml Diff ] File ]
mod - docbook/adminguide/en/configuration.sgml Diff ] File ]
mod - core/bugnote_api.php Diff ] File ]
mod - bugnote_edit_page.php Diff ] File ]
mod - manage_config_work_threshold_page.php Diff ] File ]
mod - core/obsolete.php Diff ] File ]
mod - bugnote_set_view_state.php Diff ] File ]
mod - bugnote_view_inc.php Diff ] File ]
mod - bugnote_add_inc.php Diff ] File ]

- Issue History
Date Modified Username Field Change
2009-08-27 10:27 cmfitch1 New Issue
2009-08-27 10:46 cmfitch1 File Added: issue_10884.patch
2009-09-19 13:27 dhx Note Added: 0022979
2009-09-19 13:28 dhx Tag Attached: patch
2009-09-19 13:28 dhx Relationship added child of 0010964
2009-09-19 13:29 dhx Status new => acknowledged
2009-09-25 20:51 cmfitch1 File Added: issue_10884_a.patch
2009-09-25 20:54 cmfitch1 Note Added: 0023033
2009-10-27 08:17 dhx Note Added: 0023407
2009-10-27 08:17 dhx Assigned To => dhx
2009-10-27 08:17 dhx Status acknowledged => assigned
2009-10-27 08:17 dhx Target Version => 1.3.x
2009-12-23 21:09 Zamolxis Note Added: 0023979
2010-01-17 07:24 dhx Note Added: 0024179
2010-01-17 07:24 dhx Status assigned => resolved
2010-01-17 07:24 dhx Fixed in Version => 1.3.x
2010-01-17 07:24 dhx Resolution open => fixed
2010-01-17 07:30 dhx Changeset attached master da6c133f =>
2010-04-23 23:23 dhx Status resolved => closed
2013-04-05 17:57 grangeway Status closed => acknowledged
2013-04-05 17:57 grangeway Note Added: 0036517
2013-04-05 18:04 grangeway Relationship added related to 0015721
2013-04-06 03:44 dregad Status acknowledged => resolved
2013-04-06 07:20 grangeway Status resolved => acknowledged
2013-04-06 09:26 dregad Tag Attached: 2.0.x check
2013-04-06 09:26 dregad Status acknowledged => resolved


MantisBT 1.2.16dev master-1.2.x-8c2bd07 [^]
Copyright © 2000 - 2013 MantisBT Team
Time: 0.1232 seconds.
memory usage: 2,883 KB
Powered by Mantis Bugtracker