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
Figma
Score 9.0 out of 10
N/A
Figma, headquartered in San Francisco, offers their collaborative design and prototyping application to support digital product and UI development.
$15
per month per editor
Pricing
Atlassian Jira
Figma
Editions & Modules
Standard
$9
per month per user
Premium
$17
per month per user
Enterprise
Contact Sales
per year
Professional
$144
per year
Organization
$540
per year
Starter
Free
Offerings
Pricing Offerings
Atlassian Jira
Figma
Free Trial
Yes
No
Free/Freemium Version
Yes
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
Higher volume teams may qualify buyers for a discount.
Trello is amazing for simple project management and great for non-technical teams, but it lacks the depth and complexity of JIRA for detailed issue tracking and complex workflows. Asana, similar to Trello, is great for simple and lightweight project management but isn't …
Jira was selected because it is used by all of our clients and has become the accepted standard in the type of work that we do. The other tools are great in their own right and would better suit a more insular way of working, where a business conducts all work internally, but …
Figma was a huge turning point compared to its competitors, especially Adobe XD, a tool designed for the same purpose as Figma. I would say that it and all the other tools I mentioned, including those that do not have the same focus on UX design (Photoshop and Illustrator), …
Compared to Adobe XD, the Figma tool is much easier to use, offers more features, and has a much lower cost. Its features are less complex, making it very easy to teach beginners how to use it. The navigable prototype is also easier and more efficient to share in Figma compared …
Figma easily wins against Adobe XD. Asset sharing on XD was a pain. Figma makes it really easy by allowing you to export any layer as an asset. XD had no comments making it incredibly hard to communicate with the designer in remote settings. XD's prototyping system was not good …
Figma has more features than Zeplin or Axure. Unlike Zeplin it allows to create and share dynamic prototypes. Unlike Axure it gives tools to create detailed designs.
While different, Bubble also allowed for a very quick idea to code. We started using Figma for design and Bubble for prototype, but very quickly stopped doing dual design and just did it in Bubble. It's not sustainable long term and we'll likely have to revert to Figma, but …
Honestly, Figma is so much better than its competitors, if you even want to call them that. You get accurate, high-fidelity work that you can quickly get into development for launch. The Figma community of plugins and templates is also AMAZING! There are so many passionate …
I will be specific here - With Adobe XD it was very difficult to prototype, it was also very complicated to learn. With Sketch - We had to use InVision for prototype and share and there were limited feature were available compared to Figma.
Figma has an overall better user experience, an advanced organization tool, better commentary system. And regarding prototyping, Miro doesn't stand a chance.
I've been using Figma for the past 4 years so I'm not on top of the most recent versions of the other tools but we chose Figma as it allowed our distributed team of designers who are not just in different cities but different regions and timezones to collaborate better and stay …
ChatGPTFigma surpasses Miro by offering a comprehensive design experience, allowing not only collaborative brainstorming but also the creation of realistic wireframes and prototypes. Its design-centric approach enhances visual representation, making Figma a versatile tool that …
Adobe XD really feels like a tool stuck in the past when compared to Figma. Online collaboration, autolayout, reponsive options, it's hard to argue for XD.
Figma blows their competition out of the water. Clearly #1 for me.
Sketch was too slow to get to the cloud even thought they were doing some really awesome things. They also didn't figure out collaboration, version control, and PC/Mac …
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.
I would recommend if you need to start from scratch a product UI or any customer journey that you need to implement that requires designing and visualizing different steps to complete a process. I would recommend that any design/UI/UX team brainstorm and make proposals that they can compare and discuss in a visual way.
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.
Figma allows us to create universal content. This means that if multiple designers want to re-use a piece of content, and if everyone's content should be dynamically updated from time to time, we can easily accomplish this by turning design elements into a universal instance. Then, if an update is needed, we can push the change out to all assets at once. It's very efficient and ensures we're all updating content accordingly.
Figma also allows us to set parameters for the company's brand guide and share them across various designers. This way, we can easily pull from approved brand fonts, colors, and more, which allows our assets to remain unified across multiple touchpoints.
Figma also allowed us to create and install our own plugin, which we use to export every slide we have in a frame at one time, versus the default export feature, which limits you to one slice at a time. This is particularly useful for us when we're working on email templates, since we tend to have a ton of slices in any given series.
It will be great if Figma will consider having the Pages where interactions can be stitched together among the Pages and not just one page with so many Frames to create the stand-alone clickable prototype that can be used to simulate the intended UX
Bring back the Inspect Mode tab right on the right-side panel of the main workspace instead of hiding behind the Dev Mode.
Figma Slides feature could be improved quite a bit more in order to be easier to assemble slides into a presentation deck and having pre-built templates for slides can be useful too.
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.
Figma is a pretty cool tool in many areas. My team almost uses it on daily basis, such as, brainstorming on product/design topics, discussing prototypes created by designers. We even use it for retrospectives, which is super convenient and naturally keeps records of what the team discusses every month. Furthermore, I do see the potential of the product - currently we mainly use it for design topics, but it seems it is also a good fit for tech diagrams, which we probably will explore further in the future.
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.
There's a bit of a learning curve, but generally I think it's both more powerful and intuitive that other UX design tools. Most of what I need to do as a designer can be done in this platform, from basic wireframes to creating a design system, to creating pixel perfect designs, to prototyping to dev handoff.
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.
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
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.
I haven't used their support lately but in the past, they had a chat that I used often. They often responded in a few hours and were able to give a satisfactory solution. I would imagine it's less personal now but the community has expanded drastically so there are more resources out there to self serve with a bit of Google magic.
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
In-person training has its own benefits - 1. It helps in resolving queries then and there during the training. 2. I find classroom or in-person training more interactive. 3. Classroom or in-person training could be more practical in nature where participants can have an hands on experience with tools and clarify their doubts with the trainer.
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.
Online training has its own merits and demerits - 1. Sometimes we may face issues with connectivity or the training content 2. The way training is being delivered becomes very important because not everyone is comfortable taking online training and learning by themselves. 3. With the advancement of technology online training has become popular but there is a segment of people who still prefer class-room training over online one.
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.
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.
Miro is more user-friendly than Figma, but is less robust in terms of web prototyping and graphic design. While Figma isn't made to be used as a design tool, our team has taken to using it as such because it's richer in functions and personalizations compared to Miro and Figma.
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.
