Feature #11109
closed
Repository Identifier should be frozen
Added by Jan from Planio www.plan.io over 12 years ago.
Updated over 12 years ago.
Description
I'd like to suggest/discuss the idea of "freezing" the repository identifier just like it's done for the project identifier, i.e. after a project has been created, the identifier cannot be changed anymore.
From what I understand in the comments to #779, the identifier is used in URLs and for wiki links. Both would benefit from the identifier being frozen like for projects as this would prevent users from inadvertently breaking existing links.
What do you think? Would be happy to provide a patch if you share my opinion.
Files
- Target version set to Candidate for next major release
Is it possible 'frozen' to be configurable in a checkbox at project or at Redmine level?
Ivan Cenov wrote:
Is it possible 'frozen' to be configurable in a checkbox at project or at Redmine level?
Why so?
I don't think it would make sense to make this a configurable setting. In my point of view, changing identifiers after a repo has been created can lead to broken links and confusion among users. I don't see a benefit of having changeable identifiers, so I'd say no configuration option.
Here's a patch against current trunk (r9879). Most of it is taken directly from the corresponding code for project identifiers. What do you think?
Jan from Planio www.plan.io wrote:
Here's a patch against current trunk (r9879). Most of it is taken directly from the corresponding code for project identifiers. What do you think?
Looks fine to me.
- Target version changed from Candidate for next major release to 2.1.0
- Status changed from New to Closed
- Assignee set to Jean-Philippe Lang
- Resolution set to Fixed
Patch applied with slight changes in r10081.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by