object_attributes.action field is missing from test payload for Issues and Confidential issues events
Summary
object_attributes.action field is missing from test payload for Issues and Confidential issues events
Steps to reproduce
Make sure you have at least one issue. In project, select Settings->Integrations, create a new webhook. After hook is created, select Test->Issues events.
What is the current bug behavior?
Payload that is sent:
{
"object_kind": "issue",
"user": {
"name": "Administrator",
"username": "root",
"avatar_url": "http://www.gravatar.com/avatar/e64c7d89f26bd1972efa854d13d7dd61?s=80\u0026d=identicon"
},
"project": {
"name": "test1",
"description": "",
"web_url": "http://localhost/root/test1",
"avatar_url": null,
"git_ssh_url": "git@localhost:root/test1.git",
"git_http_url": "http://localhost/root/test1.git",
"namespace": "root",
"visibility_level": 10,
"path_with_namespace": "root/test1",
"default_branch": null,
"ci_config_path": null,
"homepage": "http://localhost/root/test1",
"url": "git@localhost:root/test1.git",
"ssh_url": "git@localhost:root/test1.git",
"http_url": "http://localhost/root/test1.git"
},
"object_attributes": {
"id": 1,
"title": "test issue1",
"assignee_id": 1,
"author_id": 1,
"project_id": 1,
"created_at": "2017-11-17T13:59:48.158Z",
"updated_at": "2017-11-17T14:11:20.109Z",
"branch_name": null,
"description": "desc123",
"milestone_id": null,
"state": "opened",
"iid": 1,
"updated_by_id": 1,
"weight": null,
"confidential": true,
"deleted_at": null,
"due_date": null,
"moved_to_id": null,
"lock_version": 2,
"time_estimate": 0,
"relative_position": 1073742323,
"closed_at": "2017-11-17T14:11:14.301Z",
"service_desk_reply_to": null,
"last_edited_at": "2017-11-17T14:10:16.000Z",
"last_edited_by_id": 1,
"discussion_locked": null,
"total_time_spent": 0,
"human_total_time_spent": null,
"human_time_estimate": null,
"assignee_ids": [
1
]
},
"labels": [],
"repository": {
"name": "test1",
"url": "git@localhost:root/test1.git",
"description": "",
"homepage": "http://localhost/root/test1"
},
"assignees": [
{
"name": "Administrator",
"username": "root",
"avatar_url": "http://www.gravatar.com/avatar/e64c7d89f26bd1972efa854d13d7dd61?s=80\u0026d=identicon"
}
]
}
What is the expected correct behavior?
According to documentation https://docs.gitlab.com/ee/user/project/integrations/webhooks.html#issues-events there should be action field in object_attributes. It's present in real payloads, only missing from test requests.
Relevant logs and/or screenshots
Output of checks
Results of GitLab environment info
Expand for output related to GitLab environment info
System information System: Ubuntu 16.04 Proxy: no Current User: git Using RVM: no Ruby Version: 2.3.5p376 Gem Version: 2.6.13 Bundler Version:1.13.7 Rake Version: 12.1.0 Redis Version: 3.2.5 Git Version: 2.13.6 Sidekiq Version:5.0.4 Go Version: unknown
GitLab information Version: 10.1.4-ee Revision: a512054 Directory: /opt/gitlab/embedded/service/gitlab-rails DB Adapter: postgresql DB Version: 9.6.5 URL: http://localhost HTTP Clone URL: http://localhost/some-group/some-project.git SSH Clone URL: git@localhost:some-group/some-project.git Elasticsearch: no Geo: no Using LDAP: no Using Omniauth: no
GitLab Shell Version: 5.9.3 Repository storage paths:
- default: /var/opt/gitlab/git-data/repositories Hooks: /opt/gitlab/embedded/service/gitlab-shell/hooks Git: /opt/gitlab/embedded/bin/git
Results of GitLab application Check
Expand for output related to the GitLab application check
Checking GitLab Shell ...
GitLab Shell version >= 5.9.3 ? ... OK (5.9.3) Repo base directory exists? default... yes Repo storage directories are symlinks? default... no Repo paths owned by git:root, or git:git? default... yes Repo paths access is drwxrws---? default... yes hooks directories in repos are links: ... 1/1 ... repository is empty Running /opt/gitlab/embedded/service/gitlab-shell/bin/check Check GitLab API access: OK Redis available via internal API: OK
Access to /var/opt/gitlab/.ssh/authorized_keys: OK gitlab-shell self-check successful
Checking GitLab Shell ... Finished
Checking Sidekiq ...
Running? ... yes Number of Sidekiq processes ... 1
Checking Sidekiq ... Finished
Reply by email is disabled in config/gitlab.yml Checking LDAP ...
LDAP is disabled in config/gitlab.yml
Checking LDAP ... Finished
Checking GitLab ...
Git configured correctly? ... yes Database config exists? ... yes All migrations up? ... yes Database contains orphaned GroupMembers? ... no GitLab config exists? ... yes GitLab config up to date? ... yes Log directory writable? ... yes Tmp directory writable? ... yes Uploads directory exists? ... yes Uploads directory has correct permissions? ... yes Uploads directory tmp has correct permissions? ... skipped (no tmp uploads folder yet) Init script exists? ... skipped (omnibus-gitlab has no init script) Init script up-to-date? ... skipped (omnibus-gitlab has no init script) Projects have namespace: ... 1/1 ... yes Redis version >= 2.8.0? ... yes Ruby version >= 2.3.3 ? ... yes (2.3.5) Git version >= 2.7.3 ? ... yes (2.13.6) Git user has default SSH configuration? ... yes Active users: ... 2 Elasticsearch version 5.1 - 5.5? ... skipped (elasticsearch is disabled)
Checking GitLab ... Finished