Question: configuring different issue URL?

I’ve tried quite a few approaches and searched around and still can’t seem to get this working, I was wondering if you could help please as I’m sure I must be doing something wrong.

I have a project which is hosted on a private GitLab and use Jira for issues which is hosted elsewhere. Regardless of what I’ve tried, the issue tracker link is always set to eg. http://[e-mail]:group/project/issues/1234 – a strange hybrid of repository.url.

The notable parts of my package.json are below;

{
  "bugs": {
    "url": "https://foo.jira.com/browse-3/"
  },
  "config": {
    "commitizen": {
      "path": "./node_modules/cz-conventional-changelog"
    },
    "ghooks": {
      "commit-msg": "validate-commit-msg"
    }
  },
  "devDependencies": {
    "cz-conventional-changelog": "1.1.6",
    "validate-commit-msg": "2.6.1",
    "standard-version": "2.3.0"
  },
  "issue": "https://foo.jira.com/browse-1/",
  "issues": "https://foo.jira.com/browse-2/",
  "repository": {
    "type": "git",
    "url": "[e-mail]:group/project.git"
  },
  "scripts": {
    "release": "standard-version"
  }
}

[spudheadc]

For future reference you can use a postchangelog lifecycle hook to replace your github url with your jira url.

Something along the line of

“standard-version”: { “scripts”: { “postchangelog”: “replace ‘MY GITHUB URL’ ‘MY JIRA URL’ CHANGELOG.md” } }

[stevemao]

Sorry, the idea of this module is meant to be opinionated so it cannot be configured.

I was just trying to explain why it looks for repository.url instead of bugs entry.

How the current system works is something like this: host + user + repo + issue + issueNumber

Because we have tools to get git hosted info so we can get a lot of useful information about the url. user here is not hard coded to the current project’s user. So if you reference an issue of other repo, eg: Closes otherUser/otherRepo#123, it can link to that issue too.

https://github.com/conventional-changelog/conventional-changelog-angular/blob/master/templates/commit.hbs#L26-L60

If we use the bugs entry, we won’t achieve this. We would have to do something like

bugs + issueNumber

We can’t parse bugs url because it could be any arbitrary url.