Project alias plugin¶

The name of this plugin should be “Project identifier rename”... But project identifier aliases are what makes the renaming possible! They allow to access project pages using different identifiers in URL thus any of such identifiers can be made a project identifier. All that is needed for this is to move the previous identifier to aliases (this is done by replacing the alias, which has been made a project identifier). That’s how this plugin does the trick!

Using¶

Project identifier aliases can be managed only by administrators. To add an alias, remove an alias or rename a project identifier one should open “Administration” → “Project aliases”.

This menu item will open the alias listing:

Notice the link “Use as identifier”. By clicking on this link you put the alias into the project as an identifier and save the previous identifier as an alias... So visually nothing changes except the project’s links, which now contain the new identifier. The old links are still accessible too.

By clicking on the “New project alias” link one gets the form:

Known issues¶

Many things rely (or can rely) on the fact that project identifiers cannot be changed! So this plugin can break such things... To provide a solution for them the plugin adds the :controller_project_aliases_rename_after hook, which can be used to fix things, when project identifier is changed. But till the moment all of such issues are fixed, here I will put things (e.g. plugins), which are known to conflict with this plugin or get broken by the plugin.

If you found some other Redmine/ChiliProject functions or plugins, which conflict with the Project Alias plugin please feel free to list them on this page or email me directly using this contact form.

Check also this page for information on how to use the hook.

Redmine.pm¶

Redmine.pm does not support aliases and, if the project identifier is changed, Redmine authentication for the SCM repository will stop to work!

As a workaround you can rename the SCM repository and ask users to update their local copies.

See also #1985...

Install¶

To install the plugin:

• For Redmine 2.x.x and above:
  • Copy project_alias directory to #{RAILS_ROOT}/plugins.
  • Run migration: rake redmine:plugins:migrate RAILS_ENV=production.
• For older Redmine and ChiliProject:
  • Copy project_alias directory to #{RAILS_ROOT}/vendor/plugins.
  • Run migration: rake db:migrate:plugins RAILS_ENV=production.
• Restart Redmine/ChiliProject.