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

Migrated issues do not get indexed, search does not work #4479

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

Originally created by @ashimokawa on GitHub (Dec 12, 2019).

Description

Migrated issues do not get indexed, search does not work, examples are
https://try.gitea.io/mrsdizzie/Pix-Art-Messenger, when you search for something in the issues there is no result.

https://try.gitea.io/mrsdizzie/Pix-Art-Messenger/issues?type=all&state=open&labels=0&milestone=0&assignee=0&q=Problems

Commenting to an imported issue, seems to trigger indexing for the specific issue.
If you search in our fully migrated Gadgetbridge issues (yes we left github), and search for "Move" you will find one issue because I commented there after the move. Serching for anything else eg. "Pebble" fails.

https://codeberg.org/Freeyourgadget/Gadgetbridge/issues

Is there any way to trigger issue indexing manually?

Originally created by @ashimokawa on GitHub (Dec 12, 2019). - Gitea version (or commit ref): 1.10.1+git, also master - Git version: 2.20.1 - Operating system: Debian 10 - Database (use `[x]`): - [ ] PostgreSQL - [x] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [x] Yes https://try.gitea.io/mrsdizzie/Pix-Art-Messenger/issues?type=all&state=open&labels=0&milestone=0&assignee=0&q=Problems - [ ] No - [ ] Not relevant - Log gist: ## Description Migrated issues do not get indexed, search does not work, examples are https://try.gitea.io/mrsdizzie/Pix-Art-Messenger, when you search for something in the issues there is no result. https://try.gitea.io/mrsdizzie/Pix-Art-Messenger/issues?type=all&state=open&labels=0&milestone=0&assignee=0&q=Problems Commenting to an imported issue, seems to trigger indexing for the specific issue. If you search in our fully migrated Gadgetbridge issues (yes we left github), and search for "Move" you will find one issue because I commented there after the move. Serching for anything else eg. "Pebble" fails. https://codeberg.org/Freeyourgadget/Gadgetbridge/issues Is there any way to trigger issue indexing manually?
GiteaMirror added the type/bug label 2025-11-02 05:52:11 -06:00
GiteaMirror commented 2025-11-02 05:52:12 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Dec 12, 2019):

Currently no manually method to reindex issues per repository. It can only be triggered when you deleted all the issue indexers and restart gitea. Or any change to the issue.

@lunny commented on GitHub (Dec 12, 2019): Currently no manually method to reindex issues per repository. It can only be triggered when you deleted all the issue indexers and restart gitea. Or any change to the issue.
GiteaMirror commented 2025-11-02 05:52:12 -06:00
Author
Owner
Copy Link

@ashimokawa commented on GitHub (Dec 12, 2019):

@lunny
Thanks! That worked :)

@ashimokawa commented on GitHub (Dec 12, 2019): @lunny Thanks! That worked :)
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 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#4479
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?