-
Notifications
You must be signed in to change notification settings - Fork 127
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
Add Support Additional Events #6
Comments
Comments - yes, Work Log - no. The issue with worklog hooks is that there does not appear to be enough data in the webhook message, so we need to go with Oauth/API to get more details (like the issue key - the message only seems to include the issue ID) |
How about changes of the issue priority? And how about direct messages, if the issue gets assigned to someone? |
Yes
The "re-assigned" events are now supported, but no user mapping is performed yet, so the new assignee appears in the post by JIRA name; One could set up notifications to be triggered by that, but may be kind of spammy. |
To summarize the conversation
This has been added with #22, and scheduled for Jira v2.0 release.
Not planned, but I've opened a help wanted ticket. We welcome contributions to add support for these events.
This is planned to be supported by a new Jira subscription feature, scheduled for Jira v2.1 release. The subscription feature was started with #61, and we have a Jira ticket to include issue priority notifications as part of this feature (see https://mattermost.atlassian.net/browse/MM-15678).
This has been added with #62, along with a slash command ( The feature is scheduled for Jira v2.1 release If you are wondering about dates for Jira v2 releases, see the latest timelines here: https://github.com/mattermost/mattermost-plugin-jira#2-jira-plugin-v2-roadmap |
Thank you all for the feedback! I'll close the issue based on the response above, and we'll track the outstanding items via
If you have any questions, don't hesitate to let me know! |
I'm interested in adding support for additional events and looking for feedback. I'd love to see support for:
The text was updated successfully, but these errors were encountered: