Atlassian Jira is a project management tool, featuring an interactive timeline for mapping work items, dependencies, and releases, Scrum boards for agile teams, and out-of-the-box reports and dashboards.
$9
per month per user
Nintex
Score 8.1 out of 10
N/A
Nintex offers a platform that helps companies discover, automate, and optimize business processes.
$480
Minimum 1,000 users per user
Pricing
Atlassian Jira
Nintex
Editions & Modules
Standard
$9
per month per user
Premium
$17
per month per user
Enterprise
Contact Sales
per year
Enterprise - Process Platform
$480
Minimum 1,000 users per user
Professional - Process Platform
150,000
per year
Expert - Process Platform
185,000
per year
Custom
Personalized Quote
Offerings
Pricing Offerings
Atlassian Jira
Nintex
Free Trial
Yes
Yes
Free/Freemium Version
Yes
No
Premium Consulting/Integration Services
No
Yes
Entry-level Setup Fee
No setup fee
Optional
Additional Details
Higher volume teams may qualify buyers for a discount.
We are using Nintex for SharePoint 2016 forms and workflows only for all kinds of automation. It has the following benefits over others. It is faster than working with the old SharePoint Designer and its
textual design or Visual Studio with coding. Less complex workflow can
Nintex Process Platform commercial terms are the lowest compared to other BPM tools. The other plus point is it allows the building of API or webhooks to link up with other systems. The RPA license is also included in the bundle, which is not offered by other products on the …
Nintex is still ahead of the curve on many of its competitors for a number of actions they offer. We do frequently evaluate other tools as many other offerings are rapidly closing the gap. Microsoft Flow has come a long way in the past year and I foresee them giving Nintex a …
The integration of Nintex with SharePoint was seamless and the affordable cost allowed us to deploy the service as a shared platform without the need for complex charge back models to each team. Developing in ServiceNow is significantly more complex and more expensive since it …
Nintex WorkFlows seems to be a lot more user friendly, contrast to using SharePoint Designer. I had to spend a lot of time learning SPD and even more time troubleshooting SPD WorkFlows and InfoPath Forms. Though Microsoft offers lots of information on knowledge base (kbs) and …
Jira facilitates software development, bug tracking, and sprints. It's ideal for structured workflows, issue management, and customer communication. However, more straightforward tools might be more efficient for highly creative, unstructured tasks or tiny, agile teams with quick visual overviews. Jira's complexity can be overkill for basic task lists.
Nintex works well for linear processes that have multiple players. It's helpful to capture the triggers for why a process begins and the outputs it creates. It does have a way to link subprocesses. It's not as helpful for processes that are done by a single user (SOPs seem to work better for this) or iterative processes.
Integration of tools like Bitbucket, Github, etc., has made it easier to track the code changes, pull requests, and branches linked to the respective ticket.
The detailed tracking system in JIRA has helped the teams prioritize and understand the project tasks and issues.
JIRA's project tracking board helps you keep track of the project, its flow, and expectations in a structured format.
Integrations with other services using various secure authentication methods, along with the seamless integration with SharePoint, are the icing on the cake. This makes it superior to other BPM tools available in the market.
Flexibility in application development - The diverse configurable properties offer multiple ways to utilise the controls and events, affording the flexibility to expand your scope and enabling the creation and use of processes in a myriad of ways.
The streamlined and efficient deployment process significantly accelerates release management, allowing for faster and smoother implementation of updates and new features.
The user interface of the pages offers a more refined and appealing look and feel compared to most other BPM tools.
New Responsive Form does not allow to create a custom button anywhere we want. It will be useful to allow to add the button control anywhere within the form that can trigger the click event rule.
It will be useful to allow CSS in New Responsive Form.
Found HTML Table tag does not work properly in New Responsive Form.
More functionalities related to HTML, CSS and JavaScript in New Responsive Form will be very helpful.
This is because Jira Software generates a huge profit for an affordable price. Having a tool that makes team management transparent and effective is very valuable.
In addition, the renewal of Jira Software and all Atlassian tools is predictable and clear, as the prices are published on the Atlassian website and there is no pyramid of intermediaries.
We are currently investigating which collaboration platform best suits our needs. Chances are that we move to SharePoint Online and then we're going to also consider the microsoft power platform (power automate and power apps) to develop forms and workflows. Aspecially the pricing model for the cloud is currently a blocking factor to go for the Nintex solution in the Cloud.
The interface is simple and easy to use if you have some experience with it. Configuration is also logical most of the time. However, less experienced users tend to find themselves lost in some tasks - usually complex project configuration- but sometimes simple things, such as seeing why a user can't move issues in a workflow. Jira configuration requires a good amount of experience - and even experienced users often resort to documentation. It's a tool that's easy to use if you know what you're doing and where to find the proper documentation, but novice users tend to find it challenging.
Based on the on-prem experience with this tool, I believe that they have a lot of potential to help the online version catch up to where the on-prem left off. Nintex developed their online version and it is not as fully formed or capable compared to the on-prem version, and the licensing model scales back what we would have liked to be an expansion or at least continuous improvement of existing flows. It is also not near as user friendly specifically to non-developers and has an uncanny similarity to Microsoft Flow in the online instance. Consistent with my reviews of the tool - I believe they have some good approaches to design thinking that, if translated well from on-prem to online, could make this a clear winner again.
Did not face any issues and whenever they plan maintanance they update all of us very well in advance also so in that view we are good with the product stability.
The Nintex Process Platform has never crashed or had any availability issues during my usage. However there was an issue that was of my own making that caused a slowdown of the system. I had set up a process to run once a day and check for employees on a list that had certain parameters selected, and for some reason that I had to troubleshoot, the process instead ran constantly, which filled the cache quickly. I ended up having to dismantle that process so the system didn't crash.
Performance is really good though it holds lot of data it loads quickly especially search operation also get the results very quickly as needed hence its good
Unlike any other process automation product out there. Not only is it a low-code, easy to use tool for building processes in environments like SharePoint or Salesforce, they have really started to expand their tool-set by offering tools to manage other things like process mapping, RPA, mobile,etc.
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.
The support team works as fast as they can and they are usually fast to solver the issues. Sometimes they need more time to solve one of them because our workflows and so on are more complex than usual clients.
Had received training from our own internal user so it was good and also very easy to understand topics and many tasks in the UI are self explanatory and we can do by our own
One of their strong points i stheir documentation. Almost all of the basic set up needed within JIRA is available online through atlassian and its easy to find and very precise. The more critical issues need to be addressed as well and hence the rating of 8 instead of a 9.
I used the Nintex training software, it was easy to watch and follow along. It didn't go too fast and was descriptive enough to understand what the steps needed were in order to produce efficient workflows and user friendly forms.
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.
1.Start with Simple Workflows: Begin with basic workflows to gain user confidence before tackling complex processes. 2.Involve Stakeholders Early: Engage business users and IT early to align workflows with real business needs. 3.Comprehensive Training: Invest in user training to ensure smooth adoption and reduce resistance. 4.Leverage Prebuilt Templates: Use Nintex’s templates to speed up implementation and maintain consistency. 5.Iterate and Optimize: Continuously improve workflows based on user feedback and performance metrics.
monday.com cannot be integrated with CI/CD tools, whereas Atlassian Jira integrates with CI/CD tools seamlessly. Atlassian Jira has strong Agile and Scrum support. Coming to monday.com, it has basic agile functionality. But Atlassian Jira has a complex UI, and monday.com has an intuitive, drag-and-drop interface. Overall, Atlassian Jira provides features like Agile project management, DevOps integration, and customizable workflows.
Microsoft environment does not have the scalability of Nintex; it is perfect for small and medium-sized companies, especially in environments where Microsoft environment is almost entirely used. Although Microsoft offers options to connect to other applications, its platform lacks the development and robustness that Nintex provides. Nintex not only covers Microsoft environments but also Google and other important platforms.
The scalability is really bottlenecked by the imagination of the user. I was able to make processes for my own personal usage, making my daily tasks easier. I was also able to make processes that affected hundreds of employees, making large standardization and efficiency gains. So either way, the system is used the same way, and I was the limiting factor.
Atlassian Jira's robust workflow automation has boosted team efficiency, shortening delivery cycles and driving a positive ROI through improved project management.
Its advanced reporting and integration capabilities have enabled data-driven decisions, aligning operations with key business objectives.
However, the steep learning curve can delay adoption, potentially hindering short-term ROI.
People have woken up to the amount of overlap after mapping their processes.
People can be resistant to process changes. You need to have the support from above or support from the 'business' that you are process changing to be able to see the positive impacts.
Numbers talk. if you can get a general salary figure from your HR dept to show savings for 'employee bands', then when you present reports, they will be all the richer in data.
