Feature #13538

Role Based Access Control on Subversion commit log

Added by Toru Haraguchi almost 10 years ago.

Status:NewStart date:
Priority:NormalDue date:
Assignee:-% Done:


Target version:-



Extending RBAC on Subversion commit log increase the value of Redmine.


Human-being fails sometimes in typing, or identifying his | her changes on a write-once system, such as SCMs.

On the other hand, based on "depravity" theory, once one have a device to rewrite his scribe, he | she start depending on the facility and stop reviewing before committing it, or even start tricking colleagues...

Cure should be a control mechanism.


Redmine reflects Subversion's (and possibly any other SCM's) changes to the views by modeling the information on a table sets "changesets", "changes", "changesets_issues".

Subversion has an API as hooks to validate revprop-change requests and notify it to external program.

Suggested Implementation

  1. Add role-based permission for SCM's commit log change, and declare it to users - Redmine's feature
  2. Add utilization script which validate log change request against the permission above, at such as Subversion's pre-revprop-change - User's responsibility, but hope provided in extra/svn
  3. Add utilization script which notify to Redmine by posting a record in Redmine's DB, that the log change request was validated and processed against certain revision of the repository - User's responsibility, but hope provided in extra/svn
  4. Add batch script which fetch the notification record above, and update the related records - Redmine's feature
  5. Invoke the batch script above periodically - User's responsibility

Related issues

Related to Redmine - Feature #2667: subversion commit info modification (using hook) Closed 2009-02-04

Also available in: Atom PDF