JIRA Portfolio Reviews

Everyone mentions tasks using JIRA. It is used for various everyday tasks, including dashboards, sprints, backlogs, and workloads.

It has been very efficient for internal communication and managing different data and work projects. It tracks the progress, the development, and more. 

It is one of the important tools and one can easily maintain and manage the tasks in JIRA. 

The workflow and bucket features are most helpful. We never have code changes without a linked JIRA case. Code changes are linked to JIRA, and you can see the code changes within Jira.

 The roadmap in our capacity planning features impacted the project management. We're transitioning from Bitbucket to GitLab and JIRA, which are linked to GitLab. This change is necessary due to this transition.

The focus will be on commits. The focus will be on checking the message, confirming drastic data as a prefix. If not, then the commit will be rejected.

The products are getting bigger. So, learning JIRA is not so easy. There is a learning curve. 

It is not easy to understand all the workflows. 

I have been using it for seven years. 

I would rate the stability an eight out of ten. Sometimes, if you have a version change, even if you follow the process of "open," "in progress," "in review," "progress class," then "closed branch," and finally "close Jira," you might only change one line of code. But you still have to go through the internal process. It's modified coaching. It still goes over the entire process in ten minutes.

There are around 500 end users in the company. 

The customer service and support are good. 

We have a standalone team for the setup. 

It provides the most functions and is very agile, lean scrum. 

Overall, I would rate the solution an eight out of ten. 

I would recommend JIRA. It is based on Agile only. So if you want to learn JIRA, you first learn Agile office knowledge or cloud or function, something like this. Then you can understand JIRA too.

We use the solution for software development management. It includes the timeline and the requirement definition.

As a project management team, we’re supposed to manage the teams that develop different products. It can be hectic if we don't have a tool. With JIRA, it's very easy and seamless. All the teams can give their updates, check on their backlogs, and work on them.

The ability to move across various stages from solution discovery to completion is valuable. We can assign specific tasks to users. We can also see the timeline and the progress of the projects. It makes our work easy and efficient. The tool helps us achieve more within the stipulated timeline and budget.

JIRA and Confluence must be linked automatically. What I change on JIRA must be updated in Confluence if it is related. If a task has been completed in JIRA and is mentioned somewhere in Confluence, the status must also be updated on Confluence.

I have been using the solution for one year.

I rate the tool’s stability an eight out of ten.

The product is scalable. I rate the scalability a nine out of ten. Approximately 50 people are using the tool in our organization. We are planning to increase the usage in the future.

I rate the ease of setup an eight out of ten.

I rate the pricing a six out of ten on a scale where one is cheap and ten is expensive.

Before using the solution, we were working manually. I would recommend the solution to others. Overall, I rate the tool an eight out of ten.

We use it for ticketing and project planning, and documentation, mainly for ticketing, department-wise ticketing, for the creation.

The most valuable feature for me is the visualization and organizing of the tasks. We can have a pick, and then we can stick the multiple issues under that, and then we can again have a sort of hierarchical installation, and that's very useful. 

And I've even worked with multiple analysts, like, for services, and I work on Jira. 

There is room for improvement in terms of scalability. 

I have been using this solution for five years. 

The solution is very stable. I would rate the stability a ten out of ten. Everyone in our organization use Jira. So, there are more than a thousand end users. 

I would rate the scalability a nine out of ten. There is some room for improvement.

We experienced one to two downtimes in a year. However, it was supported by our internal tech support team.

I have worked with other solutions as well but as far as my real experience, one of the best tools that they can go for is Jira.

We are using the SaaS version, so we need to set it up on our own site.

Just the user sign-up, and then the central SSO system. We have our own SSO with Microsoft Azure, so it should be pretty straightforward.

Overall, I would rate the solution a nine out of ten. It is a good solution. 

The primary use case is project management. 

The entire features that are required for managing the product's communication between the team there are valuable. Managing product development and managing inter-team communications are also valuable features.

Maybe integration with other tools could be made easier. 

I have been using this solution for three years.

I would rate the stability a nine out of ten. There was no downtime, no issues.

It is a scalable solution that's suited to our requirements for small teams. I'm not sure about larger teams. So, it's limited to whatever users it has. So that's suited to our requirements.

I would rate the scalability an eight out of ten, as far as my experience goes with the tool, but I haven't used it on a larger scale.

I never needed any support. I'm a primary or maybe average user, so nothing extensively that I've used. So I have never needed any support.

It was absolutely easy to set up and work with Jira, so that was absolutely easy.

Jira is a SaaS solution, so there is nothing to be deployed. It's an on-cloud solution.

Currently, I use the free version for personal use.

I find it simple compared to Azure DevOps. Comparing both Azure DevOps and Jira, then Jira is simpler compared to DevOps.

Overall, I would rate the solution an eight out of ten. It is a good tool and easy to use. It is very easy to start using the tool. It is very easy to understand and use the tool.

We are using JIRA Portfolio life cycle management.

The solution can be deployed on the cloud and on-premise. However, most clients choose cloud deployment. Not all of our clients have their own database.

The most valuable feature of the JIRA Portfolio is for managing teams of 10 or more. It can track the program level and portfolio. There are plenty of beneficial features, such as the hierarchy-level view, customization, and structure plugin. 

The interface JIRA Portfolio could improve.

I have used JIRA Portfolio within the last 12 months.

I have not faced any challenges with the stability of the solution.

I rate the stability of the JIRA Portfolio a six out of ten.

The scalability should improve in JIRA Portfolio.

I rate the scalability of JIRA Portfolio a seven out of ten.

Sometimes there are difficulties receiving support from the vendor. They do not answer immediately.

I rate the support from JIRA Portfolio five out of ten.

Neutral

The setup of the cloud deployment is simple. The solution has over 2,000 plugins and research is needed to determine which one is the best to use and implement.

The cloud deployment takes a few clicks from the mouse to finish. It can be done quickly.

The solution should be overall more user-friendly.

There are free plugins available, but most of them are at an additional cost. Additionally, other services are an extra cost.

This is a great tool for life cycle management.

I rate JIRA Portfolio an eight out of ten.

We use JIRA Portfolio to implement the scaled agile methodology and conduct retrospectives. It's also used by us for writing bugs and managing our daily structure.

The workflows are the most valuable feature of the solution, whether for tasks, bugs, or chain requests from the site. I also like the solution's GUI, which is easy to navigate for everyone.

I think the solution can improve in graphs and the analysis part.

Considering what I would like to see in the solution that could simplify my life, I would like to mention Miro. Currently, we have to visit Miro specifically to carry out PI planning.

I use the cloud version of JIRA daily for the standards and traceability of defects coming from a point. I am unsure whether I am using JIRA Align or JIRA Portfolio. However, I think it is JIRA Portfolio because it has everything developed adequately for dev track, dev caller, and dev dash. Also, it has everything JIRA provides.
I think I have been using JIRA for three years. Also, I'm not sure about the version of JIRA that we are using in our organization. Since I work for a very big company in the Netherlands, the company manages all the tooling-related matters. So, only the testers and developers have access to the version information.
I am a customer of JIRA Platform.

The integration platform for the tooling now available is very easy to use, requiring no expertise in computer science engineering or any such related fields. Simply select the desired options from the provider's interface and use the tool without the need for explicit configuration. For these reasons, I rate this solution an eight out of ten.

I use the solution in cases when I need to report something such as escalating a scale. 

The solution includes good and fast notifications for other project team members. 

The solution's look and feel could be a bit more intuitive and user friendly. 

I have been using the solution for one year. 

The stability is rated an eight out of ten. 

The scalability is rated a seven out of ten. 

The technical support is good so is rated a nine out of ten. 

Positive

It is important to learn about the solution's functionalities and features to prepare for use. 

I rate the solution an eight out of ten. 

We use the solution for tracking stories or issues. Developers create tickets, and project managers track everything using Jira.

We can track the open stories or open issues that are there. That's the most valuable feature that I find.

The solution is stable and reliable.

It's scalable and allows for various configurations. 

I don't have much exposure to it. We use the tool to a minimum amount.

The integration needs to be done with different tools. In terms of email functionality, if we have an email, it would be helpful to provide the status updates or notes directly configured via email. 

I've used the solution for a couple of years. 

It's a stable solution. There aren't bugs or glitches. It doesn't crash or freeze. It is reliable. 

It is scalable. It's used with multiple tools as well, so we can do various configurations if we need to.

The developers use it. We have about 2,000 or more users that use it within the company.

I've never dealt with technical support. I cannot speak to how helpful or responsive they would be.

The initial setup was handled by somebody else. I can't speak to how easy or difficult the process was. 

I'm not sure how many people are maintaining the product.

I don't deal with the pricing or licensing aspects of the solution. 

This is a good solution overall. 

I'd rate the solution seven out of ten.