|
|
|
Ask HN: What services do you use alongside GitHub to get “Atlassian” features?
|
|
7 points
by qrco
3421 days ago
|
|
Atlassian has a pretty convenient offering. With a single service you can get: - Version Control (Bitbucket) - Issue Tracking (Jira) - Team Chat (HipChat) - Wiki (Confluence) - CI/CD (Bitbucket Pipeline) - and soon Project Management (Trello). To construct a similar set of services but centered around GitHub, what would/do you use? Any services for features not listed above? |
|
With GitHub + JIRA you get:
- associated branches, commits, and pull requests displayed on the JIRA issue view
- the ability to search for issues based on whether they have branches, commits, or pull requests associated with them
- the "Release Hub", which tracks issues that have outstanding pull requests, or have code but no pull request
- automatic issue transitions, which transition JIRA issue status based on repository events
It's flexible, but the usual automatic issue transition workflow is:
branch created: issue -> "In Progress"
pull request created: issue -> "In Review"
pull request merged: issue -> "Done"
Which works just as well with GitHub as it does with Bitbucket.
The main thing that Bitbucket + JIRA's integration adds is backlinks from Bitbucket to JIRA. Plus the ability to create branches in your Bitbucket repositories directly from JIRA.
If you're dead set on GitHub over Bitbucket, the best way to get "Atlassian" features is to adopt the Atlassian suite and replace GitHub with Bitbucket.
Disclosure: I worked on JIRA's DVCS integration.
edit: fixed formating