| The irony here is that this integration addresses the heart of the complaints in this thread. People don't want to have to update whatever project management team their management uses. Good News! That's why this integration exists. 1. This integration lets developers work on their code while automatically sending updates Jira so they don't have to. 2. When you create a commit, it can automatically transition a Jira issue so you don't have to go to Jira to do it. 3. Use smart commits to update the status in Jira, leave a comment, or log time without leaving your command line or GitHub. 4. When you create a branch in BB or GH it will automatically transition the issue in Jira so you don't have to. 5. When you merge a pull request in GH and BB it will automatically transition the issue in Jira so you don't have to. 6. Linking Jira Software to GitHub lets you see branches, commits, and pull requests right on the Jira issue. 7. Now everyone, even those pesky managers and program managers can see the status of work without asking you to take your headphones off, “bumping” their email in your inbox of “pinging” you for the 10th time in Slack. They can see your status right from the board without even clicking into the issue.
8. Search for Jira issues based on related GitHub information, such as open pull requests. https://www.atlassian.com/blog/jira-software/github-for-jira |