This repository was archived by the owner on Oct 29, 2020. It is now read-only.
Zendesk Tickets: groups and priority#1580
Merged
aaronschachter merged 6 commits intoDoSomethingArchive:devfrom Mar 31, 2014
aaronschachter:zendesk_groups
Merged
Zendesk Tickets: groups and priority#1580aaronschachter merged 6 commits intoDoSomethingArchive:devfrom aaronschachter:zendesk_groups
aaronschachter merged 6 commits intoDoSomethingArchive:devfrom
aaronschachter:zendesk_groups
Conversation
aaronschachter
changed the title
Contributor
|
👍 |
aaronschachter
added a commit
that referenced
this pull request
Mar 31, 2014
Zendesk Tickets: groups and priority
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #928
Creates admin form to configure each Cause term's with a corresponding Zendesk group_id.
Because each group is created with the same name as the Cause term, we can get away with populating the variables in a
hook_update_Nfunction.The admin form exists for if/when the names or groups should ever change. Also validates entered values against the Zendesk API to make sure the entered group_id value is valid.
Creates ticket with the group_id if it exists. Also if the form is rendered on a staff pick, the ticket is given high priority.