Child pages
  • Github Issues vs Jira pros and cons
Skip to end of metadata
Go to start of metadata

Articles on the web showing pros and cons

Atlassian, maker of JIRA (so will be biased) - https://www.atlassian.com/software/jira/comparison/jira-vs-github

Slant - https://www.slant.co/versus/9456/917/~jira_vs_github-issues

G2 - https://www.g2crowd.com/compare/github-vs-jira

 

JIRA pros and cons

ProsCons
  1. Supports security restricted issues
  2. Has globally googlable issues IDs (google for SAK-???? and you normally end up at our Jira)
  3. Distinct fields including affects version, merge versions, priority, components.
    1. github relies of freeform labels and milestones and can't capture all details
  4. Built in kanban boards, in github you'd have to use zenhub plugin
    1. Sakai project far too big to make the current boards usable, doubt this is actually used
  5. Better searching using the distinct fields
  6. Better connection with confluence (actually excellent two way connection with Confluence)
  7. All current issues are there
  8. Easy to connect issues together with links, sub-tasks. Good for tracking dependencies and relations
  9. Has a process to import from github issues
  1. Reportedly slow network access from certain locations
  2. Can be slower to switch around screens
  3. Complex form for entry of new issues (Maybe have simplified this and can continue to improve)
  4. Requires an additional separate to log an issue. (Maybe there's a plugin for this?)

 

 

 

Github Issues pros and cons

ProsCons
  1. In the same place as the code, easier to find where to file issues
  2. People already have accounts on GitHub so barrier to filing is lower (could enable Github sign-in to Jira?)
  3. Simple form for entering new issues (title/description).
  1. Doesn't have many of the fields that JIRA has, relies on labels
  2. Labels seem lacking, in that not anyone can add a label, has to be an admin.
  3. If a label is removed it's removed from all issues with no easy audit log and no easy recovery
  4. No quick migration from JIRA to github issues (that I could find)
  5. No way to track security (outside of using gitlab)
  6. Harder to see what branches an issue is actually merged into compared to JIRA
  7. No plugin support
  8. Someone has to create an account and be a member of the project to be assignable

 

 

 

https://confluence.sakaiproject.org/display/PMC/Github+Issues+vs+Jira+pros+and+cons

  • No labels