Webhook sends wrong milestone in issue milestone change triggered message. #5350

Closed
opened 2025-11-02 06:22:16 -06:00 by GiteaMirror · 0 comments
Owner

Originally created by @chriseaton on GitHub (May 4, 2020).

  • Gitea version (or commit ref): 1.11.4
  • Git version: 1.8.3.1
  • Operating system: CentOS 7
  • Database (use [x]):
    • PostgreSQL
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes

Description

When changing the milestone of an issue, the webhook sends the old milestone on the issue instead of the new one.

Example:

  1. Issue is assigned to Milestone A.
  2. User changes issue to Milestone B.
  3. A webhook message is sent saying:

[project] Issue milestoned to Milestone A [issue name] by [user]

The language indicates what the issue was changed to, instead shows what it was changed from.

Expected result:
A webhook message is sent saying:

[project] Issue milestoned to Milestone B [issue name] by [user]

Originally created by @chriseaton on GitHub (May 4, 2020). - Gitea version (or commit ref): 1.11.4 - Git version: 1.8.3.1 - Operating system: CentOS 7 - Database (use `[x]`): - [x] PostgreSQL - Can you reproduce the bug at https://try.gitea.io: - [x] Yes ## Description When changing the milestone of an issue, the webhook sends the old milestone on the issue instead of the new one. Example: 1. Issue is assigned to Milestone A. 1. User changes issue to Milestone B. 1. A webhook message is sent saying: > [project] Issue milestoned to **Milestone A** [issue name] by [user] The language indicates what the issue was changed _to_, instead shows what it was changed _from_. **Expected result:** A webhook message is sent saying: > [project] Issue milestoned to **Milestone B** [issue name] by [user]
GiteaMirror added the type/bug label 2025-11-02 06:22:16 -06:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#5350