Hari Sekhon - TamperMonkey Scripts

• TamperMonkey Scripts
  • Install
    • Option 1 - Copy & Paste
    • Option 2 - Import from URL
  • Tel to WhatsApp
  • Jira Description Autofill
• Troubleshooting
• More Core Repos
  • Knowledge
  • DevOps Code
  • Containerization
  • CI/CD
  • DBA - SQL
  • DevOps Reloaded
  • Templates
  • Misc

TamperMonkey Scripts

Copy and paste these scripts into your TamperMonkey browser extension to customize your browsing experience.

See the Knowlege-Base - TamperMonkey page for more general TamperMonkey info.

Install

Option 1 - Copy & Paste

Copy and paste the raw code into a new script in TamperMonkey.

Use the Raw button on on the top right of the file to copy from.

Option 2 - Import from URL

In TamperMonkey settings, go to Utilies at the top right, then at the bottom of that page see Import from URL.

Paste the Raw URL to the script into the box and click Install.

Raw URL looks like this, which can be obtained from the Raw button at the top right of the file on GitHub:

https://raw.githubusercontent.com/HariSekhon/TamperMonkey/refs/heads/main/jira_description_autofill.js

Tel to WhatsApp

tel_to_whatsapp.js

Replaces +tel:... links to WhatsApp clickable links for convenience.

Jira Description Autofill

jira_description_autofill.js

Autofills the Jira ticket description field with HTML contents that you can then edit natively in the Jira UI.

Does not overwrite any already populated description for safety.

For Jira tickets with existing descriptions you can Ctrl-x / Cmd-x to cut your content out and press any key in the description box to trigger the script to fill in the description boilerplate text and then paste your content back in and tweak it.

You can edit the const descriptionHTML = line of code near the top to suit your tastes, currently it renders in the Jira UI as:

Summary

As a platform engineer
I want ...
So that ...

Acceptance Criteria

• Criteria one...

• Criteria two...

Engineering Notes & References

• Put Notes here

• Record design decisions

• URLs to references and relevant docs

Troubleshooting

Logging added for debugging is visible in the Chrome Developer Tools -> Console -> All Levels drop down -> tick Verbose.

If the script isn't triggering, check you have copied & pasted it entirely correctly.

On one occasion, no scripts were triggering, and the solution was to remote the TamperMonkey Chrome extension and then re-add it fresh and then install the script back in again.

There was nothing wrong with the code itself, which is revision controlled and hadn't changed.

See the Knowledge-Base - TamperMonkey Troubleshooting section for more details.

More Core Repos

Knowledge

DevOps Code

Containerization

CI/CD

Databases - DBA - SQL

DevOps Reloaded

Monitoring

Templates

Desktop

Spotify

The rest of my original source repos are here.

Pre-built Docker images are available on my DockerHub.