Allow custom regex patterns for linking external issues #1507

New Issue

GiteaMirror · 2025-11-02T04:03:07-06:00

GiteaMirror commented

2025-11-02 04:03:07 -06:00

Originally created by @tgdchmi2 on GitHub (Feb 7, 2018).

Gitea version (or commit ref): 1.3.2
Git version: 2.16.1
Operating system: Linux
Database (use [x]):
- PostgreSQL
- MySQL
- MSSQL
- SQLite
Can you reproduce the bug at https://try.gitea.io:
- Yes (provide example URL)
- No
- Not relevant
Log gist:

Description

For external issue tracker: alphanumeric issue recognition does not work when:

Key before the dash contains a number. Example: BLG5-456
Key is enclosed in quotes. Example: 'BLG-456' or "BLG-456"
Key follows a slash: Example BLG-123/BLG-564 (first key is recognized, second one not)

We think implementing so many additional 'rules' could lead to many false positives.
Thus we propose to add a third External Issue Tracker Naming Style for specifying custom patterns to apply for matching issue keys. Then we could specify a pattern like (WP-\d+)|(BLG5-\d+) ourselves.
The matched group should then be used for replacing {index} in the External Issue Tracker URL Format.

Originally created by @tgdchmi2 on GitHub (Feb 7, 2018).  - Gitea version (or commit ref): 1.3.2 - Git version: 2.16.1 - Operating system: Linux - Database (use `[x]`): - [x] PostgreSQL - [ ] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [x] Yes (provide example URL) - [ ] No - [ ] Not relevant - Log gist: ## Description For external issue tracker: alphanumeric issue recognition does not work when: - Key before the dash contains a number. Example: `BLG5-456` - Key is enclosed in quotes. Example: `'BLG-456'` or `"BLG-456"` - Key follows a slash: Example `BLG-123/BLG-564` (first key is recognized, second one not) We think implementing so many additional 'rules' could lead to many false positives. Thus we propose to add a third _External Issue Tracker Naming Style_ for specifying custom patterns to apply for matching issue keys. Then we could specify a pattern like `(WP-\d+)|(BLG5-\d+)` ourselves. The matched group should then be used for replacing `{index}` in the _External Issue Tracker URL Format_.

GiteaMirror added the issue/confirmed type/feature type/enhancement labels 2025-11-02 04:03:07 -06:00

GiteaMirror closed this issue

2025-11-02 04:03:07 -06:00

GiteaMirror commented

2025-11-02 04:03:08 -06:00

@stale[bot] commented on GitHub (Feb 8, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Feb 8, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

GiteaMirror commented

2025-11-02 04:03:08 -06:00

@strk commented on GitHub (May 30, 2019):

See also #7084 for an even more flexible mapping idea

@strk commented on GitHub (May 30, 2019): See also #7084 for an even more flexible mapping idea

GiteaMirror commented

2025-11-02 04:03:08 -06:00

@jonny64 commented on GitHub (Nov 18, 2020):

Hi, we have tasks/{uuid v4} as issue {index}, what should we do?

@jonny64 commented on GitHub (Nov 18, 2020): Hi, we have tasks/{uuid v4} as issue {index}, what should we do?

GiteaMirror referenced this issue

2025-11-02 11:58:18 -06:00