forgejo/services/issue
Ashley Nelson e504410708
Update milestone counters when issue is deleted (#21459) (#21586)
Backports #21459 

When actions besides "delete" are performed on issues, the milestone
counter is updated. However, since deleting issues goes through a
different code path, the associated milestone's count wasn't being
updated, resulting in inaccurate counts until another issue in the same
milestone had a non-delete action performed on it.

I verified this change fixes the inaccurate counts using a local docker
build.

Co-authored-by: 6543 <6543@obermui.de>
2022-10-26 15:44:05 +08:00
..
assignee.go Move issues related files into models/issues (#19931) 2022-06-13 17:37:59 +08:00
assignee_test.go Move issues related files into models/issues (#19931) 2022-06-13 17:37:59 +08:00
commit.go Move issues related files into models/issues (#19931) 2022-06-13 17:37:59 +08:00
commit_test.go Move issues related files into models/issues (#19931) 2022-06-13 17:37:59 +08:00
content.go Move issues related files into models/issues (#19931) 2022-06-13 17:37:59 +08:00
issue.go Update milestone counters when issue is deleted (#21459) (#21586) 2022-10-26 15:44:05 +08:00
issue_test.go Move issues related files into models/issues (#19931) 2022-06-13 17:37:59 +08:00
label.go Move issues related files into models/issues (#19931) 2022-06-13 17:37:59 +08:00
label_test.go Move issues related files into models/issues (#19931) 2022-06-13 17:37:59 +08:00
main_test.go Use a struct as test options (#19393) 2022-04-14 21:58:21 +08:00
milestone.go Check if project has the same repository id with issue when assign project to issue (#20133) (#20188) 2022-07-01 15:00:05 +02:00
milestone_test.go Move issues related files into models/issues (#19931) 2022-06-13 17:37:59 +08:00
status.go Move issues related files into models/issues (#19931) 2022-06-13 17:37:59 +08:00