-
Notifications
You must be signed in to change notification settings - Fork 156
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
API call to create playbook run does not respect the option to attach to existing channel #1800
Comments
I'm having the same issue |
The same for me, after creating new run via REST API it became linked to the new channel with run's name. |
Same here, even providing the same name, two identical channels are created, and when providing a post_id it "quotes" the previous post inside the new channel, far from ideal. |
@bizlabs @tomcat77 @shalalalaw
Cheers. |
@AndresJ551 |
Summary
Mattermost 7.7 introduces the option to link a playbook to an existing channel instead of creating a new channel. This works fine when creating a playbook run interactively from the web console but not when playbook run created from API.
Steps to reproduce in mattermost 7.7.1 enterprise
Go to Playbooks and create a playbook or select an existing one
Select "Link to an existing channel" under "Actions" and select a channel.
Create a playbook run using the following api call
POST 'http://localhost:8065/plugins/playbooks/api/v0/runs' {body}
playbook run and a new channel is created with same name and linked. The run is not linked to the requested link channel.
optionally, verify playbook is valid by creating a run interactively with the blue "run" button at top right of playbook page and verify that new run is linked to the channel requested in step 2.
Expected behavior
expected that the new playbook run will be linked to the existing channel requested in step 2 above.
Observed behavior (that appears unintentional)
no error message. Just doesn't link the playbook run to the expected channel
The text was updated successfully, but these errors were encountered: