Issue links in pull request always point to the internal tracker #3305

New Issue

GiteaMirror · 2025-11-02T05:07:26-06:00

GiteaMirror commented

2025-11-02 05:07:26 -06:00

Originally created by @otbutz on GitHub (May 9, 2019).

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

Description

Mentioning an issue works properly in the main view of the repository. e.g a commit with #123 in its message properly links to our Redmine issue tracker.
But if i use the same format in the description or in a comment of a pull request, the link points to the deactivated internal issue tracker.

Originally created by @otbutz on GitHub (May 9, 2019).   - Gitea version (or commit ref): 1.8.0 - Git version: 2.21.0 - Operating system: Ubuntu 18.04 - Database (use `[x]`): - [x] PostgreSQL - [ ] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [x] No - [ ] Not relevant ## Description Mentioning an issue works properly in the main view of the repository. e.g a commit with `#123` in its message properly links to our Redmine issue tracker. But if i use the same format in the description or in a comment of a pull request, the link points to the deactivated internal issue tracker.

GiteaMirror added the issue/needs-feedback label 2025-11-02 05:07:26 -06:00

GiteaMirror closed this issue

2025-11-02 05:07:26 -06:00

GiteaMirror commented

2025-11-02 05:07:26 -06:00

@mrsdizzie commented on GitHub (May 9, 2019):

Can you reproduce this in an example (on try.gitea.io) or give an exact list of steps to reproduce? I've tried to reproduce but it appears to work fine:

https://try.gitea.io/mrsdizzie/test_issues/pulls/1#issuecomment-11512

@mrsdizzie commented on GitHub (May 9, 2019): Can you reproduce this in an example (on try.gitea.io) or give an exact list of steps to reproduce? I've tried to reproduce but it appears to work fine: https://try.gitea.io/mrsdizzie/test_issues/pulls/1#issuecomment-11512

GiteaMirror commented

2025-11-02 05:07:27 -06:00

@otbutz commented on GitHub (May 10, 2019):

I've already tried to reproduce it but it worked fine on the test server.

The funny thing is that it now seems to work after I switched the Issue Tracker back and forth. It still looks like an error to me, as the settings were correct, but the pull request web page behaved incorrectly in the browser of a coworker who had not yet visited the page.

@otbutz commented on GitHub (May 10, 2019): I've already tried to reproduce it but it worked fine on the test server. The funny thing is that it now seems to work after I switched the Issue Tracker back and forth. It still looks like an error to me, as the settings were correct, but the pull request web page behaved incorrectly in the browser of a coworker who had not yet visited the page.

GiteaMirror commented

2025-11-02 05:07:27 -06:00

@mrsdizzie commented on GitHub (May 10, 2019):

If you can reproduce it at all, let us know. Not saying there isn't possibly an error somewhere but without being able to see it there isn't anything to look at.

@mrsdizzie commented on GitHub (May 10, 2019): If you can reproduce it at all, let us know. Not saying there isn't possibly an error somewhere but without being able to see it there isn't anything to look at.

GiteaMirror commented

2025-11-02 05:07:27 -06:00

@otbutz commented on GitHub (May 13, 2019):

I'm going to report the issue if i can reproduce it again. So far no problems with 1.8.0 and 1.8.1

@otbutz commented on GitHub (May 13, 2019): I'm going to report the issue if i can reproduce it again. So far no problems with 1.8.0 and 1.8.1

GiteaMirror referenced this issue

2025-11-02 12:21:04 -06:00

[PR #3305] [MERGED] Serve .patch for pull requests #16873

Sign in to join this conversation.