Child pages
  • Github Issues vs Jira pros and cons

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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 (https://confluence.atlassian.com/adminjiraserver071/importing-data-from-github-802592903.html)
  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?)

...