Missing project name for webhook #358

Closed
opened 2025-11-01 20:54:55 -05:00 by GiteaMirror · 5 comments
Owner

Originally created by @jon4god on GitHub (Feb 19, 2025).

Description

I can't find anywhere the name of the project that uses webhook. Is this in principle not provided or should there be a name instead of "project"?

[subscription] => Array
                        (
                            [id] => 8
                            [entity] => project
                            [entity_id] => 1
                            [created] => 2025-01-28T11:54:20Z
                        )

I would like to add it if it is missing or correct it if it is not displayed.

Vikunja Version

v0.24.6

Browser and version

No response

Can you reproduce the bug on the Vikunja demo site?

Please select

Screenshots

No response

Originally created by @jon4god on GitHub (Feb 19, 2025). ### Description I can't find anywhere the name of the project that uses webhook. Is this in principle not provided or should there be a name instead of "project"? ``` [subscription] => Array ( [id] => 8 [entity] => project [entity_id] => 1 [created] => 2025-01-28T11:54:20Z ) ``` I would like to add it if it is missing or correct it if it is not displayed. ### Vikunja Version v0.24.6 ### Browser and version _No response_ ### Can you reproduce the bug on the Vikunja demo site? Please select ### Screenshots _No response_
Author
Owner

@kolaente commented on GitHub (Feb 21, 2025):

Do you mean a webhook or a subscription?

@kolaente commented on GitHub (Feb 21, 2025): Do you mean a webhook or a subscription?
Author
Owner

@jon4god commented on GitHub (Feb 21, 2025):

Webhook. I just took the part from the answer where theoretically the project name could have been specified.
Although the part where the task is specified can be used for this purpose as well.

For example, adding

[project_name] => ...

[task] => Array
                (
                    [id] => 192
                    [title] => Тест отправки в телегу
                    [description] => <p></p>
                    [done] => 
                    [done_at] => 0001-01-01T00:00:00Z
                    [due_date] => 0001-01-01T00:00:00Z
                    [reminders] => 
                    [project_id] => 6
                    ...
                )
@jon4god commented on GitHub (Feb 21, 2025): Webhook. I just took the part from the answer where theoretically the project name could have been specified. Although the part where the task is specified can be used for this purpose as well. For example, adding [project_name] => ... ``` [task] => Array ( [id] => 192 [title] => Тест отправки в телегу [description] => <p></p> [done] => [done_at] => 0001-01-01T00:00:00Z [due_date] => 0001-01-01T00:00:00Z [reminders] => [project_id] => 6 ... ) ```
Author
Owner

@kolaente commented on GitHub (Feb 21, 2025):

The payload depends on the event. Which are you using?

@kolaente commented on GitHub (Feb 21, 2025): The payload depends on the event. Which are you using?
Author
Owner

@jon4god commented on GitHub (Feb 21, 2025):

I'm adding a task to a project, and when I add the person responsible for it via webhook with task.assignee.created, I send a message to telegram.
Now I need to send from different projects, and I don't see where to get the project name information. Only its id.

@jon4god commented on GitHub (Feb 21, 2025): I'm adding a task to a project, and when I add the person responsible for it via webhook with task.assignee.created, I send a message to telegram. Now I need to send from different projects, and I don't see where to get the project name information. Only its id.
Author
Owner

@kolaente commented on GitHub (Feb 21, 2025):

Ah, now I see.

I've implemented always adding the project to the payload in 70e1fdae9 - please check with the next unstable build (should be ready for deployment in ~45min, also on try).

@kolaente commented on GitHub (Feb 21, 2025): Ah, now I see. I've implemented always adding the project to the payload in 70e1fdae9 - please check with the next unstable build (should be ready for deployment in ~45min, also on [try](https://try.vikunja.io)).
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vikunja#358