allow multiple issue_server_link

Issue #518 resolved
domruf created an issue

This would not only allow to use different issue trackers for different projects but also allow to create links to other services like a wiki.

for example additionally to the issue tracker link you could add something like

issue_pat = (?:\s*#)(\d+) wiki_pat = \b(wiki)-(.+)\b foo_apt = ... issue_server_link ={id} wiki_server_link ={id} foo_server_link = ...

Comments (11)

  1. Marcin Kuzminski repo owner
    • changed milestone to 1.4
    • edited description
    • removed version

    I like this idea, but it would require to store it per-project and it database.

    notes for me:

    • cache it like hell !
    • maybe use some pre-populate option so we don't ask db for it
  2. domruf reporter

    In my case it would already help if I could define multiple patterns and servers in the production.ini, but you are right a per-project configuration would be better.

  3. johnament

    At least from my perspective it wouldn't work from a per project perspective. There are multiple bug keys on our side, and each one routes to a slightly different URL. These bug keys are global though, so every project would end up with the same 3 bug keys.

  4. Marcin Kuzminski repo owner

    I don't see a problem of providing a list of patters per project, and just iterate over that to change patterns into links

  5. domruf reporter

    Maybe the best solution would be to allow both. In a first step different pattern/URL combinations in the production.ini (which would solve my use case and I think johnament's as well) and then also allow to override these pattern/URL combinations on a per project basis.

  6. Marcin Kuzminski repo owner

    This has been fixed in RhodeCode 3.0 series release. With a web interface that allows to configure multiple systems

  7. Log in to comment