BugTracker.net vs. Runn

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

Runn is our scheduling tool. We use it to track the dozens of projects that we have running and who is assigned to them. It allows us to create schedules for each employee and contractor (consultants) so we can effectively stay within the hours we allocate to each project and stay within the project budget.

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

• Runn allows us to track projects over a period of time to see who worked on it and how many hours were spent, to keep us on track.
• Runn allows us to create schedules for our team of consultants. By viewing a person, we can see each project assigned and the weekly hours allocated.
• Runn allows us to run reports to see if we need to bill for hours that go over the weekly allocation.

Incentivized

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

Incentivized

• Runn meets our needs so I don't have any input here.

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 used Hubstaff before moving to Runn. The decision to leave Hubstaff was purely a financial one, as we were looking to cut expenses during the early phase of the pandemic. Both products are good, and Hubstaff worked well for our organization, but it was decided to move to Runn to save on organizational expenses without losing needed functionality.

Incentivized

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

Incentivized

• Runn has been a positive impact on our expenses because we use a free (or low-cost) version in our tech stack.

Incentivized