The timetracker will not be stop from a issue reference in the message of a PR #5379

New Issue

GiteaMirror · 2025-11-02T06:23:03-06:00

GiteaMirror commented

2025-11-02 06:23:03 -06:00

Originally created by @luwol03 on GitHub (May 11, 2020).

Gitea version (or commit ref): 99082eebd7 = ~ v1.12.0
Git version: 2.20.1
Operating system: Linux Debian Buster
Database (use [x]):
- PostgreSQL
- MySQL
- MSSQL
- SQLite
Can you reproduce the bug at https://try.gitea.io:
- Yes (https://try.gitea.io/luwol03/test/issues/1)
- No
- Not relevant
Log gist:

Description

the time tracker will be stoped, if I refer a issue in a pr commit message. But if I close a issue via refer it in a pr message it will not be closed!

Screenshots

Originally created by @luwol03 on GitHub (May 11, 2020). - Gitea version (or commit ref): 99082eebd76019fc608e44c4464da6398f51dccd = ~ v1.12.0 - Git version: 2.20.1 - Operating system: Linux Debian Buster - Database (use `[x]`): - [ ] PostgreSQL - [x] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [x] Yes (https://try.gitea.io/luwol03/test/issues/1) - [ ] No - [ ] Not relevant - Log gist: ## Description the time tracker will be stoped, if I refer a issue in a pr commit message. But if I close a issue via refer it in a pr message it will not be closed! ## Screenshots ![image](https://user-images.githubusercontent.com/60048565/81560976-bcc8b580-9392-11ea-9d39-97004fd4170c.png)

GiteaMirror added the issue/confirmed outdated/theme/timetracker type/bug labels 2025-11-02 06:23:03 -06:00

GiteaMirror closed this issue

2025-11-02 06:23:03 -06:00

GiteaMirror commented

2025-11-02 06:23:04 -06:00

@stale[bot] commented on GitHub (Jul 11, 2020):

This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

@stale[bot] commented on GitHub (Jul 11, 2020): This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

GiteaMirror commented

2025-11-02 06:23:04 -06:00

@luwol03 commented on GitHub (Nov 21, 2021):

Thank you for fixing that bug. I appreciate your work.

@luwol03 commented on GitHub (Nov 21, 2021): Thank you for fixing that bug. I appreciate your work.

GiteaMirror commented

2025-11-02 06:23:04 -06:00

@lunny commented on GitHub (Nov 21, 2021):

Sorry for so long time to fix it. Look like the backport is difficult. I will send another PR to v1.15

@lunny commented on GitHub (Nov 21, 2021): Sorry for so long time to fix it. Look like the backport is difficult. I will send another PR to v1.15

GiteaMirror referenced this issue

2025-11-02 15:40:14 -06:00