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
Pricing
Adobe Workfront
Atlassian Jira
Editions & Modules
No answers on this topic
Standard
$9
per month per user
Premium
$17
per month per user
Enterprise
Contact Sales
per year
Offerings
Pricing Offerings
Adobe Workfront
Atlassian Jira
Free Trial
No
Yes
Free/Freemium Version
No
Yes
Premium Consulting/Integration Services
Yes
No
Entry-level Setup Fee
Optional
No setup fee
Additional Details
—
Higher volume teams may qualify buyers for a discount.
Much increased functionality and templating aspects. While I liked JIRA's setup, the Workfront is so much more flexible. The moving away from Jira i was able to show the possibilities of what a full pm software could accommodate and how it all connected in. Also, the pluses of …
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 …
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.
I was not part of the selection process, but I am fairly sure that it was chosen because there is no cost for user accounts for our customers. That is nice, price-wise, but not a great criterion for picking a customer service application.
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 …
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 …
Since I work remotely from my laptop, when I am finished with work, I enter my hours and submit my time at the end of the week. It's quick, it's easy, and it helps me keep a record of how many hours of vacation and sick time I have used. But when I am on the go, it is a hassle to record my time on my phone because of the lack of responsive design.
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.
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.
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.
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.
I have found that Adobe Workfront is a reliable resource, because in the post 6 years of using it, rarely has it been unavailable to our team. I think I could count on one hand the number of times the site has been down over my time using it with my team.
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.
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.
Much increased functionality and templating aspects. While I liked JIRA's setup, the Workfront is so much more flexible. The moving away from Jira i was able to show the possibilities of what a full pm software could accommodate and how it all connected in. Also, the pluses of connectivity with the Adobe suite for our creative teams were excellent. From providing updates within other programs, it allowed a much more fluid working process and instant communication.
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.
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.
Increased efficiency in threaded updates to Outlook emails - no time wasted looking for things in email vs Workfront - they automatically are in both places.
Time tracking allows us to average out how much time tasks & deliverable types take, allowing better long-term forecasting.
Planning has given us a system of record for campaigns, allowing us to easily find historic plans and/or view calendar views of upcoming ones.
For our marketing team, Jira Work Management caused us to lose valuable work time due to manual updates that could have been automated.
Due to lack of creative review tools within Jira Work Management, our team had to pursue other tools that do not integrate with Jira Work Management, thus creating additional OpEx.
