JIRA Portfolio Reviews

With Jira software, I can implement DevOps. The Jira Software Management is a part of the ITSM, incident management, for the principal features of the software. It's basically used for DevOps and the ITSM.

I like the Jira Software Management. You can attend to many areas for the customer. For example, I can support IT as well as the financial areas. Jira Software Management is very important for the customers for this reason.

The initial setup process is simple. 

We have found the solution to be stable.

It is highly scalable due to the cloud.

Technical support has been great.

The HR aspect of the solution could be improved. 

I've used the solution for one year. I started to work with Jira when I started with my organization.

The solution is very stable. There are no bugs or glitches and it doesn't crash or freeze. It's reliable. 

Scaling is easy as the software work in the cloud. That makes it very simple to scale the software. It's no problem.

We have a lot of users on the solution currently. 

Technical support is good. they have been helpful and responsive for the most part.

Positive

We have found the implementation process to be simple and straightforward. the setup is not hard. I'd rate it a four out of five for ease of use.

The deployment takes about two months. Of course, it depends on the customer and varies a bit. 

I do not have any knowledge of the licensing cost.

We are just customers. We don't have a business relationship with Jira.

It's important to know about the database. It is important to know about databases for implementing Jira Software Management.

I'd rate the solution a nine out of ten.

I work in hybrid technologies. Right now I work in service management. Our software disc space uses JIRA Portfolio. I've got a DevOps team and a team that works with operations. There are different elements within service management that we use JIRA to build team plans.

The number one feature is that the product makes it easier to collaborate. I think that is the most important point even though it is not perfect. Another point is that the interface is not exactly rocket science and it is fairly easy to learn. It is very much driven towards use like Microsoft or any of the other core applications available. For project and portfolio management and in terms of incident management — things like that — it is not that complex. To rate it on a scale of one to five as to what it needs to do in this category, I'd give it a four-out-of-five.

It is easy to get help from the community. So that is also a bonus. But that is like the situation with most software now.

I think to improve the product they need to work on integration. I think what I call heterogeneous integration into other tools will be important. It would be nice to work with data modeling from any tool. From an enterprise reporting perspective, you definitely want to be able to take core data, put it into any sort of raw database and be able to manipulate it to get the information you are looking for. I think the reporting side is probably where JIRA is not the strongest product in my view. Needed improvements just boil down to an improved integration.

I know it is always going to be a challenge to add new features, but I think better integration around Microsoft or other core applications would help. I think big data warehousing is important. Enabling RPA for the benefits that can offer would help as well.

Stability is debatable because you are not doing a lot of batch management. It depends on your operating system. The benefit of using a cloud implementation is that in an on-prem solution you are always responsible for maintaining your own infrastructure, hardware, backups, doing maintenance — all of those components. But that is not really a major issue for stability.

If a product is a true enterprise product, then scalability should never be an issue. If you are not working with an enterprise then you are doing a cloud-based solution and it is definitely scalable as well.

There are probably teams of around 50 in our organization, mostly made up of end-users. Obviously we have admin people and we had OEM support. But the solution is scalable to meet our needs.

We have mostly been satisfied with our customer support experience. Customization is a bit tricky, so you have got to really understand what you are trying to achieve. Technical support was able to help us through some issues.

If I look at just on your ITSMs (IT Service Management) side, I've used ServiceNow. Also, HP Service Manager.

I do not think the initial setup was complex.

We got maintenance support from our vendor. It included time and material when we made the contract for support.

When considering the product solutions, I was looking for functionality comparisons between an SDM (Service Desk Management) BMC (Baseboard Management Controller) remedy. I'm sort of interested to understand what are the major benefits or differences between those two. I think that was really where I was trying to just get some help. I've got a team of about 169 people in the project and I was just trying to see where I could get information very quickly without having to go to the vendors. A lot of resources just house people with more questions than answers.

If you are looking for collaboration, then I would definitely recommend the product. It is one of the easiest and not very expensive.

On a scale from one to ten where one is the worst and ten is the best. I would rate the products overall as a  seven. It could not get a ten. Seven leaves room for improvement.

I primarily use the product to collaborate with the product and engineering teams. Depending on the product stage, I may draft or review the PRD, providing feedback for improvement. I use it to plan and schedule the things I take care of. I can create and share a document if I want to discuss new ideas with my team remotely. 

Before, I used Excel, but switching to this tool has been a significant improvement. It's much more collaborative and user-friendly. With many functions, entering and processing data is easier and faster. I can easily link documents to clients and perform tasks like inserting tables with simple commands, which helps speed up my work.

Jira Portfolio is part of our standard operating procedures to ensure product functions run seamlessly and smoothly. Providing people with sufficient tools to collaborate effectively is crucial to achieve this. Jira has become the go-to document processing tool for facilitating this collaboration and ensuring productivity. Every aspect of the product is critical for your workflow, whether gathering input from team members or seamlessly writing and managing documents.

We are based in India; I would like the product to integrate local pricing. We earn in rupees but spend in dollars. Its pricing could also be lowered. 

I have been using the product for three and a half years. 

I haven't encountered any stability issues. 

I haven't contacted the technical support team personally. 

Jira Portfolio's deployment is easy. We started by signing up for the software's seven-day free trial using our credit card.  After the trial, we decided to opt for a paid plan based on the number of licenses we needed. As for any custom plans or requirements, we haven't reached that scale yet, but we know we can contact their team for further discussions when needed.

Integrating Jira Portfolio with Slack, Camunda, and other tools is part of our standard operating procedure. It helps in coordination. However, I didn't handle the integration myself. Instead, I relied on a team of more experts about the product. 

Our team has worked with the product previously and didn't need to overcome learning curve challenges. 80 percent of my organization is well versed in it. They can help people who don't know the product. I rate it an eight out of ten.

We use the solution to create a unified roadmap that allows us to track investments and actuals. Additionally, we need a single view that displays the work items assigned to each value stream, and we need to prioritize these items according to the WSA technique.

The most valuable feature is the dashboard where we can see all of our projects and apply filters to shortlist those projects.

The reporting has room for improvement. We were working on a project, trying to figure out what our task was and when the start and end dates were. This wasn't too difficult, as we had all the information we required, however, we had to align a lot of data in order to get the right information, which was a bit of a hassle.

The initial setup could be more user-friendly. Additionally, it's important to consider portfolio-level metrics. Having more portfolio-level metrics would be beneficial.

With Jira, an issue that arises is the length of time it takes to show certain data. If this could be sped up, the user experience would undoubtedly be improved.

I have been using the solution for one year.

We have some issues with the stability.

The solution is somewhat scalable.

Tech support can be reassuring but requires some effort to get the answers we need. We have to search through conference pages to find solutions, which may take some time, but we can purchase a service that provides ongoing support.

The initial setup is not straightforward. 

We don't take a big-bang approach. We start by deploying one piece of art and then presenting it to the leadership. They need to have an overall view of how it's progressing. If all the necessary data is available, it may not take more than two weeks to implement.

To properly implement, it was important to first tag the teams and their respective tasks and to assign them to the relevant ethics. Additionally, it was also important to set deadlines for the completion of the tasks. One of the biggest challenges is people not putting in their estimates, which hinders accurate tracking of progress.

I give the solution a seven out of ten.

We have one person per year using the solution.

There are several features that I like. For example, the way we can categorize the statuses of our tasks is great. We can build any number of columns to show the different status of the progress status of our task.

It is customizable and offers great integration with other products, like HP or ASD portals or any other third-party portal. 

The solution can scale.

Its stability is very reliable.

Technical support is always responsive. 

I don't much have developer insight into the Jira tool, however, it would be nice if it could provide an end-to-end solution for a project. For example, I'm from the SAP field. In SAP, we have something called SAP Chart or Solution Manager, and there you can create tickets and you can monitor the progress. You can manage the end-to-end scenario from development to go-live. If those features could be incorporated into Jira, it'll be a full package.

I've been using the solution for three or four years at this point. 

The stability has been great overall. O haven't dealt with bugs or glitches. It doesn't crash. It's reliable. 

We have found the scalability to be good. If you need to expand Jira, you can.

Technical support has been pretty good. Whenever we face an issue, we have an email with an ID number was can share with the Jira support. Instantly we get an acknowledgment that the issue has been received and they're working on it. 

I'm more of an end-user and therefore I was not involved in the initial setup.

There were a few colleagues that handled the initial implementation. 

I don't have any details in terms of licensing or costs. 

I'm an end-user. I'm not overly technical. 

I would rate the solution eight out of ten.

I am a software developer and we use this product for end-to-end SDLC. It begins with the requirements gathering, then continues with tracking features and planning our sprints. We also use it for tracking bugs.

The most valuable feature is that it fits very well into an agile framework, and it is especially helpful with the planning aspects. For example, if you create a new ticket, issue, or feature, then you classify it accordingly and you can assign it to an ongoing sprint.

You can look at the sprint backlog to see what features are planned, how many are in progress, and how many have been completed. This helps during reviews because you can get information about the velocity of the team. If somebody should leave the team for a while, or are otherwise unavailable for work, then the velocity calculations are readjusted.

Converting a task into an epic is very troublesome. As it is now, if you make the mistake of creating the wrong thing then you just have to delete it and start again. If you could convert between things such as features and tasks then it would be helpful.

I have been using the Jira Portfolio for about four years.

We use Jira on a daily basis and I cannot recall having any issues with stability.

It is easy to scale but of course, the problem is that it needs licenses. As the licenses fit into a plan, it can be kind of tricky. When you want to procure additional licenses, it is a long path.

For example, if you have licenses for 50 users and you see that you need a license for another 10, then you can't just purchase a small number. At a certain point, you have to move up to 500 users, which is quite a jump.

Currently, we have about 60 users.

I have not been in contact with their technical support team, although I do go through the community forums. I get details on new features that are going to be released and other such information, but I have not had to contact support for any specific issue.

The initial setup is pretty straightforward. Somebody who knows Agile well will have no difficulty with Jira. On the other hand, somebody new to Agile may face some problems in the beginning. 

We do not have any dedicated staff for maintenance. For the operation of it, we do have a facilitator and a scrum master who manages things for each project. However, maintenance is very straightforward. We don't need a full-time administrator working on it. A couple of people working part-time can take care of it.

Internally, people within a project may need some help when it comes to things like planning. In this case, they will get help from the scrum master.

We pay our fees annually, although monthly payments are also available.

From a developer's perspective, this tool works fine and I don't have any complaints other than wanting to convert between features, tasks, etc, when a mistake has been made in creating one.

The only advice that I have for people who are implementing Jira Portfolio is to make sure that they manage their licenses properly.

I would rate this solution a nine out of ten.

The primary use case for this solution is to manage the work that has to be done, everything else is on a repository that is maintained by another tool.

It's how the work has been designed at the beginning of the project. We have one repository where we store all of the requirements, the testing, and all of the activity trackings are done in JIRA.

The deployment model was on-premises.

There hasn't been an improvement because we were using JIRA solutions before.

It is difficult to narrow it down to features. It's one solution as a whole and to point out certain features is complicated.

There could be many things that could be improved but we haven't been working with it long enough to accurately find the weak points.

The pricing of add-ons could be improved. You should have the option to pay only for the users concerned, that would be fine, because of the dashboards everybody has access to the dashboard.

This solution is not able to be integrated with other solutions because you have to upgrade it and pay for more licensing.

This solution is stable.

This solution is scalable.

I have not had any experience with customer service or technical support.

Our IT department handles this area.

Our IT department completed the initial setup, so I am not sure how complex it was.

The implementation was done through our IT department.

The pricing of the solution is expensive. 

When you install any add-on, you have to pay for each and everyone who is declared on the system in order to have the add-on working. If you have anywhere from one hundred to five hundred users and even if you only have two hundred users using this solution, you have to pay for them all.

We evaluated other options but JIRA was already in place, which is one of the reasons we stayed with JIRA.

We are dealing with several products and clients, and each product has it's good points and it's weak points.

I don't have an opinion because I think that a good process does the job and you can apply a good process to any tool. 

The tools are more and more user-friendly. Even JIRA.  

When you want to implement something, keep it simple and it will work.

With JIRA, you can do amazing things by developing connectors, embedding features, and adding new fields to create new things.  

In the end, it needs to fit the process. If the process is of poor quality, then your tool will look poor.

For the most part, with several tools, you can do nearly anything.

JIRA is a good tool. Perhaps a little bit too much to configure and adapt, because it can be adapted to any kind of customer's needs and it's not dedicated to a specific solution, but it does the job.

I would rate this solution a seven 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.