Skip to content

Uninitialized "created_at" field in webhook when creating an issue #34401

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
kim2048 opened this issue May 8, 2025 · 1 comment
Open

Uninitialized "created_at" field in webhook when creating an issue #34401

kim2048 opened this issue May 8, 2025 · 1 comment

Comments

@kim2048
Copy link

kim2048 commented May 8, 2025

Description

Hello,
when I create an issue via web ui with a label and an assignee I get 3 webhook calls in this order: assigned, opened, label_updated. I don't know if I could expect a specific order here, but it's fine.

The assigned issue json already contains all the issue data (user, assignee, my label, state, ...) except the created_at and updated_at fields: They contain a 0 epoch ("1970-01-01T01:00:00+01:00") and have only correct values in the opened and label_updated json (all other fields are the same in all 3 calls).

My assumption was, that I would never get an "uninitialized" created_at field in any webhook issue value. Am I right?

Gitea Version

1.23.7

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

No response

Git Version

No response

Operating System

No response

How are you running Gitea?

I don't know

Database

None

@kim2048 kim2048 changed the title Wrong webhook order when creating an issue Uninitialized "created_at" field in webhook when creating an issue May 8, 2025
@lunny
Copy link
Member

lunny commented May 10, 2025

I created #34420 and could not reproduce it in main branch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants