BugTracker.net vs. WEBCON BPS

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

Really well suited for processes which work with documents, seems less (but it is possible) appropriate for single/no data actions (e.g. just provide a quick update in SQL database without any process).

• 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

• Easy to develop, doesn't require high end programming crew.
• Short learning curve for end user.
• Easy to integrate with legacy technologies.

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

Incentivized

• The configuration of the user interface is sometimes not so flexible. However, it can be developed from the (fully flexible then).

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

Great support while implementing, affordable consulting and great follow up

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

Incentivized

• ROI seems really quick, as processes are delivered really fast (on the go in an agile way)