Sifter Reviews

Its simplicity—which makes it efficient!

In-line styling of tickets could be WYSIWYG.

Suffer makes big trwcking easy. It doesn't get in the way of what you've set out to do!

When reviewing websites or apps that we've built, Sifter allows us to quickly and almost effortlessly post tickets, assign a priority level, and assign the ticket to someone. Sifter's functions are just what we need—and no more—so an overwhelming task of doing QA for a digital product becomes less overwhelming and instead organized and efficient.

1. Very Lightweight

2. Browser based tool - so works in any device

3. Works for any team size

4. Filters

5. Board view/list view

6. Flexibility in tags specific to project

7. Email notifications - flexibility in the notifcation settings

8. Reply from Email

9. @Mentions

1. Limited space to capture the screenshots/videos

2. Text formatting is not straightforward from the editor

3. Cannopt select multiple tags for issue if we want to categorize it more clearly

1. During testing, the communication between the testers team and the Developers team is to be kept track

2. In Sifter we can keep track of the issue in the comments

3. also, the developers can keep track of the communication among themselves while reporting to senior

4. I was able to keep track of the communication on each Unique ID generated by sifter while creating an issue in sifter via Email

5. Since everything comes to Email, it was easy to manage the emails and get a notification in MS Teams with the sifter ID link

6. Due to these notifications, I never miss anytime any developer or tester makes comments or update the issue status or he priority

Great for collaboration & tracking bugs, especially if your teams are working remotely.

The email notifications are a little much, but I could say that about almost any app (i.e. Basecamp, Slack, etc).

Tracking bugs & performance issues on our team's websites.

Makes it easy for our to communicate errors, testing, redesigns, and other joint projects.

Can't link external audiences to tickets

Plan the numbers and types of projects you think you may need. Consider how many users you really need. Your internal business could probably do with 1 or 2 ticket handlers to free accounts for bug fixers.

Website redesign was managed through sifter, which supported various subprojects.

I like that it is very easy to report issues, bugs, etc.

There are not enough priorities.

There is no way to prioritize a backlog.... I would like to rank the tasks in a backlog

There is no way to prioritize backlogs against each other. I would like to create sprints of work with tasks from various backlogs

Be careful about setting up too many backlogs as it just adds to the multiple work streams.

Don't create too many categories within backlogs.

Report and resolve bugs and other development task as part of the maintenance for multiple websites.