Open Issue Counter becomes offset #5523

New Issue

2025-11-02T06:27:46-06:00

GiteaMirror commented

2025-11-02 06:27:46 -06:00

Originally created by @alexander-zierhut on GitHub (Jun 9, 2020).

Gitea version (or commit ref): 1.11.6 (I also had that in older versions)
Git version: /
Operating system: Ubuntu 18.04
Database:
- PostgreSQL
- MySQL
- MSSQL
- SQLite
Can you reproduce the bug at https://try.gitea.io:
- Yes: https://try.gitea.io/Alexzz/issue-confirm/issues
- No
- Not relevant
Log gist: /

Description

When closing issues using a commit message, for example Changed some stuff Closes #1 Closes #2, the open issue count does not change to portrait the new changes. This fixes itself when closing another issue manually using the webinterface.

Screenshots

try.gitea.io	Private installation

Originally created by @alexander-zierhut on GitHub (Jun 9, 2020). - Gitea version (or commit ref): 1.11.6 (I also had that in older versions) - Git version: / - Operating system: Ubuntu 18.04 - Database: - [ ] PostgreSQL - [x] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [x] Yes: https://try.gitea.io/Alexzz/issue-confirm/issues - [ ] No - [ ] Not relevant - Log gist: / ## Description When closing issues using a commit message, for example `Changed some stuff Closes #1 Closes #2`, the open issue count does not change to portrait the new changes. This fixes itself when closing another issue manually using the webinterface. ## Screenshots | try.gitea.io | Private installation | |---|---| | ![image](https://user-images.githubusercontent.com/26348781/84170886-71312680-aa7a-11ea-9426-aa7cf5c2c3c9.png) | ![image](https://user-images.githubusercontent.com/26348781/84170941-81490600-aa7a-11ea-8ef5-18f2d75a3602.png) |

GiteaMirror added the issue/duplicate label 2025-11-02 06:27:46 -06:00

GiteaMirror closed this issue

2025-11-02 06:27:46 -06:00

GiteaMirror commented

2025-11-02 06:27:47 -06:00

@alexander-zierhut commented on GitHub (Jul 26, 2020):

This still exists in the newest version I have updated to.

@alexander-zierhut commented on GitHub (Jul 26, 2020): This still exists in the newest version I have updated to.

GiteaMirror commented

2025-11-02 06:27:47 -06:00

@iamdoubz commented on GitHub (Sep 17, 2020):

I have this issue in 1.12.4. But, if I close the issue with a pull request in the web interface, the number is not correct until I restart the server then the number is correct.

@iamdoubz commented on GitHub (Sep 17, 2020): I have this issue in 1.12.4. But, if I close the issue with a pull request in the web interface, the number is not correct until I `restart the server` then the number is correct.

GiteaMirror commented

2025-11-02 06:27:47 -06:00

@warnat commented on GitHub (Sep 17, 2020):

There is a cron (?) job running every 24 hours, to correct that value. The function is called CheckRepoStats.
In the Administration->Monitoring, there is a button for that: "Check all repository statistics".
I must admit, that I cannot find the root cause for the problem.

@warnat commented on GitHub (Sep 17, 2020): There is a cron (?) job running every 24 hours, to correct that value. The function is called CheckRepoStats. In the Administration->Monitoring, there is a button for that: "Check all repository statistics". I must admit, that I cannot find the root cause for the problem.

GiteaMirror commented

2025-11-02 06:27:47 -06:00

@alexander-zierhut commented on GitHub (Sep 17, 2020):

There is a cron (?) job running every 24 hours, to correct that value I was going to mention that as the server does not have to be restarted to fix this problem. It gets fixed after sometime.

@alexander-zierhut commented on GitHub (Sep 17, 2020): `There is a cron (?) job running every 24 hours, to correct that value` I was going to mention that as the server does not have to be restarted to fix this problem. It gets fixed after sometime.

GiteaMirror commented

2025-11-02 06:27:48 -06:00

@alexander-zierhut commented on GitHub (Sep 18, 2020):

I cannot find the root cause for the problem. @warnat Have you thought about a caching issue?

@alexander-zierhut commented on GitHub (Sep 18, 2020): ` I cannot find the root cause for the problem.` @warnat Have you thought about a caching issue?

GiteaMirror commented

2025-11-02 06:27:48 -06:00