You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In JiraIssueEventRenderer#renderStandardNotification, the visitCreated() method doesn't include the issue description in either the Slack chat text, or the attachment.
Ideally, this would function like visitCommented() does, in that the description would be part of the attachment if extended verbosity is on, and part of the text if not.
But in any case, getting a Slack notification for a new issue is currently often unhelpful, because most of the issue context tends to be in the description, not the summary/title. Also note that the Jira Cloud Slack plugin does include the description, so there should be parity between the two.
The text was updated successfully, but these errors were encountered:
Thanks for an idea! Current design of the issue notifications was intentionally designed to be different from the Cloud version to reduce verbosity. We are happy to accept PRs for this change though by adding a new verbosity level - Verbose (for instance).
In
JiraIssueEventRenderer#renderStandardNotification
, thevisitCreated()
method doesn't include the issue description in either the Slack chat text, or the attachment.Ideally, this would function like
visitCommented()
does, in that the description would be part of the attachment if extended verbosity is on, and part of the text if not.But in any case, getting a Slack notification for a new issue is currently often unhelpful, because most of the issue context tends to be in the description, not the summary/title. Also note that the Jira Cloud Slack plugin does include the description, so there should be parity between the two.
The text was updated successfully, but these errors were encountered: