There is currently a major limitation in SLACK-created-tickets. When you use a SLACK action to create a ticket the user is encouraged to select a group to assign the ticket to.
As we are structured with 1st and 2nd line groups, (and also groups that are effectively parking garages for tricky internal tickets) user are able to assign to these groups in error which breaks our workflows and means I must keep checking these groups, OR it looks like a second line query that has not been through 1st line. (see image)
We need to be able to EXCLUDE some of these groups from the assignee field in SLACK. As you can see I have had to rename the groups with clunky names to try and reduce this behaviour, but this looks untidy everywhere you see the group name.
I also echo other users calls to be able to customise the fields in SLACK submissions, for example adding PRIORITY, TYPE and other standard fields would be a massive stride forward.
댓글을 남기려면 로그인하세요.