Atlassian JIRA VS Commit Together by Github

• Comprehensive Project Management
  JIRA provides a wide array of tools for project management, including planning, tracking, and releasing software solutions, making it ideal for Agile teams.
• Customization and Flexibility
  JIRA is highly customizable, allowing teams to tailor workflows, dashboards, and fields to match specific project requirements and methodologies.
• Integration Capabilities
  It integrates seamlessly with a multitude of third-party applications and other Atlassian products, enhancing collaboration and productivity.
• Robust Reporting
  JIRA offers powerful reporting and analytics tools that help teams monitor progress, track issues, and improve project transparency and accountability.
• Scalability
  Suitable for organizations of all sizes, JIRA can scale efficiently as project teams grow and evolve.

Possible disadvantages

• Complexity for New Users
  The vast array of features and customization options can be overwhelming for new users, leading to a steep learning curve.
• Cost
  For larger teams or when additional features are required, the cost of JIRA can become relatively high compared to some other project management tools.
• Performance Issues
  With extensive customization and as projects grow, some users experience performance issues or slower response times.
• Limited Non-Technical Use
  JIRA is primarily designed for software development teams, which may limit its appeal or effectiveness for non-technical projects.
• Administrative Overhead
  Managing and maintaining the platform can become complex, requiring dedicated resources or expertise, especially in large organizations.

• Enhanced Collaboration
  Commit Together allows multiple authors to be credited in a single commit, which fosters a more collaborative environment and ensures everyone involved receives recognition for their contributions.
• Improved Code Review Process
  With multiple authors clearly listed, reviewers can better understand who contributed to which parts of the code, facilitating more directed questions and discussions.
• Accountability
  By attributing every change to the respective author, teams can easily track who made specific changes, which helps in accountability and understanding the history of a project.
• Efficiency in Pair Programming
  When pair programming, both developers can be credited for their combined effort, streamlining the process of sharing code ownership during collaborative sessions.

Possible disadvantages

• Complex Commit History
  Having multiple authors for a single commit may lead to a more complex commit history, making it harder to pinpoint individual contributions over time.
• Potential Workflow Conflicts
  Teams that are used to single-author commits may experience workflow conflicts or require adjustments in practices to accommodate multi-author contributions.
• Initial Setup Overhead
  Learners and new users might face a learning curve or require additional setup to understand and correctly implement the multi-author commit feature.
• Tooling Compatibility
  Some third-party tools and extensions might not fully support or display multi-author commits, leading to inconsistencies in those environments.

Tracking Atlassian JIRA since Mar 2021.

• Ask HN: Do you rewrite pull requests?

  There is "Co-authored-by" which is supported on GitHub [1] and seems appropriate if the maintainer is basing the solution on someone's code. [1] https://github.blog/2018-01-29-commit-together-with-co-authors/. - Source: Hacker News / over 4 years ago