TrustRadius
JIRA Software is an application lifecycle management solution for software development teams. It allows users to create, prioritize and track the progress of tasks across multiple team members, and offers a wide range of integrations. It is offered via the cloud and local servers.https://media.trustradius.com/product-logos/Do/VE/SNKZVM5Z3C0V.PNGGet agile with JIRA SoftwareMultiple teams within our organization use JIRA Software, including Product Content Strategy, Product Design, Product Education, Product Research, Front End, and Dashboard. Each team uses JIRA a bit differently, and each team's "project" is therefore set up a bit differently, but all of us follow a kanban agile structure. JIRA helps us stay on top of our tasks, view progress, and ensure all necessary work gets done on time.,JIRA offers a lot of integrations that really improve our work. For example, the Salesforce integration makes it really easy to link Salesforce product roadmap cards (relevant to the entire product team) to an individual JIRA issue (one specific task-relevant to that team). JIRA offers very good search and filter functionality. The quick filters make it very easy to immediately see only my own issues. You can create custom views, which are especially helpful for my team during our daily standup, allowing us to only see relevant issues. JIRA issues come with lots of customizable fields. Due dates, assignees, labels, priority level, epic link, etc. -- makes it very easy to organize and find specific issues.,Our team happens to have many steps within the workflow, and therefore we have more columns than other teams. JIRA Software always displays all columns in one static view. Because we have so many columns, each column becomes very skinny and the issues can be difficult to parse. We can't reduce our number of columns, so I wish we had the option to side-scroll instead of fitting all columns into the current browser size. We would love the ability to create CLEAR multiple statuses within a column. You can create multiple statuses for a column, but they all appear together and are difficult to distinguish. It isn't possible to move an issue from one status to a different status within the same column. You have to drag the issue into a different column, then drag it back into your chosen status, or change the status using the issue dropdown option. A minor nitpick, but I wish I could create an issue and immediately put it into our "To Do" column. Instead, it automatically goes into our backlog. Then I have to go to a different page to move the issue from backlog to To Do.,9,JIRA Software streamlines communication between different teams -- I can look at other teams' JIRA projects to see the status of individual issues without having to directly ask any colleagues. JIRA exponentially improves our team's productivity. We have a daily standup where we go over our JIRA project, and this allows us to focus on slow-moving tickets and identify blockers. It really helps to see the issue "physically" moving down the line, closer and closer to finish. JIRA improves our team's visibility. Often it feels like our work goes under the radar, but with JIRA, other teams can track our progress and view our contributions to new features.,7,7,Trello and AsanaJira for Enterprise BusinessJIRA is being currently utilized as a second tier ticketing and workflow management system. Our users create a ticket in our regular ticketing system for an enhancement and such. Once it has been approved a ticket and sub tasks with all the detail are input into JIRA and tracked. We then use JIRA in our weekly meetings to give updates and such.,JIRA makes collaboration very easy JIRA allows us to keep a line of sight on all of the tasks that are on going JIRA also allows for easy export of data for reporting and such,The UI In JIRA is not very intuitive, they have comingled products and navigation is difficult at times JIRA can be annoying with the number of email notifications it shoots out JIRA's security model is overly complex and can lead to issues,5,JIRA has allowed us to create reports on tasks and deliverables so this is helpful We spend too much time attempting to create the reports so this is a negative JIRA has help us meet some of our auditing requirements,4,5,,SAP Service Cloud, ServiceNowJira makes agile software development management easyWe use Jira as the product management tool for our agile web team of about 12 people that are doing a major redesign/rebuilding of our city's main website. It's used to plan and track the individual tasks, stories, and bugs assigned to each team member. It also provides helpful reports showing our sprint velocity and other useful metrics.,Jira is powerful and flexible. It can be configured and used in a number of ways and for a number of different use cases. But despite that, we've found it easy to use and we were able to use it without much training. For agile-based software development, it makes it easy to manage your backlog, plan sprints, track and manage individual issues, and get reports showing overall team/sprint metrics. All of these features are seamlessly integrated with each other. It integrates well with other developer tools like Github and Slack. For example, this makes it easy to view branches and pull requests related to a specific story or automatically notify your team of important status changes to an issue.,Sometimes there are different modes for editing the same piece of data (like an issue's description) depending on how you're viewing that issue. One mode may use a WYSIWYG editor while the other mode uses plain text with Markdown. This is slightly confusing as the user experience isn't consistent. As with most WYSIWYG editors, it can sometimes be difficult to control the formatting the way you want. I've also had issues with it inserting line breaks after hyperlinks sometimes for no apparent reason.,8,As a team switching to an agile-based methodology, it's helped us to follow our desired agile practices and has made it easy manage our processes. It's helped our project to stay on track and has been recognized as a successful pilot with our organization. Other teams within the organization have seen or heard of our success and are now looking to implement some of our same tools and practices, including Jira.,8,9,Redmine and Basecamp,Eclipse, Google Drive, DropboxManage your projects with a simple and easy to use interfaceIt is being used throughout our organization. We use it to plan, monitor and develop your projects quickly and easily. With Jira, plan your daily work by creating user stories, incidents or assigning tasks and subtasks to your team members. Integration with the main development environments such as Eclipse, Visual Studio, Netbeans, make it an effective and productive alternative.,It is very simple, basic and simple to use. It allows precise customizable estimates according to the needs of the project. You can have administrative control of the company's activities (projects, processes, procedures). It is compatible in virtually all databases. It offers Web access with support for the main browsers in the market, email notifications, as well as many applications that provide additional resources to Jira.,Although Jira is an excellent tool for project management, the cost can be somewhat expensive. Its initial configuration proved to be complicated. It can be difficult for beginners, because it is difficult to understand its characteristics.,9,Workflows can be customized and adapted to our needs. It substantially improves teamwork and communication between users. Increase productivity, as it helps to plan, specify and follow the work of my team members.,8,9,Basecamp and Zoho Projects,CylancePROTECT, Zendesk, Lexmark Managed Print ServicesJIRA worksJIRA Software is used by the website development group. It tracks our new projects, our system bugs, and system problems. We use it to communicate with our workers who are off-site. We also use JIRA with Github to number our Git branches. Using JIRA's ticket codes keeps everything in sync and reduces problems.,Project tracking Individual task tracking Integration with Github,Communication with team members is adequate but not as good as other software Not as many software integrations as I would like Can't delete tasks unless you are super user,8,Project teams are able to work more effectively. Keeps team on task,8,8,Yes,Price Product Features Product Usability Third-party Reviews,I would more fully evaluate the softwares integration with other third party applications.JIRA for an easy kickstartI have experienced JIRA in two major areas: 1 ) a tool supporting internal users or client requests (internal or external service desk/help desk). 2) a teamworking tool for the sharing of software specifications during software development.,Excellent tool for supporting internal or external users. If you want to start, you can go to the cloud/online subscription which is very cheap and you can start immediately with preconfigured processes Great tool for sharing business and IT requirements in SW development. Requires connection of JIRA and Confluence which works fine after initial configuration. Available basic reporting of performance of teams or individuals. An immediate good overview of severity (priority) of tickets, resolutions KPIs, etc.,The processes can not be thoroughly analyzed, visualized and managed. Although a basic reporting is available and reports can be customized, the process discovery in a complex environment is not supported. This can, however, be provided by an external process mining application. JIRA can export the data or provides access to its database via API.,10,This tool can save a lot of money by visualizing project progress, regardless if you develop in a waterfall or agile mode. Imagine saving just 1 day on a project with 50 programmers just by being able to recognize an issue in development. The monthly subscription fee per user was back in 2018 a peanut.,9,10The winning combination for your software development team: JIRA + AgileWe use JIRA as a project management and a bug tracking tool for most of the company projects. Whether it is software development, ASIC design or IP development, JIRA fits all flavors. For software development, we use it mainly for its agile scrum and Kanban development support. We realized that switching to Agile with JIRA was a winning combination to increase productivity, together with having more homogeneous teams and same mindset across team members.,Easy to use bug tracking features. It has a great support for Agile SCRUM and Kanban software development methodologies. Promotes collaboration within the team and across teams. It is extremely configurable and allows a system admin to address complex project management requirements.,There is a steep learning curve for JIRA administrators before the full potential of the tool can be harnessed. The licensing system is per number of users. If you buy a small license and the tool is widely adopted, you may have an issue in getting your budget approved in a low cost environment, because the price for higher tiers goes up quickly. Support can use some improvement. It happened few times that for critical issues we had to spend a lot of time exchanging emails and explaining to different people where the problem was.,10,It really improved our productivity and therefore decreased the time to market of our deliveries by 40%. It improved the collaborative work inside the team. Helped building the scrum mindset in the team. It helped replacing the various bug tracking tools used across the company to just one.,9,7,BugzillaJIRA is a great project management toolJIRA is being used in our organization to manage software development. It is used to easily manage the workload. It makes our developer's job easier as they can get all the information from the JIRA stories. JIRA is also used to check the status of the project and manage assignees.,Easily manage workload. Get all useful information and links to useful documents. Check the status of a project. Integration with Git.,There is no code refactoring plugin. We can prioritize the projects. The user interface makes it a bit complex to search for all items.,9,JIRA makes project management seamless. Developers and managers are updated with project progress. All documents are accessible easily which makes for a hassle-free process.,9,9,VersionOneJIRA - Managing a Project Activity at your Fingertips!JIRA is used by our Company to setup Epics and the associated Tasks that belong with the Epic. We then plan our Sprint (2 weeks) with Development tasks and track the progress of those tasks. If something happens that hinders the development of such task, we can easily put a block on that Task until the block can be removed (i.e. waiting on data cut from Agency). We can easily drop something into the backlog when needed.,Manages Epics (projects) very well. Tasks can be adjusted easily along with their corresponding Story Points. The Backlog can be easily managed by moving Tasks around as needed. Notifications can be automatically sent out (if setup) to the Developer when new work is assigned. Epics/Tasks/backlog items can be managed through an easy to use drag and drop process. Agile. Easy to work with (very intuitive),I don't have anything negative to say about the software. As with any software, the GUI can always use improvement, but that comes with time. It can lock up very briefly at times due to too many users.,10,We can manage 100's of projects at a time. I work on a DB Conversion Team and it can get a little hairy trying to keep everything straight. JIRA does that for us. JIRA is easy to use and there is a very little learning curve for new team members. JIRA allows for a 40,000-foot view or a 5,000-foot view. You can drill down as deep as you need to go, or take a step back and look down from the heavens.,10,10,Logitech Rally,Changepoint, Microsoft Office 365, Microsoft ProjectJIRA: A great bridge between PM and R&DOur organization uses JIRA as a project management tool between our project management office, our product management team, and our research and development team to plan, coordinate, and deliver on product releases encompassing multiple initiatives, epics, features, users, stories, and tasks. Each team is responsible for various components of a release from inception to end-of-life.,Organization of features Story development for R&D Release candidate control,Ease of searching Editing Process flow of feature development Acceptance Criteria development,8,Better organization for feature releases. Linking to issues and enhancements has increased ROI from releases. Customer satisfaction improved due to the adoption of continuous release model.,7,8,Microsoft Visual Studio Code,Microsoft Teams, Skype for Business (formerly Lync)JIRA is the most easy to use project management software out thereWe use JIRA to manage multiple high-level projects within our company. It is a corporate-wide engagement with JIRA with several businesses that use it independently with a corporate administrator to manage the tool. We use it for very large projects, like Salesforce rollouts, as well as smaller projects like minor enhancements or bug fixes across all key software environments.,It is a great tool to link documents and documentation to specific user stories to keep things organized. It has a great user management feature to help us plug resources into the right projects and remove users as they move on to other work. It has sold plug-and-play options that you can elect to use or deselect in order not to cloud the interface.,The look and feel is a bit sterile, which is both good and bad. Some nice skins to make it easily customizable to our existing corporate color schemes would be nice. Cost is always a place for improvement. JIRA is not overly expensive, but in a market where there are a ton of options, price is a negotiation point. Better integrations with vendor/partners using the same tool would help onboard offshore resources we occasionally use.,10,Better prioritization of user stories and resources. Better tracking of resources. Better documentation container to store relevant information.,9,10,Basecamp, Workzone, VersionOne, TargetProcess, Pivotal Tracker, Assembla Workspaces and SprintGround,Basecamp, Workzone, SprintGround, ActiveCollab, Assembla Workspaces, Attunity Managed File Transfer, Sopheon Accolade, Cloudera Data Science Workbench, Snowflake, Qlik Sense, Qlik Sense Cloud, QlikView, Microsoft Power BI, Informatica Cloud, Informatica Enterprise Data Integration, Salesforce CPQ (formerly SteelBrick), Salesforce Service Cloud, Salesforce Marketing Cloud Email StudioJira- Effective Tool to manage Agile TeamsIt is being used at a program level in the organisation. We use JIRA to track our Agile teams that are [composed] of Scrum and Kanban teams. We use it for tracking epics, stories, issues, tasks, subtasks, production maintenance tracking, and planning. It provides a good dashboard where higher leadership can look at how things are progressing and ultimately bringing in transparency.It eliminates the need for individual teams to send weekly or monthly status reports to leadership on progress and what they are involved with. So at team level sprints, stories, epics, sizing, capacity, scrum and Kanban boards are managed and looked at.,Requirements are managed very well there which can be captured in the form of epics. Epics, which capture the high-level ideas can be broken down into stories, tasks and sub-tasks. The team can team can raise bugs, capture comments and tag test cases, against each story ultimately bringing end-to-end traceability. Since distributed agile requires more collaboration, JIRA's seamless integration with communication tools like HipChat and Slack allows teams to work collaboratively. JIRA supports customization since each team is unique, you can create your own issue types, modify the workflows, add/remove fields. Standard issue types created in any project are: a) Bug b) Task c) Sub-Task d) Epic e) Support Ticket f) User story User Story workflow can be: a) Backlog b) Ready to Start c) Dev In-Progress d) QA In-Progress e) Ready for Demo All these can be modified based on your requirements. If you are looking for devops implementation, JIRA has support for CI & CD. It can be integrated with Git and Jenkins very well. JIRA supports two kinds of boards, Kanban and Scrum boards. It is very easy to track things using these boards & it also provides ample of charts like reporting options such as burndown charts to help teams plan & replan at every stage in the development life cycle Searching issues in JIRA is very simple through JQL (Jira Query Language). If we would like to perform a complex search JQL allows to find issues from any timeline.,The basic version of Jira do not have support for test management, capacity management & release management. So users have to buy various plugins to support these basic functionalities which can prove costly based on team size. Navigation around the UI can be difficult at times Jira is not a simple tool, it requires some training before users can start working on it so some learning curve is involved.,8,Jira brings in more team collaboration since teams were geographically distributed by seamless Integration of communication tools like HipChat and Slack which makes it very easy for tracking and responding to notifications. Sprints management was relatively simple and straightforward. Not cost effective since we needed to buy a lot of plugins for test management, release planning and agile estimation and basic version of JIRA did not support them.,,CA Agile Central (formerly Rally), ActiveCollab, HP Application Lifecycle Management, AgileCraft, VersionOne,Yes,9,No,I got stuck with release planning and I got advice on the Tempo plugin from the helpdesk. Also, they helped me with installing ad using that for release planning.JIRA - Love at First Site for Developers, a Slow Courtship for BusinessThe use of JIRA is company-wide but sporadically. JIRA is viewed as an "opt-in" tool in our organization and is mainly sought by the development groups. We have had some success pushing it out to business users in departments that would benefit from ticketing and tracking of workload. In general, development and QA are the primary users.,Differentiated workflows. It was important to us that new product development could be handled differently than IT implementation bugs, etc., and JIRA does a great job of allowing us to treat efforts appropriately without a lot of complicating customization. Card view. The layout of the work items on the board is user friendly and easily gives the team a handle on what is happening during the working period. The drag and drop functionality is constantly lauded by our teams and whenever alternate tools are reviewed, is one of the top features used for comparison. Simplified Querying. One of the biggest selling points to the business groups that have taken on JIRA is that finding items in the system doesn't depend on someone with say, SQL talents. Though there are complaints on querying more complicated information from some, overall the WYSIWYG interface for querying tickets is very helpful for business users to "self-service" information. Integration with wiki tool (Confluence). This I think is one of the biggest draws for us on the business side. We find that JIRA is sometimes too complicated for the business user and were able to build dashboards and pages that help the business users navigate to what they need to know. Being able to maintain up-to-date reporting from JIRA without having to constantly update is beyond valuable.,Reporting. JIRA has always been a little finicky on the reporting side in my opinion. The gadgets are helpful but can be confusing if you aren't shown how to use them. Time tracking continues to get worse rather than better with the removal of the one built-in timesheet we had replaced by a paid plugin with fewer options. Roles Based Permissions. JIRA is really light on this but you can work it out using validations in the workflows and permission schemes. I think this is not intuitive for most admins and they wind up with a very unrestricted instance of the tool. Sometimes setup can be a pain because of the openness. Ramp up is long. JIRA is really difficult to understand and to be properly configured if it doesn’t suit you out of the box. Once you understand all the ins and outs of the setup process you can wind up with a decent tool but it's the fact that you need someone to sit there and learn it before you can use it - not a coherent message to management when pitching Agile. Or to some "missing features". Some features that the community feels should be a part of the core product are only available via plugin. Again, the message to management when trying to purchase these is disconcerting to leaders that are used to the "big box, all in one, everything you need, one price" solutions. Business Features. Depending on your final configuration you may find tracking business features rather onerous. Based on release structure we have a non-traditional setup where our business projects exist in one space with children work in software spaces. It is the easiest solution to our technical release issues. There is only one ticket type that can have children spanning projects and it is the Epic. Pulling in children tickets is time-consuming and laborious. I discovered that I could automate update of a ticket field on children tickets to help tracking back but it's not elegant and is open to creating gaps should things change (and they often do in Cloud JIRA).,8,Positive: this tool provides a convenient and efficient workspace for our developers/QAs as well as transparency for our leaders in the Dev/QA space. Higher level tracking (at the Epic) level gives greater transparency at the business feature level but could be improved. Negative: this tool requires a lot of time to learn and maintain. Updates are not always clear in their impact so you do accept (even in a Cloud situation) that if you do not use JIRA with no modifications (I have never heard of this by the way) you will need someone to keep an eye on it. Consider it to be 25% to 50% of a headcount based on your configuration complexity.,ServiceNow and Workfront,Atlassian Confluence, ServiceNow, MS SharePoint,No,8,Yes,None spring to mind at the time of this writing but I have very positive impressions of the support team at Atlassian.,Prioritization for Stories, etc is very nimble; caveat for the issuetype "Epic" which is decidedly less so. Sprint planning WYSIWYG query tool Dashboard gadgets for Agile development tracking,Feature prioritization (at the Epic level for our shop) is very hard to use in the Backlog - we've developed a hack where we prioritize Epics in a Kanban board but it's got an element of disconnect to the Backlog planning that isn't very "agile" Portfolio tracking - you might try to arrange features according to Business Goals but you'd have to 1) purchase the Portfolio tool from Atlassian which is the same price as the JIRA software itself or 2) build and maintain insane filters Time tracking - your time tracking will again be a choice between purchasing a plugin that does half of what you want or maintaining JQL that does backflips for the same level of value,Yes, but I don't use it,8
Unspecified
JIRA Software
1466 Ratings
Score 8.1 out of 101
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener noreferrer'>trScore algorithm: Learn more.</a>TRScore

JIRA Reviews

<a href='https://www.trustradius.com/static/about-trustradius-scoring#question3' target='_blank' rel='nofollow noopener noreferrer'>Customer Verified: Read more.</a>
JIRA
1466 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener noreferrer'>trScore algorithm: Learn more.</a>
Score 8.1 out of 101

Do you work for this company?

TrustRadius Top Rated for 2019
Show Filters 
Hide Filters 
Showing 13 of 1467 JIRA ratings and reviews.
Clear all filters
Overall Rating
Reviewer's Company Size
Last Updated
By Topic
Industry
Department
Experience
Job Type
Role

Reviews (1-13 of 13)

Companies can't remove reviews or game the system. Here's why.
Elissa Bernstein profile photo
Score 9 out of 10
Vetted Review
Verified User
Review Source

Support

7
I have not had a chance to contact JIRA's customer support. It does offer extensive documentation, although it often feels too technical for me. There is also a JIRA training app that lets you take little lessons and quizzes on different areas (e.g., JIRA basics, agile). I did find it a helpful way to teach myself.
Read Elissa Bernstein's full review
Kyle Kochtan profile photo
Score 5 out of 10
Vetted Review
Verified User
Review Source

Support

5
I have not personally tried to get support from JIRA. I have seen that their user forums seems to be well updated and populated. This would allow for users to get self help from the system when you need it. Most of the time my needs are met by an in house super person.
Read Kyle Kochtan's full review
Richard Davies profile photo
Score 8 out of 10
Vetted Review
Verified User
Review Source

Support

9
I haven't had to interact with their support team, outside of maybe reading some online help or blog articles. So I can't really comment on their support team, but the fact that I haven't needed to use them says quite a lot about the quality and ease of use of this system.
Read Richard Davies's full review
Harry Miller profile photo
Score 9 out of 10
Vetted Review
Verified User
Review Source

Support

9
Jira's support provides the most appropriate answers to all the requirements and concerns that our team needed. In addition, there is enough information for the proper management of this excellent project management tool.
Read Harry Miller's full review
Cristian Bodnarasec profile photo
Score 10 out of 10
Vetted Review
Verified User
Review Source

Support

7
Atlassian's support is lake any other support of a big company, slow and demanding. Initial consultant assigned to look at your issue doesn't have too much knowledge and he/she may waste your time until it is escalated and people with more knowledge about the system will take a look at the problem and provide a fix/workaround.
Read Cristian Bodnarasec's full review
No photo available
Score 10 out of 10
Vetted Review
Verified User
Review Source

Support

10
Our JIRA support is handled internally by members of our Product Support team. It is not supported by a 3rd party. Our internal support will always sent out notifications for downtime which is usually done on the weekend unless it is required to fix a bug/issue that is affecting the entire company. Downtime is typically 3-4 hours and then once the maintenance is complete, another broadcast email is sent out informing the user community that the system is now available for use.
Read this authenticated review
No photo available
Score 8 out of 10
Vetted Review
Verified User
Review Source

Support

8
The organization is very responsive to customer inquiries and provides standard templates to initiate set up. I would suggest working closely with their team to align your business, product management, and R&D processes. Once set up, the software runs effectively without much need for support calls or on-site visits.
Read this authenticated review
No photo available
Score 10 out of 10
Vetted Review
Verified User
Review Source

Support

10

JIRA gives us easy access to experts in the fields we need who have
knowledge of JIRA. All of our vendors, as well as most of our internal hires, have
already been exposed to JIRA, making onboarding swift and clean. We support
ourselves, so we do not have a lot of interactions with JIRA as a troubleshooting
service, but they have always been there when we did need them. It’s just easy to implement option in a crowded space of project management
software.

Read this authenticated review
Sourav Singla ,Safe Agilist, CSP,  ICP-ACC, CSM, CSPO, SSM, LSSG profile photo
Score 8 out of 10
Vetted Review
Verified User
Review Source

Support

9
I used to get immediate support from the Jira helpdesk; also most of my issues are already explained in the user manual which is really helpful.
Read Sourav Singla ,Safe Agilist, CSP, ICP-ACC, CSM, CSPO, SSM, LSSG's full review
No photo available
Score 8 out of 10
Vetted Review
Verified User
Review Source

Support

8
Whenever I contact the support staff at JIRA I find the interaction to be typical to support interactions. Quite a few of the staff are very friendly and always seem to want to help. I have given them a couple tough situations that they've had to take back but all-in-all it seems like they try very hard to get to the root of the problem in a timely manner.
Read this authenticated review

About JIRA

Atlassian Jira is a task management tool for software development teams developed by Atlassian in San Francisco. Atlassian Cloud and local server options are both available. It allows the user to create, prioritize and track the progress of tasks across multiple team members. Projects are treated as and formed from, in this software, collections of issues, which can be managed individually or in bulk in a multitude of ways. Analytic features allow team member workload and time to resolve issues to be studied and reallocated as needed. Issue voting allows team members to up or down prioritize elements of a job. Tasks can be delegated and issues can be started anonymously, if need be. Customizability and functionality are extended via extensive support for plugins. Pricing is dependent upon inclusion of Atlassian Agile (for development) or Atlassian Service Desk and upon the number of users, in both cloud or local server options.

JIRA Integrations

SnapEngage, Freshservice, Stackify Retrace, Planview PPM Pro (formerly Innotas)

JIRA Competitors

Pricing

Has featureFree Trial Available?Yes
Does not have featureFree or Freemium Version Available?No
Does not have featurePremium Consulting/Integration Services Available?No
Entry-level set up fee?No

JIRA Technical Details

Operating Systems: Unspecified
Mobile Application:No