github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-12 10:39:38 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

404 error on the left side of the /pulls page (external issue tracker) #3433

New Issue
Closed
opened 2025-11-02 05:12:50 -06:00 by GiteaMirror · 7 comments
GiteaMirror commented 2025-11-02 05:12:50 -06:00
Owner
Copy Link

Originally created by @mindfl on GitHub (Jun 5, 2019).

Description

404 error on the left side of the /pulls page if repo is configured with no issue tracker, or with an external issue tracker.

Similar issues

But the problem looks like still exists, or may be it's just a similar with closed issues.

Steps to reproduce

  1. Create a repository that is configured with no issue tracker, or with an external issue tracker
  2. Create a Pull Request
  3. Go to the https://try.gitea.io/pulls page
  4. Press on a link on a left side
  5. 404, but the filtered page like as repo with gitea internal issue tracker enabled is expected

Screenshots

Steps to reproduce

src_20190605-234302

Error

src_20190606-000424

Originally created by @mindfl on GitHub (Jun 5, 2019). - Gitea version (or commit ref): 1.9.0+dev-325-g59e6a7b97 (try.gitea.io), or stable 1.8.2, or old stable 1.8.1 - Git version: 2.7.4 - Operating system: Ubuntu 16.04 - Database (use `[x]`): - [ ] PostgreSQL - [x] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [x] Yes (https://try.gitea.io/pulls?type=all&repo=11986&sort=&state=open) - [ ] No - [ ] Not relevant - Log gist: - ## Description 404 error on the left side of the /pulls page if repo is configured with no issue tracker, or with an external issue tracker. ### Similar issues - https://github.com/go-gitea/gitea/issues/6302 - https://github.com/go-gitea/gitea/issues/5892 - https://github.com/go-gitea/gitea/issues/2447 - https://github.com/go-gitea/gitea/issues/1847 But the problem looks like still exists, or may be it's just a similar with closed issues. ### Steps to reproduce 1. Create a repository that is configured with no issue tracker, or with an external issue tracker 2. Create a Pull Request 3. Go to the https://try.gitea.io/pulls page 4. Press on a link on a left side 5. 404, but the filtered page like as repo with gitea internal issue tracker enabled is expected ## Screenshots ### Steps to reproduce ![src_20190605-234302](https://user-images.githubusercontent.com/7414997/58989036-bb3e5700-87eb-11e9-8fd4-66c7386da804.png) ### Error ![src_20190606-000424](https://user-images.githubusercontent.com/7414997/58990488-a9aa7e80-87ee-11e9-89e7-5d164efa47ba.png)
GiteaMirror added the issue/confirmedtype/bug labels 2025-11-02 05:12:50 -06:00
GiteaMirror commented 2025-11-02 05:12:50 -06:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Aug 5, 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 (Aug 5, 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 05:12:51 -06:00
Author
Owner
Copy Link

@Toxik1983 commented on GitHub (Jan 17, 2020):

This issue is still present in 1.10.2. Our team only uses external trackers, so these links are always broken. Please implement a fix.

@Toxik1983 commented on GitHub (Jan 17, 2020): This issue is still present in 1.10.2. Our team only uses external trackers, so these links are always broken. Please implement a fix.
GiteaMirror commented 2025-11-02 05:12:51 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Jan 17, 2020):

I think this is because you ever used internal issue tracker and then converted to external issue tracker. But this is a real bug that we should don't display those repositories which has external issue tracker enabled.

@lunny commented on GitHub (Jan 17, 2020): I think this is because you ever used internal issue tracker and then converted to external issue tracker. But this is a real bug that we should don't display those repositories which has external issue tracker enabled.
GiteaMirror commented 2025-11-02 05:12:51 -06:00
Author
Owner
Copy Link

@Toxik1983 commented on GitHub (Feb 12, 2020):

I think this is because you ever used internal issue tracker and then converted to external issue tracker.

I believe you are right. A lot of other projects work fine with a combination of PRs and external trackers. Isn't there some way to get rid of the old issue tracker data?

But this is a real bug that we should don't display those repositories which has external issue tracker enabled.

I don't think that is correct. The /pulls page should just be a list of PRs, at least in our case. But there is an internal dependency on issues, because the links to the PRs of other projects with an external tracker enabled point to [organization]/[project]/issues/[id] but actually just redirect to [organization]/[project]/pulls/[id].

@Toxik1983 commented on GitHub (Feb 12, 2020): > I think this is because you ever used internal issue tracker and then converted to external issue tracker. I believe you are right. A lot of other projects work fine with a combination of PRs and external trackers. Isn't there some way to get rid of the old issue tracker data? > But this is a real bug that we should don't display those repositories which has external issue tracker enabled. I don't think that is correct. The /pulls page should just be a list of PRs, at least in our case. But there is an internal dependency on issues, because the links to the PRs of other projects with an external tracker enabled point to [organization]/[project]/issues/[id] but actually just redirect to [organization]/[project]/pulls/[id].
GiteaMirror commented 2025-11-02 05:12:51 -06:00
Author
Owner
Copy Link

@guillep2k commented on GitHub (Feb 12, 2020):

This may have been fixed in #10092

@guillep2k commented on GitHub (Feb 12, 2020): This may have been fixed in #10092
GiteaMirror commented 2025-11-02 05:12:51 -06:00
Author
Owner
Copy Link

@Toxik1983 commented on GitHub (Feb 13, 2020):

This may have been fixed in #10092

Thanks for mentioning this, I'll keep an eye on the release logs and update when it's available.

@Toxik1983 commented on GitHub (Feb 13, 2020): > This may have been fixed in #10092 Thanks for mentioning this, I'll keep an eye on the release logs and update when it's available.
GiteaMirror commented 2025-11-02 05:12:52 -06:00
Author
Owner
Copy Link

@Toxik1983 commented on GitHub (Feb 14, 2020):

This may have been fixed in #10092

Thanks for mentioning this, I'll keep an eye on the release logs and update when it's available.

Somehow I missed this in the 1.11.0 release log. I updated this morning and can confirm that this has been fixed.

@Toxik1983 commented on GitHub (Feb 14, 2020): > > This may have been fixed in #10092 > > Thanks for mentioning this, I'll keep an eye on the release logs and update when it's available. Somehow I missed this in the 1.11.0 release log. I updated this morning and can confirm that this has been fixed.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label issue/confirmed type/bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#3433
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?