Opened 4 years ago
Closed 4 years ago
#5446 closed defect (bug) (invalid)
Can keywords be added to the Trac>Slack integration for #ticket unfurling
| Reported by: |
|
Owned by: | |
|---|---|---|---|
| Milestone: | Priority: | normal | |
| Component: | Communication (Matrix, Slack, IRC) | Keywords: | has-screenshots |
| Cc: |
Description
A thought to help bugscrubbers is to include the keywords on the unfurl when a ticket number is mentioned. In many cases the scrubbers main focus is to apply the correct keywords so displaying them without a click may help with this.
Attachments (2)
Change History (6)
#1
@
4 years ago
Is the intention here to prevent the need to scrub tickets, or to provide context?
The reason I ask, is that displaying the keywords in Slack just so that it can be skipped to the next sounds like something that would be better off dealt with by filtering the report prior to scrubbing it - This would only add extra slackbot mentions to the ticket without actual discussion?
If it's wanted to provide context for discussion, would it make sense to remove one of the other pieces of information for space considerations?
Or would it make sense to combine the Type & Status fields into something like "open defect", "reopened enhancement" so that there's an even number of displayed fields? or are the keywords usually long enough that it'd probably take up the bottom two sections anyway?
#2
@
4 years ago
Thanks @dd32 it was mostly to provide context during the scrub to easier spot missing keywords and understand the status of the ticket.
In my experience some tickets can have alot of keywords so I would expect they could spread two columns as some in rare cases can have upwards of 10 (needs-patch, needs-testing, needs-privacy-review, needs-copy-review, has-screenshots, needs-dev-note, needs-design, needs-unit-tests, ...). In those longer cases having it in one column would make the message very long.
#3
@
4 years ago
Turns out, keywords are included if the ticket has any keywords.
Focuses are also appended to the Component if the ticket has any focuses.
The lack of a keywords field is due to the ticket not having any keywords.
I'm inclined to leave it as is, rather than adding complexity by listing no-keywords.
The current unfurl when a ticket is mentioned on Slack.