BugTracker.net vs. CoreIntegrator Workflow

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

I have found CoreIntegrator to work well for our needs as an Accounts Payable workflow solution. The system was implemented with very little internal technical assistance. It can be administered by a business user without a great deal of technical knowledge because the CI support staff is knowledgeable and helpful.

• 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

• Integration to Great Plains
• Simple to use

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

Incentivized

• The system administration is somewhat difficult for someone that is not highly technical.
• Deleted or removed items appear in search results.

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

Sometimes we receive slow responses.

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

Incentivized

We didn't review another product because CoreIntegrator so perfectly met our needs.

Incentivized

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

Incentivized

• Time saving outweighs the cost.
• Ease of use is so much better than most software solutions.

Incentivized