Jira Data Center 7.0.0 - 7.2.15
View Git Commits, Branches, Tags and Pull Requests in Jira. Connect git servers + GitHub, Bitbucket, GitLab & Azure Repos VSTS/TFS
View Git Commits, Branches, Tags and Pull Requests in Jira. Connect git servers + GitHub, Bitbucket, GitLab & Azure Repos VSTS/TFS
Integrate Git with Jira
View source code with diffs in Jira
Create branches and pull requests in Jira
View your Git commits inside of Jira. Quickly view commit comments, files changed, and authors.
Special integrations with GitHub.com, GitHub Enterprise, GitLab.com, GitLab server, + Azure Repos and more.
Keep your Jira issues moving through your development process while keeping your quality high by reviewing code inside Jira. No other tools needed.
Create branches and pull requests in Jira issues. Branch name is automatically contains Jira issue key (necessary for linking to Jira) and the issue summary. (not available for Gerrit or plain git repositories)
Integrate Git with Jira
View source code with diffs in Jira
Create branches and pull requests in Jira
View your Git commits inside of Jira. Quickly view commit comments, files changed, and authors.
Special integrations with GitHub.com, GitHub Enterprise, GitLab.com, GitLab server, + Azure Repos and more.
Keep your Jira issues moving through your development process while keeping your quality high by reviewing code inside Jira. No other tools needed.
Create branches and pull requests in Jira issues. Branch name is automatically contains Jira issue key (necessary for linking to Jira) and the issue summary. (not available for Gerrit or plain git repositories)
Integrate Git with Jira
View source code with diffs in Jira
Create branches and pull requests in Jira
View your Git commits inside of Jira. Quickly view commit comments, files changed, and authors.
Special integrations with GitHub.com, GitHub Enterprise, GitLab.com, GitLab server, + Azure Repos and more.
Keep your Jira issues moving through your development process while keeping your quality high by reviewing code inside Jira. No other tools needed.
Create branches and pull requests in Jira issues. Branch name is automatically contains Jira issue key (necessary for linking to Jira) and the issue summary. (not available for Gerrit or plain git repositories)
More details
🎉 Automation triggers supported 🎉
🖥️ Schedule a one-on-one review of your setup/configuration
----
Trusted by +9100 customers in 75 countries. (Roadmap | Release notes)
Features
- View Git in context with Jira to understand development status
- Smart Commits: Add comments, time, transition Jira issues, change assignee, & add fix/affects version with Git commits
- Integrates with Jira Software's agile tools
- View Git tags
- Search Git commits with JQL
- Browse repositories in Jira (files, commits, compare branches)
- Manage branches, pull/merge requests from issue view
- Supports all Git servers:
-
- GitLab.com
- GitLab CE/EE
- Microsoft Azure DevOps Repos (formerly Visual Studio Team Services - VSTS) + TFS
- GitHub.com
- GitHub Enterprise
- AWS CodeCommit
- BitBucket
- Beanstalk
- Git on Linux/Windows
- Gerrit
- Gitblit
- Windows network share
- SSH
- HTTP/HTTPS
- git protocol
- local file/network path
- Localized: EN, DE, JA, FR, RU, ZH, PL, ES
More details
🖥️ Schedule a one-on-one review your setup/configuration
----
Over 9100+ customers in 75 countries. (Roadmap)
Features
- View Git in context with Jira to understand development status
- Smart Commits: comment, time, transition issues, assign, & add fix/affects version with Git commits
- Integrates with Jira Software's agile tools
- View Git tags
- Search Git commits with JQL
- Browse repositories in Jira (files, commits, compare branches)
- Bulk change for managing 1000s of repositories
- Manage branches, pull/merge requests from issue view
- Supports Git LFS
- Supports all Git servers:
- GitLab.com
- GitLab CE/EE
- Microsoft Azure DevOps Repos (Visual Studio Team Services - VSTS) + TFS
- GitHub.com
- GitHub Enterprise
- BitBucket
- AWS CodeCommit
- Beanstalk
- Git on Linux/Windows
- Gitolite
- Gerrit
- Windows network share
- SSH
- HTTP/HTTPS
- git protocol
- local file/network path
- Localized: EN, DE, JA, FR, RU, ZH, PL, ES
More details
🖥️ Schedule a one-on-one review your setup/configuration
----
Over 9100+ customers in 75 countries. (Roadmap)
Features
- View Git in context with Jira to understand development status
- Smart Commits: comment, time, transition issues, assign, & add fix/affects version with Git commits
- Integrates with Jira Software's agile tools
- View Git tags
- Search Git commits with JQL
- Browse repositories in Jira (files, commits, compare branches)
- Bulk change for managing 1000s of repositories
- Manage branches, pull/merge requests from issue view
- Supports Git LFS
- Supports all Git servers:
- GitLab.com
- GitLab CE/EE
- Microsoft Azure DevOps Repos (Visual Studio Team Services - VSTS) + TFS
- GitHub.com
- GitHub Enterprise
- BitBucket
- AWS CodeCommit
- Beanstalk
- Git on Linux/Windows
- Gitolite
- Gerrit
- Windows network share
- SSH
- HTTP/HTTPS
- git protocol
- local file/network path
- Localized: EN, DE, JA, FR, RU, ZH, PL, ES
Reviews for cloud
(282)Sign in to write a review
David - thanks for the review. We're not always able to turn around new feature requests this quickly - but we're pleased this is helpful to your team.
For those reading the review - the new feature is the ability to use ${sourcebranch} in the default branch name template in General settings. - Adam
Thank you for taking the time to correspond with us and leave this review. Based on your feedback we've made a number of in-product and team process updates and rolled them out. Thank you again! - Adam
Hi Dan,
Thank you for the review!
DLG
Reviews for server
(282)Sign in to write a review
Hi Zvika - to associate branch/tags/commits/pull requests to Jira issues, you will need to put the Jira issue key ("ABC-123") in the commit message or branch/PR name. Please note that the Atlassian Marketplace discourages the Reviews section for asking questions. If you have follow up questions for us - email us at support@bigbrassband.com Cheers, AW
Hi Lyndsey - the advantages depend on the git servers you are connecting to Jira. The DVCS app in Jira only natively supports GitHub and Bitbucket - our app supports GitLab, Azure DevOps, AWS CodeCommit and Gerrit. Our app also makes it possible to create branches and pull requests from Jira issues. There are other features - we'd be happy to do a demo or correspond via email - just email us at support@bigbrassband.com. Cheers, AW
Reviews for Data Center
(282)Sign in to write a review
Thank you for the star review! - AW
Cloud Pricing
Server Pricing
Data Center Pricing
| 10 users$10 | 25 users$425 | 50 users$765 | 100 users$1,325 | 250 users$2,300 | 500 & upAdditional pricing details |
| 50 users$765/year | 100 users$1,325/year | 250 users$2,300/year | 500 users$3,300/year | 750 users$3,700/year | 1000 & upAdditional pricing details |
Pricing FAQ
- How does cloud app pricing work?
Cloud apps are sold as a monthly or annual subscription. You are eligible for support and automatic version updates as long as your subscription is active.
When your subscription renews each month, you are automatically billed for apps based on the number of users in your instance.
If app pricing changes after your initial purchase, there's a 60-day grandfathering period during which you can renew based on the old pricing.
- How do I determine my cloud pricing?
Apps are billed based on the number of users in your Atlassian product. Jira Cloud apps are priced based on the maximum users of the Jira products on your instance. For example, if you have Jira Software (50 users) and Jira Service Management (10 agents) on the same instance, you pay the 50-user price for apps.Note: While this app has features specific to Jira Service Management, the app is technically available across the whole Jira instance. Therefore the above guidelines for licensing across maximum users still apply.
The pricing structure for cloud apps is as follows:
- Monthly subscriptions with up to 10 Atlassian product users are billed at a flat rate price.
- Monthly subscriptions with more than 10 users are billed per user, starting at the first user.
- Monthly subscriptions with more than 100 users are billed per user. The table above provides example pricing at various user levels.
Annual subscriptions may offer a discount depending on the number of users purchased.
- Do you offer academic, community, or open-source licenses for cloud apps?
Yes. Academic, community, and open source licenses are available to qualifying organizations. See our Purchasing & Licensing FAQ for more information.
- Can I extend my free trial?
For cloud apps, you cannot extend your free evaluation period. All cloud apps are immediately subscribed by a user, and we provide a free evaluation period. This is a minimum of 30 days and ends on the second billing cycle after you first subscribe to the app.
Pricing FAQ
- How does server app pricing work?
Server products and apps are hosted on your servers. This app is sold as a perpetual license, and the purchase price includes 12 months of maintenance (support and version updates).
You can renew maintenance after 12 months at 50% of the current purchase price. You can upgrade the tier of your Atlassian product and app licenses at any time. Upgrade prices are calculated based on Atlassian's formula (view example).
If app pricing changes after your initial purchase, there's a 60-day grandfathering period during which you can renew based on the old pricing.
- How do I determine my server pricing?
Apps are billed based on the number of users in your Atlassian product. For Jira 7.0 or later, the app tier should match the maximum tier of the licensed Jira products on your instance. For example, if you're running Jira Software (500 users) and Jira Service Management (25 agents) on the same instance, you should purchase the 500-user tier for apps. For versions of Jira prior to 7.0, the app tier should match the licensed user tier for Jira. Even if fewer users want to use the app than your Jira license, the two licenses should match exactly. Note: While this app has features specific to Jira Service Management, the app is technically available across the whole Jira instance. Therefore the above guidelines for the license tier still apply.
- Can I install this app in a Data Center product?
Yes, this app has a Data Center approved version. If you're using a Data Center product, you should install the Data Center version of the app.
- What type of license do I need if I'm using this app in a Data Center product?
Because this app has a Data Center approved version, you should purchase a Data Center license for the app.
If you already own a server license for this app, you can continue using the server license in your Data Center product for a limited period of time.
- Do you offer academic, community, or open-source licenses for server apps?
For server apps, academic licenses are available at a 50% discount if you have an academic license for your Atlassian product.
Community and open-source licenses are available for server apps. Learn more about community and open source licenses.
- Can I extend my free trial?
For server apps, you can extend your app trial up to 5 times - in other words, for up to six months. Extend your trial by generating a new evaluation license key from Atlassian Marketplace. Click Try it free and you'll be directed to generate a new license. Paste this license key into the app listing in UPM from your Atlassian product, and you're all set.
- How can I buy apps for my legacy Jira Server or Confluence Server license?
If you own a legacy Jira Server Unlimited (100+ users) or Confluence Server Unlimited (2000+ users) license purchased in 2012 or earlier, legacy app pricing is no longer available. You have two options for app purchasing:
- Purchase the app at the non-legacy Unlimited (10000+ users) tier.
- Renew your Jira or Confluence license at a non-legacy tier, then purchase the app at the same tier.
Pricing FAQ
- How does Data Center app pricing work?
Data Center apps are sold as an annual subscription. You are eligible for support and version updates as long as your subscription is active.
If app pricing changes after your initial purchase, there's a 60-day grandfathering period during which you can renew based on the old pricing.
- How do I determine my Data Center pricing?
Apps are billed based on the number of users in your Atlassian product. For Jira 7.0 or later, the app tier should match the maximum tier of the licensed Jira products on your instance. For example, if you're running Jira Software (500 users) and Jira Service Management (25 agents) on the same instance, you should purchase the 500-user tier for apps. For versions of Jira prior to 7.0, the app tier should match the licensed user tier for Jira. Even if fewer users want to use the app than your Jira license, the two licenses should match exactly. Note: While this app has features specific to Jira Service Management, the app is technically available across the whole Jira instance. Therefore the above guidelines for the license tier still apply.
- Can I install this app in a Data Center product?
Yes, this app has a Data Center approved version. If you're using a Data Center product, you should install the Data Center version of the app.
- What type of license do I need if I'm using this app in a Data Center product?
Because this app has a Data Center approved version, you should purchase a Data Center license for the app.
If you already own a server license for this app, you can continue using the server license in your Data Center product for a limited period of time.
- Do you offer academic, community, or open-source licenses for Data Center apps?
For Data Center apps, academic licenses are available at a 50% discount if you have an academic license for your Atlassian product.
Community and open-source licenses are not available for Data Center apps. Learn more about community and open source licenses.
- Can I extend my free trial?
For Data Center apps, you can extend your app trial up to 5 times - in other words, for up to six months. Extend your trial by generating a new evaluation license key from Atlassian Marketplace. Click Try it free and you'll be directed to generate a new license. Paste this license key into the app listing in UPM from your Atlassian product, and you're all set.
BigBrassBand provides support for this app.
BigBrassBand provides support for this app.
BigBrassBand provides support for this app.
Vendor support resources
Find out how this app works.
Community discussions connect you to the vendor and other customers who use this app.
Atlassian-hosted discussions connect you to other customers who use this app.
Vendor support resources
Find out how this app works.
Community discussions connect you to the vendor and other customers who use this app.
Atlassian-hosted discussions connect you to other customers who use this app.
Vendor support resources
Find out how this app works.
Community discussions connect you to the vendor and other customers who use this app.
Atlassian-hosted discussions connect you to other customers who use this app.
Versions
Jira Cloud • Released 2020-11-27
Summary
Minor version update
Details
Minor version updateVersions
Version 3.7.2.5 • Jira Server 7.3.0 - 8.14.0 • Released 2020-11-27
Summary
New feature: Associate pull/merge requests to issues based on commits
Details
v3.7.2.4
- New feature: Associate pull/merge requests to issues based on commits
- New General settings: Enable indexing PRs via API + commits
v3.7
As with any large updates - we recommend updating a non-production Jira before updating production
Features:
- Introduce cron style scheduling option (documentation)
Improvements:
- Deduplicate webhook indexing triggers
- Rearchitect pull/merge request indexing (see Administrator note below)
- Optimize pull/merge request calls for GitHub/GitLab
Bug fixes: 9
Minimum Jira compatibility: 7.2
Jira administrator note:
Pull/merge requests previously stored as files in Jira. Pull/merge requests will now be stored in Jira database table: AO_8BA09E_MERGE_REQUEST. A Lucene index is then created to reduce database load (DC: each node will generate a Lucene index).
Report issues to support@bigbrassband.com
Future releases: Roadmap
Versions
Version 3.7.2.5 • Jira Data Center 7.3.0 - 8.14.0 • Released 2020-11-27
Summary
New feature: Associate pull/merge requests to issues based on commits
Details
v3.7.2.4
- New feature: Associate pull/merge requests to issues based on commits
- New General settings: Enable indexing PRs via API + commits
v3.7
As with any large updates - we recommend updating a non-production Jira before updating production
Features:
- Introduce cron style scheduling option (documentation)
Improvements:
- Deduplicate webhook indexing triggers
- Rearchitect pull/merge request indexing (see Administrator note below)
- Optimize pull/merge request calls for GitHub/GitLab
Data Center:
- Overall reduction of PR API calls to git server by retrieving pull requests from a single node, rather than all nodes
Bug fixes: 9
Minimum Jira compatibility: 7.2
Jira administrator note:
Pull/merge requests previously stored as files in Jira. Pull/merge requests will now be stored in Jira database table: AO_8BA09E_MERGE_REQUEST. A Lucene index is then created to reduce database load (DC: each node will generate a Lucene index).
Report issues to support@bigbrassband.com
Future releases: Roadmap
Installation
- Log into your Jira instance as an admin.
- Click the admin dropdown and choose Atlassian Marketplace. The Manage add-ons screen loads.
- Click Find new apps or Find new add-ons from the left-hand side of the page.
- Locate Git Integration for Jira via search. The appropriate app version appears in the search results.
- Click Try free to begin a new trial or Buy now to purchase a license for Git Integration for Jira. You're prompted to log into MyAtlassian. Git Integration for Jira begins to download.
- Enter your information and click Generate license when redirected to MyAtlassian.
- Click Apply license. If you're using an older version of UPM, you can copy and paste the license into your Jira instance.
To find older Git Integration for Jira versions compatible with your instance, you can look through our version history page.
- Log into your Jira instance as an admin.
- Click the admin dropdown and choose Add-ons. The Find new apps or Find new add-ons screen loads.
- Locate Git Integration for Jira.
- Click Free trial to download and install your app.
- You're all set! Click Close in the Installed and ready to go dialog.
- Log into your Jira instance as an admin.
- Click the admin dropdown and choose Atlassian Marketplace. The Manage add-ons screen loads.
- Click Find new apps or Find new add-ons from the left-hand side of the page.
- Locate Git Integration for Jira via search. The appropriate app version appears in the search results.
- Click Try free to begin a new trial or Buy now to purchase a license for Git Integration for Jira. You're prompted to log into MyAtlassian. Git Integration for Jira begins to download.
- Enter your information and click Generate license when redirected to MyAtlassian.
- Click Apply license. If you're using an older version of UPM, you can copy and paste the license into your Jira instance.
To find older Git Integration for Jira versions compatible with your instance, you can look through our version history page.
Similar apps
