GitLab DevSecOps platform enables software innovation by aiming to empower development, security, and operations teams to build better software, faster. With GitLab, teams can create, deliver, and manage code quickly and continuously instead of managing disparate tools and scripts. GitLab helps teams across the complete DevSecOps lifecycle, from developing, securing, and deploying software. Differentiators, as described by Gitlab:
Simplicity: With GitLab, DevSecOps can…
$0
per month per user
Pivotal Tracker
Score 7.2 out of 10
N/A
Pivotal Tracker is a project management program primarily for software developers. It is built from the ground up to facilitate the agile development cycle, and is optimized for structuring projects in sprints, or “stories.”
The solution is now owned and supported by VMware, and is part of the Pivotal / Tanzu product line up.
As mentioned earlier, the features like chart visualization sets it apart from the others. Other than that, GitLab is open source while other are not and comparatively more secure that its other counterparts. Also, GitLab supports adding other types of attachments which is not …
When i was using the other platform, Some time i face down time, But GitLabs its not happening for single time. GitLab is having easy user interference as compared to other platforms. Pull Request, Code review, Issue tracking, Merging, Access control and User Roles is having a …
GitLab is miles ahead of the competition. In so many words, having a simple UI with robust security and the ability to conduct Git actions takes the cake. The competitions like to say they can do these things easily but their products are more confusing and hard to use.
GitLab allows a self-hosted version that is easy to setup and configure. It is also open-source as compared to GitHub. The integrated CI/CD tools is a plus, since we do not have to worry about those tools, unlike Github. The All-in-one solution of GitLab made sense for our …
Gitlab offers the best support for CI/CD pipelines and the highest degree of customisation for workflows, permissions, and integrations. The integration of BitBucket with JIRA is better than GitLab but CI/CD features are limited in comparison. GitLab's built-in Container …
Gitlab provides basic functionality like any other git tool. Some features of push and pull requests , clone and merge is handled equally well. It lacks in AI features which are there in GitHub and setup processes are difficult. Cost difference is the only concern while …
GitHub is an inferior product from most points of view. We had to use it and the teams finds no positives about it. Everything is a downgrade from our previous GitLab solution.
GitLab CI\CD is vastly superior to workflows, for example doing a manual node is just "when : manual" …
It's much simpler than the competitors. The one important feature Gitlab stand out is the CI/CD pipeline. GitHub required integration with external CI tools but Gitlab has this feature built-in. Compare to Jenkins and Teamcity, It's easy to use without any additional Plugins. …
Gitlab seems more cutting-edge than GitHub; however, its AI tools are not yet as mature as those of CoPilot. It feels like the next-generation product, so as we selected a tool for our startup, we decided to invest in the disruptor in the space. While there are fewer …
i have more exoerence in GitLab rather than bitbucket . As personally , it is good for me to understand how things is going on. i have used personally and also in organisation . It is great for developer to see there 3 months ago code and also can come up with new solution to …
Because with Visual Studio code, it was very easy for us to install GitLab in it and have easy access through the terminal and due to GitLab, it was easy to implement codes regarding API and AWS services to make our software better. Gitlens and all features help to check the …
GitLab provides a far superior platform due to it's great integration and CI/CD focus. And while in the beginning the UI might look a bit overwhelming with use you will find it way more useful than it's competitors. The variables and settings also make way more sense and it's …
My feedback may not be important here because when I joined the company they already had GitLab and we still use it due to the ability to do CI/CD Integration, deployments, debugging, code owners approval, and Jira integration. So far we have not had any major blocker that has …
Github is more open-source first and enterprise-first second in their approach. The reverse is true for GitLab. Both are exceptional products and it highly depends on the specific needs of an org
GitLab has a open-source community and great documentation that provides support resources and community contributions. AWS CodeCommit is used for integration with other AWS services in the AWS ecosystem and also have a low community and support compared to GitLab hence …
It was a management decision to use GitLab over other tools. It integrates well with RBAC using Terraform. Runners are easy to setup. Almost all the features the organization used before are available in GitLab.
For small projects or companies that do work on a few only code repositories selecting one of the git code hosting services like GitLab, GitHub, Bitbicket etc does not make a big difference.
But, if you are on a code development company that handles too many repositories and …
Software delivery is the key objective and GitLab made it much easier to hit the group quickly. It worked well with automation, and integrations with other SDLC tools used in the Organization and it is really easy to use. It's widely adopted and has the power to deliver what we …
GitLab's online IDE and code modification is much better compared to Stash. While pricier than Bitbucket, Gitlab also provides CI CD configuration better than BB.
JIRA is very user friendly. It's ideal for people new to the software development lifecycle and the tracking of the work. They have simply nailed the intuitiveness. Pivotal Tracker might be the better long-term tool because of the flexibility that comes with it. But as …
I have used a number of systems like Pivotal Tracker over the last 15 years. I have had several occasions to use Wrike separate from and alongside Pivotal Tracker. Wrike was more difficult to use and seems to either be locked down by permissions, so I had to "fight" to do my …
The only thing that PT compares to is Salesforce and we now utilize both platforms - Salesforce is a bit more organized in its automated task flow and allows us to connect our other platforms to it for efficient data transfer and data consistency.
I haven't used dev-specific tools other than Pivotal Tracker but it's useful because it is built for a specific use case. The simplicity of an Asana or Trello is great and they have their advantages, but the additional functionality mentioned was worthwhile and a compelling …
It's not necessarily a matter of better vs. worse when it comes to all of these different tools. They all serve a different purpose to different sized teams. I found Pivotal Tracker and monday.com to be a matter of preference while serving a similar purpose. Good for smaller …
Pivotal Tracker keeps users 'close' to the software project(s) by allowing users to understand, in plain words, the tasks and expectations of each software release, whereas other tools are either way too close to the source code or require an extensive amount of maintenance. …
JIRA allows teams to tailor the application workflow to meet their needs, while "opinionated" Pivotal Tracker enforces a consistent workflow approach on all team members. While I, personally, may prefer to have a system configured to my particular habits and desires as a …
We selected Pivotal Tracker because it is highly opinionated about the process. It worked quite well for what we were expecting from it. Other software we tried were much more flexible, so we could implement our own process there.
Pivotal Tracker, Asana and Trello all have free versions making them ideal for smaller companies to try out. All of them blast Kannan boards and issue tracking capabilities. While Trello and Asana are great products in themselves, Pivotal Tracker edges them out with its wealth …
I've used Jira ages ago, and it was still a young product in its initial iterations. The UI was a clunky and was missing a lot of ease with drag and drop for individual stories, uploads, etc. Management of users was useable, but not as ideal as it could be.
We selected Pivotal Tracker because of its simple, elegant workflow. This is the ideal; it's where we want to be. So we continue to improve, and as we get better, we get more out of the software.
The other software products we evaluated were too complex, and we found that …
We have had employees in the past look at Drupal, and other open source project management tools to assist in our needs. Unfortunately each solution took too much time to implement, design and configure that we could not stop the work we were doing for clients to complete a …
We were using JIRA and found it lacking in their UI and some of their services, especially communication. PT communicates much easier with simple links to tasks for execution and QA review.
Basecamp is just really a super note taking and asset depot. I would not consider true …
Compared to other task management tools, Pivotal Tracker has the best blend of functionality and cost. When you need something simpler than Jira, and not solely focused on code or UI related tasks like BugHerd, and have a more direct approach to completing tasks than Trello - I …
Pivotal Tracker, for better or worse, provides a more structured and rigid workflow than most. That makes it easy to get started, but if you have your own workflow you want to integrate into it, it could mean it'll take longer to get used to or customize. It's still more …
Our organization actually does not exclusively use Pivotal. We also have teams on solutions like Trello and LeanKit. It's all preference, those who buy into all the agile features that pivotal provides, love it. Those who do not need all the overhead, simply use a different …
Rally is too complicated - there are far too many fields that all have the same meaning. It's a better agile tool in my opinion since it it was designed purely as an agile tool, but since the CA technologies acquisition, the tool has become more complicated and there are far …
Compared to Rally the tool seems more accessible because or the suite of apps available. It also feels more polished and stable than Rally. It definitely has more tools and features but again it can be overkill for a smaller team or project.
Overall I have found that I prefer using Pivotal over all the competitors I've tried. There are certain aspects of the other products which I do like but as a whole Pivotal does a better job. My one request is that I feel it is very much a web app and the other products have …
I have also used Trello and Jira. A small company with only a couple of projects may be best suited with Trello due to its cost and simplicity, whereas Jira may be better suited for a large company that can afford a dedicated Jira manager, due to its complex configurations and …
Jira is very complex, while tracker is more straightforward to use. Tracker requires less micromanagement and upkeep. Asana is pretty but not useful for product and engineering build. It is more geared towards design projects.
It is well-suited for any project that needs VCS. It's an excellent choice for teams that might be remote or have to collaborate across teams. Plenty of features allow for async working. With its dashboards and reporting features, it is also suitable for nontechnical PMs or stakeholders. It allows for very bespoke customization and can most often do much more than you need it to.
The UI of the Pivotal tracker is really beautiful and amazing, which looks trivial, but we have it open all the time, so it's nice for us. In Pivotal tracker for me its very Easy to create tasks or stories anytime without facing any problems. Pivotal tracker provides us a ton of features to track the tasks and manage a team and the projects. Pivotal tracker allows for a entire team to be on the same page of the tool in regards to where is the project right now, right status of every task, what is being worked on and by whom.
Pivotal Tracker helps our team visualize our projects in the form of stories (virtual cards) moving through our workflow. This encourages us to break down projects into manageable chunks and have important conversations about deliverables and scope.
The forced-prioritization allows our team to have a shared understanding about what is most important and make collective decisions about what our team will work on next.
By dividing future iterations by our team's velocity, Pivotal Tracker accurately predicts when we will complete future work.
Used to have a newsfeed-type feature with all the updates from the previous day. They removed it. I liked getting a snapchat of what changed from before.
When signing up for email alerts, can be inundated with emails for every change to the status of a story.
Communication on stories through the comment section can be a little difficult, and not very organized.
I really feel the platform has matured quite faster than others, and it is always at the top of its game compared to the different vendors like GitHub, Azure pipelines, CircleCI, Travis, Jenkins. Since it provides, agents, CI/CD, repository hosting, Secrets management, user management, and Single Sign on; among other features
I find it easy to use, I haven't had to do the integration work, so that's why it is a 9/10, cause I can't speak to how easy that part was or the initial set up, but day to day use is great!
It works good enough. I didn't have many problems with that. The user interface is a bit confusing though. The team took some time to understand where some configurations were.
I've never had experienced outages from GItlab itself, but regarding the code I have deployed to Gitlab, the history helps a lot to trace the cause of the issue or performing a rollback to go back to a working version
GItlab reponsiveness is amazing, has never left me IDLE. I've never had issues even with complex projects. I have not experienced any issues when integrating it with agents for example or SSO
At this point, I do not have much experience with Gitlab support as I have never had to engage them. They have documentation that is helpful, not quite as extensive as other documentation, but helpful nonetheless. They also seem to be relatively responsive on social media platforms (twitter) and really thrived when GitHub was acquired by Microsoft
We've never had to request support in the 5 years I have been using it. A solid solution! Everything I have had questions about is on the website. New features are in their newsletter with more details on their website. Often I am using the new features within a few minutes of reading the article.
GitHub is an inferior product from most points of view. We had to use it and the teams finds no positives about it. Everything is a downgrade from our previous GitLab solution. GitLab CI\CD is vastly superior to workflows, for example doing a manual node is just "when : manual" in GitLab while you have to do clickops in GitHub to achieve the same. No overview of code in branches is a minus when we tried to figure out what our colleagues are trying to merge as it looked off.
Pivotal Tracker, Asana and Trello all have free versions making them ideal for smaller companies to try out. All of them blast Kannan boards and issue tracking capabilities. While Trello and Asana are great products in themselves, Pivotal Tracker edges them out with its wealth of features including trackability of epics, burndowns, better reporting, and analytics. JIRA, on the other hand, is way more customizable, has more reporting capabilities and more features than Pivotal Tracker but is more expensive too. At the end of the day, it comes down to what you're looking for in an agile project management tool as well as how much you're willing to pay for it.
Pivotal Tracker has been a cost-effective solution for what we need. It has allowed our ROI to be greater than if we went with another system.
Learning curve; with this easy to use tool, it has been a shorter learning curve for new hires to find what they need to accomplish their task.
Flexibility; we are right now stuck at 4 levels of classification; project; Story, Task, Comments. If we were able to expand on this, we would be able to role this out faster to other departments within our business.