Support both numeric and alphanumeric External Issue Tracker Number Format #8095

Open
opened 2025-11-02 07:53:47 -06:00 by GiteaMirror · 2 comments
Owner

Originally created by @strk on GitHub (Nov 12, 2021).

Feature Description

We recently decided to move to a new issue tracker but the git repository is full of numeric issue tracker numbers, like #1012.
In order to distinguish, in history, between the old tracker and the new tracker, we plan to use NT-10 syntax but the current repository settings for Gitea only allows either Numeric or Alphanumeric, not both, so if we enable Alphanumeric the #1012references will stop working.

I do like the fact that when Alphanumeric is enabled the external tracker also receives the alphabetic part of the reference (so it can redirect the user to the appropriate tracker) but unless the #1012 old references turn to links, we're missing links from the historical tracker.

This issue is to allow rendering both syntaxes, passing the whole information to the external tracker.

Screenshots

No response

Originally created by @strk on GitHub (Nov 12, 2021). ### Feature Description We recently decided to move to a new issue tracker but the git repository is full of numeric issue tracker numbers, like `#1012`. In order to distinguish, in history, between the old tracker and the new tracker, we plan to use `NT-10` syntax but the current repository settings for Gitea only allows either Numeric or Alphanumeric, not both, so if we enable Alphanumeric the `#1012`references will stop working. I do like the fact that when Alphanumeric is enabled the external tracker also receives the alphabetic part of the reference (so it can redirect the user to the appropriate tracker) but unless the `#1012` old references turn to links, we're missing links from the historical tracker. This issue is to allow rendering *both* syntaxes, passing the whole information to the external tracker. ### Screenshots _No response_
GiteaMirror added the type/proposal label 2025-11-02 07:53:47 -06:00
Author
Owner

@lunny commented on GitHub (Nov 12, 2021):

Looks like complicated.

@lunny commented on GitHub (Nov 12, 2021): Looks like complicated.
Author
Owner

@strk commented on GitHub (Nov 12, 2021):

Isn't #4265 going in that direction ?

@strk commented on GitHub (Nov 12, 2021): Isn't #4265 going in that direction ?
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#8095