I'm looking for a part-time remote job.

Hire me


I'm the author of:

Mastering Redmine is a comprehensive guide with tips, tricks and best practices, and an easy-to-learn structure.

Check the book's project or

Buy the book

Social pages of the book:

By buying this book you also donate to Redmine (see this page).


Follow me:

Bug #2421

The access to Git is based on projects identifier.

Added by Sven Mayer over 2 years ago. Updated 11 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:

0%

Redmine version:
External issue:

Description

The access to Gits is based on projects identifier. When the projects identifier and the git repository name is not the same, the member access will fail. Somehow the access rules are based on a string comparison not on the projects number.

Thus, I can create two different gits but never access both because always one GIT has a different name then the project name. If the GIT access rules are based on the project ID’s and the links to the repository and then their name this would be possible.

Furthermore, its super confusing that I can not just rename a GIT repo and fix the database entry in the table “repositorys”. In order to to so I also need to rename the projects identifier.

History

#1 Updated by mizuki ishikawa 11 months ago

I think that it can be solved by setting the repository name to project_identifier.1, project_identifier.2, etc.

Also available in: Atom PDF

Terms of use | Privacy policy