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
BugTracker.net
Score 7.5 out of 10
N/A
N/A
N/A
Microsoft Visual Studio Code
Score 9.3 out of 10
N/A
Microsoft offers Visual Studio Code, an open source text editor that supports code editing, debugging, IntelliSense syntax highlighting, and other features.
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 …
Having requests for immediate work being routed directly to the team members who perform the function. Proofreading needs to happen fast and turnaround quickly while retaining visibility everywhere. Through reporting and statuses, we can show progress at every stage. A large campaign organization means multiple requests and documents going between departments. By using requests alongside related rejects, we have everything in one place.
See above. Recommended questions: What type of feedback or tracking will we be doing? Will this need to be client-facing? How will we track content edits? How many users will be assigned to issues in a given project?
As a general workhorse IDE, Microsoft Visual Studio Codee is unmatched. Building on the early success of applications such as Atom, it has long been the standard for electron based IDEs. It can be outshone using IDEs that are dedicated to particular platforms, such as Microsoft Visual Studio Code for .net and the Jetbrains IDEs for Java, Python and others. For remote collaborative development, something like Zed is ahead of VSCode live share, which can be quite flakey.
The customization of key combinations should be more accessible and easier to change
The auxiliary panels could be minimized or as floating tabs which are displayed when you click on them
A monitoring panel of resources used by Microsoft Visual Studio Code or plugins and extensions would help a lot to be able to detect any malfunction of these
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.
I would plan on renewing and staying with BugTracker.net simply because it is a no nonsense easy to use tool. Once you get it set up and understand the small nuances with this custom piece of software, it really is a great tool to help your organization get started with Defect Management and BugTracking without having to drop several thousands of dollars on tools that are more fluff than function.
Solid tool that provides everything you need to develop most types of applications. The only reason not a 10 is that if you are doing large distributed teams on Enterprise level, Professional does provide more tools to support that and would be worth the cost.
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.
Microsoft Visual Studio Code earns a 10 for its exceptional balance of power and simplicity. Its intuitive interface, robust extension ecosystem, and integrated terminal streamline development. With seamless Git integration and highly customizable settings, it adapts perfectly to any workflow, making complex coding tasks feel effortless for beginners and experts alike.
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.
Overall, Microsoft Visual Studio Code is pretty reliable. Every so often, though, the app will experience an unexplained crash. Since it is a stand-alone app, connectivity or service issues don't occur in my experience. Restarting the app seems to always get around the problem, but I do make sure to save and backup current work.
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.
Microsoft Visual Studio Code is pretty snappy in performance terms. It launches quickly, and tasks are performed quickly. I don't have a lot of integrations other than CoPilot, but I suspect that if the integration partner is provisioned appropriately that any performance impact would be pretty minimal. It doesn't have a lot of bells and whistles (unless you start adding plugins left and right).
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.
Active development means filing a bug on the GitHub repo typically gets you a response within 4 days. There are plugins for almost everything you need, whether it be linting, Vim emulation, even language servers (which I use to code in Scala). There is well-maintained official documentation. The only thing missing is forums. The closest thing is GitHub issues, which typically has the answers but is hard to sift through -- there are currently 78k issues.
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.
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
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.
Visual Studio Code stacks up nicely against Visual Studio because of the price and because it can be installed without admin rights. We don't exclusively use Visual Studio Code, but rather use Visual Studio and Visual Studio code depending on the project and which version of source control the given project is wired up to.
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.
It is easily deployed with our Jamf Pro instance. There is actually very little setup involved in getting the app deployed, and it is fairly well self-contained and does not deploy a large amount of associated files. However, it is not particularly conducive to large project, multi-developer/department projects that involve some form of central integration.
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.
