Feature #1248
closed
New Permission: Edit own issues
0%
Description
- Today (as in version 0.7.1):
- We may only grant/revoke a role the permission to edit any issues ("Edit issues" permission).
- Suggestion / Request:
- It would be nice to be able to grant/revoke a role the permission to "Edit own issues".
Files
Related issues
Updated by 
Updated by
Updated by Royce Williams over 14 years ago
+1. Empowering users to modify their own request can reduce the load on the people processing requests.
Updated by Алексей Лошкарёв over 14 years ago
+1 This may reduce count of misspelled or invalid bug. Because user may do mistake on filling bug.
Updated by Leo Hourvitz about 14 years ago
- File 0001-Added-edit_own_issues-and-edit_own_new_issues-permis.patch 0001-Added-edit_own_issues-and-edit_own_new_issues-permis.patch added
I have a patch for this against recent trunk, attached. We are having this problem in a big way at an installation of mostly native Japanese speakers; with Asian languages, you're always hitting return to do Kanji conversion of your input and one extra carriage return means a half-baked issue in the tracker!
New Permissions¶
I addressed this by creating two new permissions that can be assigned to roles:- edit_own_issues allows users with that permission to edit issues they created (i.e., whose author field is equal to the current user). This addresses the problem, but is potentially a big workflow change, so not all sites might want it.
- edit_own_new_issues is a more limited permission that allows a user to edit their own issues if there are no journals yet, or if all existing journals were created by the author. I think this is really the pinpoint solution to the problem; as far as I know, all edits will create a journal, so this lets you edit your issue until the moment someone else pays attention to it.
- Because it seems like such a contained right, in the patch I added it to the default permissions for the Reporter role.
Implementation¶
To implement the above, I created a new editable? predicate on the issue model parallel to the visible? predicate that was already there (this also seems like a pretty good pattern to follow in general). Then, I changed the code that was doing User.current.allowed_to?(:edit_issues, @project)
to just call issue.editable?
instead.
I updated the English and Japanese locales as well.
The patch file was formatted with git format-patch; is that the preferred patch format? Specifically, the patch was generated against svn+ssh://rubyforge.org/var/svn/redmine/trunk@4175 e93f8b46-1217.
I'm fairly new to Redmine and Ruby, so it would definitely be good to get other eyes on this patch. I'll be able to get in some more testing next week. My configuration is:
bash-3.2$ RAILS_ENV=production ruby script/about About your application's environment Ruby version 1.8.7 (universal-darwin10.0) RubyGems version 1.3.5 Rack version 1.0 Rails version 2.3.5 Active Record version 2.3.5 Active Resource version 2.3.5 Action Mailer version 2.3.5 Active Support version 2.3.5 Application root /Users/leo/OpenSrcSources/redmine Environment production Database adapter mysql Database schema version 20100819172912
Updated by Leo Hourvitz about 14 years ago
I also applied this patch on our production redmine at work (Redmine 1.0.1 release on CentOS 5.2).
Updated by 
Updated by
Updated by Brian Lindahl almost 14 years ago
Created patch issue to follow the progression of my patch to add this feature and other issue edit permission improvements. Please add relation to #7444.
Updated by Leo Hourvitz almost 14 years ago
Is there any approved way to urge this get moved to trunk? I need to apply this on every Redmine instance we use, I think any installation with real scale of users is unmanageable without something like this.
Brian: I don't seem to have permissions to add the relation.
Updated by Brian Lindahl almost 14 years ago
Leo: Issue relations in Redmine are controlled by a different permission: 'Manage issue relations'. I can see a situation where project managers/software leads would not want issue reporters to have the ability to set up relations. Perhaps another permission should be added: 'Manage own issue relations'?
Updated by Brian Lindahl almost 14 years ago
Leo: Hah! Just realized that you were saying that you don't have the permissions to relate this issue to my patch issue #7444.
Updated by Etienne Massip over 13 years ago
- Target version set to Candidate for next major release
Updated by 
Updated by
Updated by Yannick Recht almost 13 years ago
+1 also.
It should be interesting to add this parameter.
Updated by Gabriel Mazetto over 12 years ago
It's also wise to have a "time limit" to help people not trying to modify something made a year ago, for example. As we will never find a good for everyone value, it's good to have it configurable, some values as suggestion:
- Limit own issue editing and own issue comments:
- Custom (please specify)
- 30 days
- 15 days
- 7 days
- 3 days
- 24 hours
- 12 hours
- 6 hours
- 3 hours
- less then one hour
- Never
Updated by 
Updated by
Updated by Thierry Brochu about 12 years ago
This would be an excellent feature to allow our client to edit the mistakes on its own created issues without having us to deal with it through a note left on this same issue by him. +1
Updated by Terence Mill about 12 years ago
+1 - very useful for redmine.org itself
Updated by Anonymous 
Updated by 
Updated by
Updated by Etienne Massip over 10 years ago
- Has duplicate Feature #6194: Edit own issues added
Updated by Toshi MARUYAMA over 10 years ago
- Related to Feature #5195: edit_own_issues and delete_own_issues permissions added
Updated by 
Updated by 
Updated by
Updated by Sandro De Melis almost 10 years ago
+1 this would be an excellent feature
Updated by 4wk_ _ over 9 years ago
+1, really need this. "Editing issue" grant ppl to be like an admin ! (and we don't want that, we want "Edit own issue")
Updated by Chet Wang over 9 years ago
+100
I really need this feature. We're planning to use Redmine but the lack of this feature blocks a lot.
Updated by Do Lam over 9 years ago
+100. We need this permission.
Thank so much!
Updated by
Updated by Trurl McByte over 9 years ago
+100500 It's bad idea to give access to edit all issues for Reporter only for possibility to change Status from Resolved to Closed
Updated by Adnan Topçu about 9 years ago
Leo Hourvitz's edit_own_new_issues is good idea.
edit_own_issues is topic of this issue.
edit assigned issues is most important for me
In my opinion, "own" is not clear for this mean. Reported or created is more understable ?
Updated by budo kaiman about 9 years ago
+1 to separate "Edit Reported Issues" and "Edit Assigned Issues".
Updated by Ronie Henrich about 9 years ago
Adnan Topçu wrote:
Leo Hourvitz's edit_own_new_issues is good idea.
edit_own_issues is topic of this issue.
edit assigned issues is most important for meIn my opinion, "own" is not clear for this mean. Reported or created is more understable ?
Owner == Author all accross Redmine, modifying this Redmine convention is out of this issue's scope.
Updated by Ronie Henrich about 9 years ago
budo kaiman wrote:
+1 to separate "Edit Reported Issues" and "Edit Assigned Issues".
- In regards to "Edit Reported Issues", please read my comment 40 (#1248#note-40) above;
- If a user belongs to a role with "Issues can be assigned to this role" enabled, having something like "Edit Assigned Issues" is not gonna stop him/her to edit an issue, it is just a matter of assigning the issue to himself/herself and voila, now he/she may edit the issue.
Updated by budo kaiman about 9 years ago
Ronie Henrich wrote:
- If a user belongs to a role with "Issues can be assigned to this role" enabled, having something like "Edit Assigned Issues" is not gonna stop him/her to edit an issue, it is just a matter of assigning the issue to himself/herself and voila, now he/she may edit the issue.
That only works if they already have "Edit Issues" permission, if they don't have that permission then they cannot assign an issue to themself, someone else with that permission must assign the issue to them.
Ronie Henrich wrote:
Owner == Author all accross Redmine, modifying this Redmine convention is out of this issue's scope.
I don't think that there is any scope change, just a wording change as "Author" or "Reporter" is more clear in it's intention.
Updated by
Updated by Pasi Karkkainen almost 8 years ago
Yes please, this is an important feature to have!
Updated by 
Updated by
Updated by Go MAEDA about 6 years ago
- Related to Feature #29935: Edit authored issues and Edit assigned issues in issue tracking permission added
Updated by Go MAEDA almost 6 years ago
- Has duplicate Feature #4767: Add permission group to allow 'edit your own tickets (header)'. added
Updated by Yuichi HARADA almost 6 years ago
- File add_permit_edit_own_issues@2x.png add_permit_edit_own_issues@2x.png added
- File 1248-edit-own-issues-permit.patch 1248-edit-own-issues-permit.patch added
Added "Edit own issues" permission. This permission can edit issues created by you regardless of the presence or absence of a journal.
I attached a patch.
Updated by Go MAEDA over 5 years ago
- Target version changed from Candidate for next major release to 4.1.0
LGTM. Setting the target version to 4.1.0.
Updated by Go MAEDA over 5 years ago
- Subject changed from Permissions - Edit own issues to New Permission: Edit own issues
- Status changed from New to Closed
- Assignee set to Go MAEDA
- Resolution set to Fixed
Updated by Mischa The Evil about 1 year ago
- Related to Defect #39493: Role with only :edit_own_issues no longer considered for workflow added