BugTracker.net vs. Lytho Digital Asset Management

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?

Incentivized

Our creative and marketing department consists of several team members with various roles in the organization and process. We receive creative requests from the program managers and other marketing specialists daily. Lytho helps us keep track of all of these projects while listing due dates, proofing dates, completion dates and has the ability for multiple reviewers to be added to the proofing routes. We're able to customize each proofing route to best suit each client. We also have the ability to add outside clients to the proofing routes, which makes the process much smoother. At times I'd say it is less appropriate for very small requests or projects that did not need to go through a full-blown proofing route.

Incentivized

• Ability to split our multiple projects and assign a user base.
• Ability to set permissions based on user base/ roles.
• Customization of fields on a project level.

Incentivized

• project management
• project review process
• project tasks assigned to each project

Incentivized

• User interface for client-facing feedback
• Content and design updates tracking

Incentivized

• simplify the project dashboard
• simply the dashboard to view outstanding reviews
• additional training for our sales reps how to use the review process

Incentivized

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.

Incentivized

I didn't choose the product or evaluate other options, but I've been satisified with it except for tracking content changes.

Incentivized

We currently use Canto for our final art file storage as well as a web dam for our art files, client files, client portals, etc. Canto and Lytho work seamlessly together in my personal opinion. So, the two should not be stacked against each other but moreso working in tandem. Canto does not have the ability to assign projects and/or proofing abilities.

Incentivized

• Decreased turn around time for defect fixes.
• Smoother builder deploys
• Clearer communication from QA to Dev Team

Incentivized

• 100% improved accuracy in our final art files
• 100% improved client satisfaction
• 100% improved project management and tracking

Incentivized