Do you have an example commit?

I would say, supporting arbitrary pattern as a issue link would be very useful here, so not only hard-coding to Gitlab/Github issues.

For example, some organisations use exteral issue tracking systems. Linking to those would make a lot of sens and help in adoption.

Proposal

The arbitrary, user-defined URL scheme could be given as a config key, perhaps templated with {issue_number} placeholder like this:

// in pyproject.toml
external_issue_url = "http://some.url.com/browse/{issuse_number}"

The following example commit, could then be supported:

    fix: No more process hang on bad inputs.

    Input data is validated before being passed down to executor. This also addresses input validation request.

    Fixes #FOO-123, #FOO-456

ideally producing hyperlinks to these issues respectively in the changelog:

...
* No more process hang on bad inputs [FOO-123](http://some.url.com/browse/FOO-123), [FOO-123](http://some.url.com/browse/FOO-123)
...

It would make sense, for the tool to use build-in defaults URL scheme for GitHub and GitLab issues, but when IT IS set, then a custom URL pattern should kick in.

It has been 60 days since the last update on this confirmed issue. @python-semantic-release/team can you provide an update on the status of this issue?

A redesign is in progress to hopefully address this sooner than later. Likely a few more months though.

It has been 60 days since the last update on this confirmed issue. @python-semantic-release/team can you provide an update on the status of this issue?

Still in the backlog.

It has been 60 days since the last update on this confirmed issue. @python-semantic-release/team can you provide an update on the status of this issue?

Should be completed in the next few weeks.

🎉 This issue has been resolved in version 9.15.0 🎉

The release is available on:

• PyPi package
• GitHub release

Since this issue has been open for so long, there have been some significant changes in PSR since. I do believe this is as close as we can get it to resolution of the original request. v9.15.0 provides a parsing mechanism to extract the issue numbers into the resulting ParsedCommit objects. Then with custom changelogs you are able to use the ParsedCommit object's linked_issues attribute to extract link references. From there, you can pass those values to the VCS's issue_url filter to generate the URL for whichever format you desire. I have included an example of this on the Changelog Templates page under the issue_url filter details. I have not added any formatting to the default changelog to identify closed issues though so right now it is only available to people whom write their own custom changelogs.

There is a future endeavor to post updates to issues and prs #975 which I think will hammer out any details related to separate issue tracking systems outside of the configured remote VCS.