Adobe Workfront, acquired by Adobe in late 2020, is a web-based project-management tool. It is designed for both IT and marketing teams, but can be implemented for any kind of project. Workfront offers all the features standard to project management platforms, as well as resource allocation, automation, and agile workflow.
N/A
Atlassian Jira
Score 8.4 out of 10
N/A
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
Azure DevOps
Score 8.1 out of 10
N/A
Azure DevOps (formerly VSTS, Microsoft Visual Studio Team System) is an agile development product that is an extension of the Microsoft Visual Studio architecture. Azure DevOps includes software development, collaboration, and reporting capabilities.
$2
per GB (first 2GB free)
Pricing
Adobe Workfront
Atlassian Jira
Azure DevOps
Editions & Modules
No answers on this topic
Standard
$9
per month per user
Premium
$17
per month per user
Enterprise
Contact Sales
per year
Azure Artifacts
$2
per GB (first 2GB free)
Basic Plan
$6
per user per month (first 5 users free)
Azure Pipelines - Self-Hosted
$15
per extra parallel job (1 free parallel job with unlimited minutes)
Azure Pipelines - Microsoft Hosted
$40
per parallel job (1,800 minutes free with 1 free parallel job)
Basic + Test Plan
$52
per user per month
Offerings
Pricing Offerings
Adobe Workfront
Atlassian Jira
Azure DevOps
Free Trial
No
Yes
No
Free/Freemium Version
No
Yes
No
Premium Consulting/Integration Services
Yes
No
No
Entry-level Setup Fee
Optional
No setup fee
No setup fee
Additional Details
—
Higher volume teams may qualify buyers for a discount.
I like both Jira and Asana. They both help streamline campaign processes and provide visibility into the work being completed by multiple departments. However, with Workfront, it syncs with other Adobe products, giving it an edge over other products.
JIRA is better for the day to day type work that is done by individuals or teams, Adobe Workfront excels at the high level day to day work that is done by an entire organization.
While I consider Jira to have a somewhat different targeted use case from Adobe Workfront, they definitely overlap in some of their capabilities. As mentioned earlier, I find that Adobe Workfront is better at tracking progress and managing resources for larger projects that …
It gave better structure for marketing/creative operations where intake, approvals and governance actually matter. Compared to Asana/Monday/Trello, it felt heavier but it handled standardised workflows, audit trails and stakeholder drived demand reliably.
We needed a single …
Workamajig is great specifically for marketing project management. Jira is great specifically for software development project management. However, if you want all of the company on the same PM software, you need something less purpose-built. Asana is good for both, but lacks …
Workfront is more comprehensive. The thing that sets Workfront apart is that using their api, we can write custom integrations over Workfront and design our own dashboards using that integration. This allows us to not only use tools provided by Workfront, but write our own very …
Verified User
Analyst
Chose Adobe Workfront
To manage the organization's work from project to project, the organization uses multiple project management solutions. In comparison to Jira, however, the only useful feature I found is the Gantt chart, which helps give a clear overview for multiple projects at once. Moreover, …
Jira is mostly used as a bug locking tool or to track any new development for any specific region/EPIC. But Workfront has a lot of other features which are beneficial in project management. I still consider Jira and Workfront my top two options for project management and …
Workfront destroys Trello in my opinion for large, multifaceted projects, however, is not compatible with the more intimate projects that perhaps involve 2-5 people. The free Trello option, though limited, is better suited for this.
I am a consumer of Workfront for a couple of years now and am a major defender of this venture and the board apparatus for a few reasons. 1) I think that it's exceptionally natural for clients to utilize. 2) It is effectively tweaked dependent on the requirements of your …
Compared to JIRA, Workfront is a lot more user-friendly and less focused on IT/technical tasks. If you're looking for a resource tool that is for creative departments, I highly recommend Workfont.
JIRA and Clarizen were too complicated and did not offer an integrated document review and proofing system. Microsoft Project did not handle multiple small projects and resource allocation as well. Smartsheet was too limited for large teams and required too much manual work.
I've used Jira and Jira seems to cater better to the developers. It doesn't seem to cater as well to the PMO side of things. If we could combine the PMO friendly Workfront with the dev friendly Jira, that would be a win-win. Besides Jira, I haven't used any other systems that …
JIRA has a bit more of a GUI interface which is more conducive for the agile methodology. It provides much more information in a lateral space which is easier for the user to consume. We are actually in the process of moving away from Work Front and using JIRA solely.
From my point of view, the biggest difference between Jira Software and Azure DevOps Services is that Jira is way easier to use, Azure DevOps is not that friendly user, you need to do a lot of research to modify Azure boards or to move things around. Making changes in Jira is …
Compared to GitLab, Jira offers a lot more features and details. The GitLab feature is nice for small projects or teams but we are multiple teams with multiple topics and projects even inside one team - so Jira is more applicable for our case. Azure DevOps offers a comparable …
Atlassian Jira provides the greatest access to integrated tools, the most common/familiar interface and toolset for most development teams, and is competitively priced when compared to the level of customization required to outfit similar tools we've used.
Jira was the application choose by the company that work for, was already part of the culture, it perform well for organizing and managing the software projects and the company, ClickUp its easier to configure projects and automations and Azure Dev Ops and Trello is simpler but …
Jira is easy to use for less technical work professionals, while Azure and GitHub [take] more time to learn how to use effectively. For large firms with multiple business and technology teams collaborating, Jira Software is a great tool for first time Agile users and …
Although Slack is used a bit differently, we use Slack when it comes to quick fixes and issues that don't need to go through the Jira process. Jira is best used for larger-scale issues and projects where we need to keep track in a neater way and do more than just communicate …
TFS has a feature to put requirements on estimates, but it's really not visual (not for account managers or PMs). It's not easy to use whereas Jira in very easy to use.
We remain with JIRA even though our umbrella company is fully invested with ServiceNow(SNOW) as SNOW has just a portion of the utility of JIRA when it comes to agile development. SNOW also requires advanced technicians and an entire support team to maintain, whereas JIRA's …
ADO has better linking than Confluence and is adaptable for a specific need, whereas Confluence might be a bit more rigid, but it's also sort of along the same lines as to what can be done with both tools. ADO also had an ease of use to it and can do a bunch of stuff with it, …
We love the multi-tier hierarchy in Azure DevOps for tasks, with epics, features, stories, bugs and tasks all available in a nice nested hierarchy. It's not as pretty as monday.com and doesn't work as well OOTB as ServiceNow SPM however.
Jira is fantastic for project management and customer facing portal. It is not good for pure development (no integration with Git, pipeline management, automated testing features). If DevOps were to integrate and adopt the project features of Jira as well as the customer facing …
Jira is super clunky and doesn't behave in a modern fashion. monday.com is too flexible and doesn't provide enough feature set. AWS is the most competitive, but it's hard to wrap your brain around all of the features and offerings provided by amazon. ADO does a better job of …
Trello is simple to use, but it's only for a Kanban board. Jira might be the same, but I don't really have enough experience with Jira to fully compare them. When I used it, it missed certain functionalities that I was used to in Azure DevOps. Visually it's a lot different too.
Azure DevOps Services have huge functionality and are well supported by Microsoft as well. You will get plenty of features in the marketplace and learning documentation.
Verified User
Employee
Chose Azure DevOps
Azure DevOps is widely used because of its collaboration and integration with various other tools. Here the assign of the sub task is quite easy compare to Jira. Also Azure Devops can we integrate easily with Git for better code representation and versioning. It reporting is …
Azure DevOps is a completed product and ecosystem. It offers a robust ecosystem that does everything that is needed. The above products do lack features like pipelines tasks, third-party integrations. Besides all cloud benefits, the main advantage of Azure DevOps Services …
Currently, we use both products, however, we use more the Atlassian suite. We have started recently using Azure DevOps for specific implementations and projects. We don't have any plan yet to migrate all our projects to Azure DevOps, we may in the next couple of years. …
One of the foremost reasons that acted in favor of Azure DevOps was its all-in-one packed web portal which enabled easy access to all the CI/CD tools and kits. Customizable screens, notifications via Teams/mails, project views, etc. Most other tools/products offer only part of …
They are really close. Azure DevOps is better because of the deep integration with Microsoft technologies. JIRA is better on the customization side. However, Azure DevOps is really improving on that front. They are releasing new features every other week now. Azure DevOps also …
Being primarily Microsoft Developers and how VSTS integrates with Visual Studio it stood head and shoulders above other options for us at the time of making our initial decision.
Our TFS was dated and in some ways was quite crude. VSTS is thoroughly modern and I don't have to worry about updating it since MS is always updating VSTS. Also, VSTS has better integration with other products such as JIRA than our older TFS would. I am sure you could integrate …
With more functionality added, JIRA has become slow, whereas VSTS is a pleasure to use. Trac and JIRA do not show the entire health status of the pipeline like VSTS. Hygieia is open source and trying to achieve what VSTS does but it is not as mature yet.
VSTS is the best integrated tracking and deployment software for a pure Microsoft shop. It has some weaknesses, the builds aren't as easy to configure as TeamCity and the security setup is needlessly convoluted, but it is a solid offering.
It works super well for creative brief intake and brand reviews. It took us more time than I'm willing to admit to get it all set up, but for our limited use case, it's working very well now. I'm not sure where it wouldn't be a good fit, honestly. As a newer user, it's still something I'm getting to know and learn.
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.
Azure DevOps works well when you’ve got larger delivery efforts with multiple teams and a lot of moving parts, and you need one place to plan work, track it properly, and see how everything links together. It’s especially useful when delivery and development are closely tied and you want backlog items, code and releases connected rather than spread across tools. Where it’s less of a fit is for small teams or simple pieces of work, as it can feel like more setup and process than you really need, and non-technical users often struggle with the interface. It also isn’t great if you want instant, easy programme-level views or a very visual planning experience without putting time into configuration.
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.
Allow nonusers to add requests, our organization has no need to add all 10,000+ team members to Adobe Workfront, but would like them to be able to send requests to our team
I did mention it has good visibility in terms of linking, but sometimes items do get lost, so if there was a better way to manage that, that would be great.
The wiki is not the prettiest thing to look at, so it could have refinements there.
Workfront is sometimes a bit clunky to use, but overall it works well for our teams when it comes to project management and collaboration across multiple, involved teams. It also has flexibility that allows us to adapt it to diverse use cases, some of which aren't necessarily always the first things that one would think of using workfront for.
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.
I don't think our organization will stray from using VSTS/TFS as we are now looking to upgrade to the 2012 version. Since our business is software development and we want to meet the requirements of CMMI to deliver consistent and high quality software, this SDLC management tool is here to stay. In addition, our company uses a lot of Microsoft products, such as Office 365, Asp.net, etc, and since VSTS/TFS has proved itself invaluable to our own processes and is within the Microsoft family of products, we will continue to use VSTS/TFS for a long, long time.
Workfront is overly complex, but it is functional as a tool to keep track of projects. It is a shame that sometimes it takes a lot of clicks to find anything. Workfront is slowly modernizing its interface but at the same time, hides certain information away thus making the experience feels worse.
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.
It's a great help to get more information about new feature release and stay updated on what the dev team is working on. I like how easy it is to just login and read through the work items. Each work item has basic details: Title, Description, Assigned to, State, Area (what it belongs to), and iteration (when it’s worked on). See image above.They move through different states (New → Discovery → Ready for Prod → etc.).
Maintenance is required, but usually after work hours, Some days the proofing tool function is not operational, but this is a new function of the tool that WF is working out. the kinks on. Chrome is the best browser to use the system in and we find Firefox and Explorer lose some view functionality - Gantt Chart, Resource Grid
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.
I think overall, Adobe Workfront performs well. There have been some times when it doesn't load or run as quickly as our team would like. This is frustrating when it is such a crucial tool that our team utilizes on a daily basis. It can show our workflow when it lags.
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 know that this particular company has it's own Adobe Workfront employee that builds out things they need from the software, and meets with them regularly to troubleshoot. I'm not part of this process, but it's refreshing to see Adobe provide this level of customer service to people, and they're expedient.
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.
When we've had issues, both Microsoft support and the user community have been very responsive. DevOps has an active developer community and frankly, you can find most of your questions already asked and answered there. Microsoft also does a better job than most software vendors I've worked with creating detailed and frequently updated documentation.
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
The training is very easy to use and you can simply choose the topics included in the course(s) that are most important to your training needs. After each training course, you are tested on what you have learned. If you need a refresher course, they provide Course Catalogs as well as instructor-led courses & workshops.
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.
Most people learn as you go, a lot of this stuff requires trial and error throughout so my suggestion is to provide as much information in the upfront and keep it as simple as possible. You can add other tools and features as you go but everyone should have the basics down so no bad habits can start to develop. Be persistent with everyone, and don't be afraid to correct and talk through steps again so everyone is on the same page
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.
Adobe Workfront blows the other systems out of the water. It just delivers more - out of the gate, and at every quarterly update. Innovation is top of mind, and meeting customers' needs is key. We have been extremely satisfied with Workfront and look forward to all the new features on the horizon, especially AI.
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 Planner is used by project managers and IT service managers across our organization for task tracking and running their team meetings. Azure DevOps works better than Planner for software development teams but might possibly be too complex for non-software teams or more business-focused projects. We also use ServiceNow for IT service management and this tool provides better analysis and tracking of IT incidents, as Azure DevOps is more suited to development and project work for dev teams.
As I stated earlier, I didn't have to pay for Workfront myself- I'm a user under a large organization. I know it's not cheap to implement, I don't know how the price scales for a small-business, but I do like the product enough that I'm going to look into it in the future for my own company.
Our organization has thousands of users that use Workfront and it seems to hold up very well. I have not encountered any issues using it and I think it makes it very easy for multiple people to be involved in a project and keep things organized and clear for everyone involved.
Resource Management - Year over year, we were able to validate time and money saved by the implementation of Workfront by more than 2%, saving in non-working dollars and 9% savings in working media dollars.
Organization Restructuring and Automation- We also restructured our teams and implemented automation based on our analysis of how and what we spend our time on and the ROI for our respective business units.
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.
We have saved a ton of time not calculating metrics by hand.
We no longer spend time writing out cards during planning, it goes straight to the board.
We no longer track separate documents to track overall department goals. We were able to create customized icons at the department level that lets us track each team's progress against our dept goals.