GitHub Jira Integration (faenbbkpfnklhncjianlfllkfekgghih): This extension shows contents of linked tasks from Jira in Github... Read More > or Download Now >
GitHub Jira Integration for Chrome
Tech Specs
User Reviews
- • Rating Average
- 4.4 out of 5
- • Rating Users
- 5
Download Count
- • Total Downloads
- 30
- • Current Version Downloads
- 2
- • Updated: January 18, 2023
GitHub Jira Integration is a free Productivity Extension for Chrome. You could download the latest version crx file or old version crx files and install it.
More About GitHub Jira Integration
Edits GitHub pages to contain information fetched from your Jira instance.
It requires PRs 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.
CHANGELOG:
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
It requires PRs 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.
CHANGELOG:
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
