This project contains various handy user scripts for the Greasemonkey (only for Firefox; GM) and Tampermonkey (for Chrome, but also for other browsers; TM) browser addons. A user script is a piece of JavaScript code which gets executed on page load and which extends functionality of the pages it was written for.
Videos in the following YouTube playlist might help you to get started with this project quickly: gm-scripts - User scripts for Jira.
Firstly install the aforementioned addon for your favorite browser and then simply open the selected *.user.js file in the browser. GM (or TM) will guide you through the rest of the user script installation. The most important thing to do is to set up the pages for which you want to have the given user script activated. You can always find an example of the appropriate "include pattern" right in the installed user script.
An example configuration:
The usage is always specific to a given user script. Most user scripts should offer a special help dialog that can be opened via the GM / TM toolbar icon. And of course, you can always look into the script's source code and see what it actually does... :)
An example help dialog:
An example of the JIRA_copy user script in action (the red "overlay" is rendered by the script after the user presses a corresponding shortcut):
One of the JIRA_shotcuts user script functions in action:
What if something is not working as expected? Then you should firstly try to find some relevant information or error messages in the console log - this is typically available by pressing F12 in your browser and by navigating to the "Console" tab. And select for example "Logging -> Log" to see detailed logging from the GM scripts in Firefox.
If you find a bug or a missing feature, you can create a new issue for that on the "Issues" page of this Github project.
This special chapter includes tips for those who would like to develop GM / TM scripts.
Set the following on the "about:config" page in Firefox:
greasemonkey.fileIsGreaseable: true
At least some @grant <> 'none' must be present in the user script's header in order to force GM to run the script 'in sandbox'.