Web development team relying on JIRA
Updated July 08, 2015

Web development team relying on JIRA

Bo Acimovic | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User

Software Version

JIRA v6.4-OD-02-003

Modules Used

  • Jira Agile

Overall Satisfaction with Atlassian JIRA

In our company JIRA is used by our Web Development teams. We have teams in multiple locations and need a good project management tool. As an in-house web team, we develop various B2B websites and internally used web based tools. Keeping track of every part of the team is essential. This can be a challenge when working in a global company with teams in different time zones. With JIRA, we are able to create and assign tasks to any team member and be sure that it will be taken care of. Implementing JIRA in our work routine also helped us bring a good and efficient workflow to any type of task.
  • Workflows. Being able to define workflows for any type of a task, helps with keeping that task on track. Additionally, you can trigger various actions when a task hits a step in a workflow, like automatically re-assigning a task to a specific team member.
  • Dashboards. You can organize your JIRA dashboard any way you want and you can have as many dashboards as needed. This helps when preparing for team meetings and generating reports.
  • Customization. Being able to customize JIRA is great. It allowed us to adjust the use of the software to our needs and not the other way around.
  • JIRA is missing an iOS app. Even though there is a mobile version of the site, it is not easy to work in. As a manager, I receive a lot of JIRA related emails. Being able to answer questions or make changes on the go would be very helpful.
  • You are able to embed a form outside of JIRA that would upon submitting, create a new JIRA task. We use it for submitting tickets. Once a ticket has been closed, there is no automatic way of informing the requester about the resolution.
  • Better tracking of tasks/issues
  • More accurate prediction of project completion dates
  • Better task distributing
  • Better task categorization
What appealed to us with JIRA at first sight is pricing per user. It may sound funny, but for us this was better than pricing per number of projects. Most of our projects are ongoing. Once an initial development is done, we continue maintaining the software and keep track of tasks. So we have a steady number of people but are not sure about the number of projects we might have.
JIRA is perfect for web/software development projects. That being said, I couldn't find it suitable for any other types of projects. JIRA also requires a certain knowledge of agile project management. Anyone not familiar with the concept might struggle to use that part and could make everything more complicated. Do not expect JIRA to tell you how to manage your projects. This tool is highly customizable and in order to fully use it you must have your processes defined. It took us five days to set up workflows, task types, reporting and everything else. This is crucial if you do not want to have your team members struggle.

Using Atlassian JIRA

JIRA is a tool that gets updated regularly. This is a sure sign that there is a company behind it that is always improving the quality of their product. This means we can rely on usage of this tool for years to come. Considering we have a lot of projects and tasks in JIRA and knowing it's a tool with a future we will definitely keep using it. Also, even though we don't attach a lot of files to our tasks, I don't think there are any storage limits.

Jira Implementation

Take your time implementing Jira. Make sure you understand how you want to handle your projects and workflows. Investing more time in the implementation can pay off in a long run. It basically took us 5 days to define and implement correctly, but that meant smooth sailing later on.
Change management was minimal
  • Defining workflows
  • Understanding various project types

Jira Reliability