GitHub Jira Integration

This extension shows contents of linked tasks from Jira in Github

Manipulates GitHub webpages to contain information fetched from your Jira instance. It requires PR's to contain a link to the name of a ticket (in the TICKET-321 format). It will then try to fetch data from there and put it in the PR page, appending information and making ticket links clickable. INSTALLATION GUIDE: - Install the plugin. - In the right top, click the icon, and open up the "options" screen - Fill in your settings (such as company.atlassian.net) and press save - PR's on github.com should now show direct links to Jira tickets and information. CHANGELOG: v1.3.0 - Fix prefilled data being overwritten by plugin (thanks @blakegearin | fixes #49) - Upgrade manifest from v2 to v3 (thanks @HanJaeJoon) - Allow for custom URL's with optional permissions (thanks @exadeci | fixes #45) - Replaced deprecated DOM checks with proper listeners - Fixed potential undefined error in navigating pages v1.2.3 - Fix title selection in Github page v1.2.2 - Assignee is now optional, doesn't show when unassigned - Page jumps around a bit less when loading ticket information v1.2.1 - Fixed order of reporter / assigned names v1.2.0 - Added option to disable automatic title generation - Added option to disable automatic template insertion - Fixed incorrect title loading when opening an MR - Updated jQuery to 3.3.1 - Improved look of inserted information in PR overview - Improved option page - Improved API calls - no longer using jQuery's `ajax`, but Chrome's `fetch` in a background view. - Changed template language to be English by default - Removed the extra tab generated, as it wasn't really used v1.1.1 - Fixed compatibilty with new GitHub layout (#15, #18) - Added ticket status in PR (#17) - All links to tickets in commits are automatically parsed and a link will be placed (#16) v1.1.0 - Added possibility to filter acceptance criteria from the ticket and parse it into the PR using the template. v1.0.4 - Removed console logs - Fixed Uncaught TypeError when no ticket number was found (#3) v1.0.3 - Automatically full a new PR description with a preset template, and will try to update the PR title with a proper one based on the tickets (the ticket number should be in your branch name) - Fixed a button loading bug More updates will follow; such as: - Information in PR overview - More information in the overview / Jira page Privacy: https://github.com/RobQuistNL/chrome-github-jira/blob/master/PRIVACY.md