292 Jira Software Testimonials

"Using Jira Cloud helps us have one less backend system that needs operational support and maintenance. We also have offices in multiple countries, so using the cloud version of Jira and Confluence helps with performance since we don’t have a local server.”

"[Integrating Atlassian Access and Okta has been] such a big improvement. I almost can’t imagine what it was like before."

“We have 1,000-2,000 people coming through each ship during a 10-month field service [the time a ship spends in an African port]. In order to maintain output and minimize brain drain when people turn over and when new ships are built, we need to store procedures for everything onboard, from making the perfect coffee to how to operate the engines, deal with cargo, surgical procedures, etc. We wouldn’t be able to do that without Confluence.”

“I noticed progress was not being made on a specific epic, and then when you drill into it in Portfolio’s scope table you realize the status of a lot of stories are code complete. This led me to identify that we need a better process for making sure things get reviewed. I can see where bottlenecks are. This was a nice efficiency gain.”

“Jira brings a lot in terms of a ‘social networking’ feel, in that you can track people’s interactions. I live in Jira, I love Jira, I’m in Jira every day. Without Jira, I wouldn’t be able to do my job nearly as efficiently, and in some cases at all without Jira.”

“The richness of information stored is the main benefit. Jira is a key critical thing to answer customer questions and address customer requirements.”

"Ultimately, the fact that Jira allows SAF to work smarter means more Montana foster care youths get laptops and the supplies they need to pursue their dreams of higher education."

"To see what’s going on underneath the covers – that will be lovely. And Jira can help us set resources for the team and also set expectations for the business. As I’m a liaison with the end users, I want them to be a lot more engaged and a lot happier with how we do their work for them.”

“No code should be committed to the source repository unless there’s a Jira issue attached to it.”

"There is a single instance of Jira used for working with all Siteworx clients. Most clients use a single project, but some use more. There are currently over 100 projects with thousands of issues. Siteworx likes to keep a streamlined instance with up-to-date versions and plugins. The current instance has a few security customizations and custom workflows running on version 4.0.1. An upgrade to the latest version should take place in the next month or so. It is used mostly for task and issue tracking between Siteworx and the clients, but it is also used internally for help desk, recruitment, marketing and proposal management."

“it would be nice to see the history on my source code.”

“I was really struggling to see what the bigger picture looked like. It just made me and my team frustrated because it was so difficult to keep the scope and plan of releases aligned. Our Jira Software issue lists were way too long, so all anyone could easily see was what’s ahead for the next three weeks.”

"Of course we all try to avoid it, but sometimes an effort gets resized; this could be due to new customer requirements or if the tech team unearths a roadblock. At that point, most often, everything after gets pushed back. With Portfolio for Jira, it’s really easy to update my roadmap and see what’s moving and what my new delivery dates are. I don’t have to resize work items in Jira Software and then go into another tool to calculate what needs to move. Those days of spreadsheet hell are over.”

"Since all the teams were already using Jira Software, it’s not like we had to maintain two different systems to report on the status of multiple teams. As long as people are updating their Jira tickets, then the plan in Portfolio for Jira is updated as well. It was better to just look at what we’re doing all in one place in Jira."

"Atlassian tools have become key to our teams. We can't afford downtime or latency. We need around the clock access without compromising performance."