aculligan / zendesk_priority_highlights Goto Github PK

To be honest, I've never been a big fan of Google Analytics, but it has proven useful (ie: knowing what languages needed support).

However, I don't think there's a need to have all the information it provides. The needs of the extension are simple when it comes to analytics: install, uninstall, usage, version, and options editing. I don't need to know anything else really. So, in order to keep protecting users and their privacy, an alternative should be implemented.

Open to ideas. No ETA.

Add the option to customize the colors for each priority.

Options get reset every time after an update.

This happens because the extension sets default options when it's installed, and there is no way to differentiate between a first time install and an update install.

Will need to check if data is already saved and stop the extension from setting new default options.

Make it possible to highlight tickets based on custom fields as well as the default "Priority" field.

Currently using the tabs permission (here and here) to set the icon actions, but using the tab permissions seems like an overkill for an extension that only runs in one domain.

Changing the permission to activeTab (here and here) will still give the same benefits without the the extension having access to any other pages. This is good for privacy.

Add Force SSL.

Seems like a good practice.

Hi @aculligan,

Our team uses Zendesk for our primary support and often find ourselves wishing for the ability to highlight tickets that have not received an agent response after a certain amount of time has elapsed. I was wondering if you would be open to me forking this repo and giving that update a try?

The reason I ask here is because I would be happy to submit a pull request under this issue (or a new one if it doesn't quite fit here) if I'm successful and if this is something you would find useful?

No matter what, thanks for this helpful chrome extension!

Originally posted by @jude-lawson in #3 (comment)

Some CSS items in Firefox are moved around, or the wrong size.

To protect user privacy, will add "anonymizeIp" to all Google Analytics. Google never displays that data to developer, but there's no reason anyone should have it at all in the first place.

anonymizeIp
IP Anonymization in Analytics

Extension is unable to find DOM elements when a views page is reloaded. This is because Zendesk can take a long time to load all the elements, especially tickets in views.

This has been addressed in the past by setting a timeout before extension loads, but that creates a bad UX when the page does load fast enough.

Firefox throws an error when using window.close();

Scripts may not close windows that were not opened by script.

This means the Options page and Options popup can't be closed by user or after inactive time.

Functions in content_scripts run multiple times, causing Google Analytics to fire several times and local variables get reset to undefined.