View Issue Details Jump to Notes ] Wiki ] Related Changesets ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0011290mantisbtfeaturepublic2009-12-16 08:072014-02-13 16:08
Assigned Todregad 
PlatformOSOS Version
Product Version 
Target Version1.3.xFixed in Version1.3.x 
Summary0011290: Create Clone access to reporters
DescriptionUsers with "reporter" access can submit issues.

It would be great if these users also could use the "Create Clone" feature, instead of having to open XX "Report Issue"-forms, copy & paste data from a previously submitted issue, just to make a similar (but not identical), new issue.
TagsNo tags attached.
Attached Filespatch file icon 0001-Allow-Reporters-to-Clone-issues.patch [^] (2,549 bytes) 2012-01-09 12:49 [Show Content]
patch file icon 11290-allow-reporter-close-option1-v2.patch [^] (3,508 bytes) 2012-05-23 05:58 [Show Content]

- Relationships
has duplicate 0013323closeddregad Add the option to be able to link to read-only tickets 

-  Notes
User avatar (0023915)
RoboDoc (reporter)
2009-12-16 08:11

This would be VERY useful for "repetitive work"-purposes, e.g.

Parent: "Update BIND on all name servers"
`- CHILD1: " - Update BIND"
`- CHILD2: " - Update BIND"
`- CHILD3: " - Update BIND"

And yes; we use MantisBT for other stuff than code bugtracking, as well; [simple] project management, systems maintenance, logistics, tracking non-code-related bugs, etc. :-)
User avatar (0023917)
RoboDoc (reporter)
2009-12-16 08:59

It seems that UPDATER access is needed (re. "update_bug_threshold"), but it should be sufficient with REPORTER access for this operation.
User avatar (0030882)
dregad (developer)
2012-01-09 12:17
edited on: 2012-05-23 05:59

This behavior is by design, as cloning an issue will allow the user to create a relationship to the parent issue, which will be updated by doing so.

That being said, your suggestion makes sense. Please consider these 2 alternatives:

1. Allow Reporters to clone issues

In that case, to be consistent with access rights, the "Relationship with the parent issue" field in bug_report_page.php should be disabled when the user does not have updater access to the parent bug.

See attached: 11290-allow-reporter-close-option1-v2.patch

2. Create a new config option $g_clone_bug_threshold

With that new setup, we could treat the bug cloning as a special case in which it is acceptable for a Reporter to update a bug they would normally not be allowed to change; however, since that change is very limited and controlled in nature (i.e. creating a new relationship), this may be acceptable.

I recommend to go for option 1, which is more respectful of the access rights. Please test and let me know your thoughts.

If you think option 2 is necessary, I'll bounce it off the other devs to see what they think.

EDIT: revised patch (old one was missing modification of access check in bug_report.php)

User avatar (0030898)
vincent_sels (reporter)
2012-01-12 17:07
edited on: 2012-05-23 16:03

Pretty much a duplicate of one of my tickets: 0013323. The solution I went for is more like your option 2.
User avatar (0031884)
dregad (developer)
2012-05-23 05:58

Following a discussion on the mailing list [1] a new option was identified

3. Allow a user without update_bug_threshold to add relationship to parent

Even though strictly speaking that should be considered as an update of the parent bug, this would probably be acceptable in the limited context of cloning and would avoid adding a new config option.

[1] [^]
User avatar (0039323)
dregad (developer)
2014-02-05 09:40

See PR
- [^] for option 1
- [^] for option 3

Option 2 not implemented at this stage
User avatar (0039397)
dregad (developer)
2014-02-13 14:31

Implemented option 3 (Allow a user without update_bug_threshold to add relationship to parent)

- Related Changesets
MantisBT: master 8aafaaf4
Timestamp: 2014-02-05 07:51:54
Author: dregad
Details ] Diff ]
Allow Reporters to Clone issues

Previously, users needed to have update_bug_threshold to be able to
clone issues, since the creation of a relationship with the parent bug
requires to update it.

This patch lets Reporters clone issues and allows them to create a
relationship with the parent, even if they lack updater access.

Fixes 0011290 (implements option 3)
mod - bug_report.php Diff ] File ]
mod - bug_report_page.php Diff ] File ]
mod - core/html_api.php Diff ] File ]

- Issue History
Date Modified Username Field Change
2009-12-16 08:07 RoboDoc New Issue
2009-12-16 08:11 RoboDoc Note Added: 0023915
2009-12-16 08:59 RoboDoc Note Added: 0023917
2012-01-09 12:17 dregad Note Added: 0030882
2012-01-09 12:17 dregad Status new => acknowledged
2012-01-09 12:49 dregad File Added: 0001-Allow-Reporters-to-Clone-issues.patch
2012-01-09 12:50 dregad Note Edited: 0030882 View Revisions
2012-01-12 17:07 vincent_sels Note Added: 0030898
2012-01-13 05:22 dregad Relationship added has duplicate 0013323
2012-05-23 05:58 dregad Note Added: 0031884
2012-05-23 05:58 dregad File Added: 11290-allow-reporter-close-option1-v2.patch
2012-05-23 05:59 dregad Note Edited: 0030882 View Revisions
2014-02-05 09:40 dregad Note Added: 0039323
2014-02-05 09:47 dregad Assigned To => dregad
2014-02-05 09:47 dregad Status acknowledged => assigned
2014-02-13 12:37 dregad Changeset attached => MantisBT master 8aafaaf4
2014-02-13 12:37 dregad Status assigned => resolved
2014-02-13 12:37 dregad Resolution open => fixed
2014-02-13 12:37 dregad Fixed in Version => 1.3.0dev
2014-02-13 14:31 dregad Target Version => 1.3.x
2014-02-13 14:31 dregad Note Added: 0039397
2014-02-13 16:08 atrol Fixed in Version 1.3.0dev => 1.3.x

MantisBT 1.2.17 [^]
Copyright © 2000 - 2014 MantisBT Team
Time: 0.1123 seconds.
memory usage: 3,075 KB
Powered by Mantis Bugtracker