GitHub by Git-Zen
GitHub by Git-Zen When a developer pushes a fix, your support team should know - automatically. When an agent escalates a bug, it should reach engineering without a Slack thread. Git-Zen connects Zendesk and GitHub so both teams stay current, in the tools they already live in. How It Works From a Zendesk ticket, agents can: * Create a new GitHub issue in one click, with your existing labels, milestones, assignees, and issue templates * Link an existing GitHub issue to the ticket * See issue updates, commits, and comments appear automatically in the ticket timeline From GitHub, developers can: * Reference a Zendesk ticket number in a commit message. The commit and affected files appear in the ticket automatically * Leave issue comments that flow into Zendesk as public or private notes No GitHub account needed for support agents. No Zendesk access needed for developers. Key Features Create GitHub issues from Zendesk: File bugs and feature requests directly from tickets, with labels, assignees, and milestones set at creation time Commit tracking: Every commit that references a ticket number appears inside Zendesk, with the files it touched Two-way comment sync: GitHub comments appear in Zendesk; ticket comments post to GitHub Custom issue templates: Use your existing GitHub issue templates when creating from Zendesk Multiple issues per ticket: Link as many GitHub issues as needed to one ticket, and vice versa Auto-tagging: Zendesk tickets are automatically tagged when linked or when an issue is closed Role-based permissions: Control which agents can create or modify GitHub issues Simple per-agent pricing: $4 per Zendesk agent, per month. Unlimited tickets and integrations. Free trial included. Works with GitHub.com. Security & Data Disclosure Git-Zen relays data between Zendesk and GitHub in real time: ticket subject, description, and comments are read from and written to your Zendesk account, and corresponding issue data (title, description, status, assignee, labels, and comments) is read from and written to your GitHub account, to keep both systems in sync. We store your OAuth access tokens (encrypted) and account configuration (connected GitHub account/workspace, sync settings, field mappings) on Git-Zen servers so we can act on your behalf. We do not separately retain ticket or issue content on our servers -- sync state is written back into a private custom field on the Zendesk ticket itself. Authentication uses OAuth 2.0 for both Zendesk and GitHub. For more information, visit https://www.git-zen.com
Top keywords
- github17×4.28%
- zendesk15×3.78%
- ticket12×3.02%
- issue10×2.52%
- comments6×1.51%
- account5×1.26%
- git-zen5×1.26%
- automatically4×1.01%
- commit4×1.01%
- issues4×1.01%
- sync4×1.01%
- zendesk ticket4×1.01%
BeyondTrust Remote Support
Simply locate the BeyondTrust Remote Support app in the Zendesk Apps Marketplace (Admin > Apps > Marketplace) and click Install. Settings for the app include (required settings in bold text): Title – Name of the app provided in upload step; can be overridden here Hostname – Hostname of the BeyondTrust Remote Support appliance Issues – A list of issues from which an end-user can choose when using the ‘Get Support Now’ button to start a chat session. These should be entered one per line in the format issuecode=IssueName where issuecode is the issue code configured for the issue in the Remote Support appliance /login interface and IssueName is the user-friendly name that will be displayed to the end-user in the dropdown list. Jumpoints – A list of Jumpoints configured for the Remote Support appliance from which an agent can choose entered one per line. Allow Jump-To Pinned Client Session – Determines whether jump method is available to agents Allow Push and Start Local Jump Session – Determines whether jump method is available to agents Allow Push and Start Remote Jump Session – Determines whether jump method is available to agents (if enabled, requires at least one Jumpoint to be entered) Allow Remote Desktop (RDP) Session – Determines whether jump method is available to agents (if enabled, requires at least one Jumpoint to be entered) Allow Remote Console Session – Determines whether jump method is available to agents (if enabled, requires at least one Jumpoint to be entered) Enable role restrictions – This is a standard Zendesk app setting that allows you to customize which (agent) roles will see the UI elements provided by the app Once the app is installed and configured, you should see the UI elements (buttons) in the appropriate section when viewing an existing ticket or creating a new ticket. The final portion of the app is for end-users and must also be configured by an administrator. Just as with the Generate Session Key and Jump buttons, when viewing a ticket administrator users will see an additional button labelled Customize Help Center. Clicking the button will open a modal dialog with instructions for editing the current theme to add the support button to ticket views for end-users. When clicked, a chat support session tied to the selected ticket will be started and routed to the appropriate team based on the issue selected by the user prior to clicking the button.
Top keywords
- jump8×2.04%
- session8×2.04%
