Redmine

+1

+1. Empowering users to modify their own request can reduce the load on the people processing requests.

+1 This may reduce count of misspelled or invalid bug. Because user may do mistake on filling bug.

I also applied this patch on our production redmine at work (Redmine 1.0.1 release on CentOS 5.2).

+1 - this should go in the trunk.

+1

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.

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.

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'?

Leo: Hah! Just realized that you were saying that you don't have the permissions to relate this issue to my patch issue #7444.

+1

+1

+1 also.

It should be interesting to add this parameter.

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

+1

+1

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

+1 - very useful for redmine.org itself

+1 crucial

+1

+1 please for 3.0.0

A feature that we should have, please!

+1 please

+1

+1 - will be very useful

+1 will be usefull

+1 this would be an excellent feature

+1, really need this. "Editing issue" grant ppl to be like an admin ! (and we don't want that, we want "Edit own issue")

+100

I really need this feature. We're planning to use Redmine but the lack of this feature blocks a lot.

+100. We need this permission.
Thank so much!

+100 v 3.1

+100500 It's bad idea to give access to edit all issues for Reporter only for possibility to change Status from Resolved to Closed

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 ?

+1 to separate "Edit Reported Issues" and "Edit Assigned Issues".

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 me

In 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.

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.

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.

+1

Yes please, this is an important feature to have!

+1

must have feature indeed