GitLab
vs
BluePrint Storyteller
Comparison
Comparison
Blueprint Storyteller is a visual application modeling tool that enables creating process models, design artifacts, and includes workflow to manage the lifecycle events and collaboration of the artifacts.
| FEATURES |
|
|
|---|---|---|
|
Issues
Quickly set the status, assignee or milestone for multiple issues at the same time or easily filter them on any properties. See milestones and issues across projects. |
|
|
|
Labels
Labels provide an easy way to categorize issues, merge requests, or epics based on descriptive titles as ‘bug’, or ‘documentation’. |
|
|
|
Burnup Charts
With Milestone and Iteration Burnup Charts, you can better understand scope change during a sprint or while working on a new version of your software. |
|
|
|
Burndown Charts
GitLab provides Burndown Charts as part of Milestones and Iterations. This allows users to better track progress during a sprint or while working on a new version of their software. |
|
|
|
Project Issue Board
GitLab has Issue Boards, each list of an Issue Board is based on a label that exists in your issue tracker. The Issue Board will therefore match the state of your issue tracker in a user-friendly way. |
|
|
|
Group Issue Board
Issue board scoped at the group level, so that you can view issues in all projects of that group. |
|
|
|
Multiple Project Issue Boards
Large companies often have hundreds of different projects, all with different moving parts at the same time. GitLab allows for multiple Issue Boards for a single project so you can plan, organize, and visualize a workflow for a feature or product release. Multiple Issue Boards are particularly useful for large projects with more than one team or in situations where a repository is used to host the code of multiple products. |
|
|
|
Single level Epics
Plan and track features and work group level epics that collect issues together. Easily create and assign Issues directly from the Epic itself |
|
|
|
Multi-level Epics
Plan and track strategies, initiatives, and features with multi-level epics. Organize and prioritize work across multiple children epics and their issues within the Epic Tree. |
|
|
|
Confidential Epics
Organize a collection of related confidential issues into a confidential epic, allowing you to manage sensitive work more efficiently. |
|
|
|
Roadmaps
Visualize multiple epics and milestones across time in a roadmap view. |
|
|
|
Portfolio-level Roadmaps
Establish product vision and strategy, gain progress insights, organize, govern and shape the effort of multi-disciplinary teams with portfolio-level roadmaps. |
|
|
|
Planning hierarchy
Using epics and issues together results in a planning hierarchy that spans groups and projects. This allows multiple layers of breaking down work and better organization. Hierarchy starts with single level epics in Premium. It becomes more flexible with mult-level epics in Ultimate. |
|
|
|
Out-of-the-box Agile Reporting
Teams have access to more than a dozen out-of-the-box reports with real-time, actionable insights into how their team is performing sprint over sprint. Example reports are sprint burndown, epic burndown, cumulative flow diagram, velocity chart, burn up chart, and sprint report. |
|
|
|
Issue Analytics
See issue analytics at the group level. |
|
|
|
Requirements Management
Gather, document, refine, and track approval of business and system requirements. Define traceability between requirements and other requirements, code, or test cases. |
|
|
|
Satisfy Requirements from CI/CD pipelines
This powerful feature uses the GitLab single-application model to allow testing run in the CI/CD pipelines to satisfy your requirements. This automates the cumbersome task of identifying satisfied requirements, and enables your organization to focus on delivering value. |
|
|
|
Import & Export Requirements
To better collaborate with external groups and organizations, requirements can be imported and exported in CSV format. This allows teams to use a single interface for development and testing against requirements. |
|
|
|
Merge Requests
Create merge requests and @mention team members to review and safely merge your changes. |
|
|