Open WilliamVenner opened 1 year ago
Would you be able to elaborate on why you would want such an action to inform the customer?
Personally I would see the pinning of tickets as an additional organizational method, where in some cases one might not even want to directly inform the customer that their ticket was "pinned" (it may set a certain expectancy).
In the cases that a creator would want to inform the customer that the ticket has been "pinned", I'd think that a customized message may add more value.
I'd like to hear your input on this.
I'm indifferent, really. But I can definitely see how it could set a certain expectancy.
Off-topic: a temporary/maybe even better solution for your use case could be subscribing to the ticket label webhooks and adding tickets to something like a GitHub board automatically when they're labeled with the bug label :).
Feature
I would like to be able to "pin" tickets. E.g., if a ticket is a bug report and I need to action it, I don't want it to be buried under other tickets.
Additional Information
The customer should be informed that the ticket has been pinned.