Skip to content
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

Subject tag in email to #30

Open
wants to merge 2 commits into
base: stable
Choose a base branch
from

Conversation

bobtfish
Copy link

Allow per queue tags to be used in email 'To' addresses.

bobtfish added 2 commits May 17, 2012 10:59
Currently, you can create a ticket (via the REST interface) with a Cc
of => [4], which will unexpectedly cause the ticket to be CC'd to the
entire group (all privilidged users is always ID bestpractical#4).

This is obviously unexpected, and in a large multi-tenant shared RT situation,
all privilidged users seeing a specific ticket is really really bad..

If for some reason this API needs to stay, then I strongly think it should
refuse to create CCs for the default privilidged / everyone groups, as this
is never what you want, and always bad...

Also, the user interface is completely unable to handle tickets which have a
group CC'd in - they instead list a blank space, and checking the checkbox
doesn't work to remove the group. So even after we'd worked out what was
going on, we weren't able to undo it without manual database hacking.

If the numeric API _is_ meant to be supported, then it either needs to expand
group ID into a list of user IDs and add these, or group ID#s need to be
disallowed, or the interface needs to correctly support the removal of groups
from tickets.
@sunnavy
Copy link
Member

sunnavy commented Oct 6, 2015

we already support "the interface needs to correctly support the removal of groups from tickets.", so I assume the first commit is not necessary any more.

the 2nd commit lacks the document of the new option and it seems not quite flexible as subject tag is fixed to be the first %s, so maybe it's good to make a local customization instead of coring it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants