Comparison of issue tracking in major SCM tools
Transcript of Comparison of issue tracking in major SCM tools
• Create issues without assigning to amilestone
• Repository-bound issuemanagement
• Cannot set any priorities or modify states
• Shortcuts for properMarkdown commands
• Unclear support for attachments
Conclusion
GitHub's issuemanagement has similarities with
other SCM tools. Simplicity is a plus, as is the
possibility to set due dates for milestones. Lack of
prioritizingmay cause issues for project managers.
• Repository-bound issuemanagement
• Choose between "open" or "closed" states
• Priority set on a scale of 1-9
• Filterable bymultiple factors
• Allows bulk milestone, status or assignee edits
Conclusion
GitLab's issuemanagement has nice features,
looks good, and lets you use emojis and choose the
color for your labels. Communicating within issues
is also possible.
•Not active by default
• Issues states limited to open or resolved
• Limited labelling and priority levels
• Basic filtering via advanced search
• Lacksmany basic issuemanagement features
Conclusion
BitBucket's issuemanagement lacks many basic
features youmight expect from an issue
management tool. It's possible Atlassian would
prefer users adopt JIRA instead.
• Project based issuemanagement
• Issues categorized undermilestones
• Custom priorities, states, and labels
• Filter by custom priorities, states, and labels
• Visualize issues in a task board (Kanban board)
or list view
Conclusion
Deveo's issuemanagement has a versatile feature
set for project based issuemanagement. Users can
set custom priorities and states, and view in a
board or list view. Deveo issuemanagement
doesn’t allow bulk editing or deadlines.
Possible tomodify toppriority levels
Possible tomodify states
Supports attachments in issues
Commenting/ Discussionunder issues
Labels
Kanban view
Possible to link to issues
Ability to set deadlines
Ability to bulk edit the issues