Fog Creek SoftwareFogbugz - Great for all users and a large amount of projects2017-10-18T18:05:50.502ZWe used Fogbugz to manage books that our company was converting from paper to digital versions. For us, Fogbugz was a way to track not just bugs or software improvements, but projects and assignments that the team at large was working on. I oversaw a queue of book projects for five other workers, as well as running my own queue of fogbugz tasks and subtasks.
The case and subcase flow in Fogbugz works well if you want to visualize multi-step processes and how the processes are materializing. It was also good for users to self-refer to their tasks each day.,Tasks, Subtasks, and notes. All three of these areas were critical for our team. Tasks in Fogbugz were a bit easier to see than in more bug based software like Trello or JIRA
The entire screen is used to view a task or case. Clicking on a task or case will open up and take up the entire screen, aside from the sidebar nav columns. I like to see details and I think Fogbugz does this very well, using up as much digital real estate as possible.
Flowcharting in Fogbugz with Creately is nice - instead of getting an exterior flowchart software like Lucidchart, Creately works right in Fogbugz.,Personal dashboards could be a bit more customizable - i.e. if I log in, I'd like to see some of the cases more at the bottom of the screen and notes at the top. This is a minor minor quibble.
I wish projects and cases within projects could be viewed in another format aside from list view. Perhaps a panel view or a card view would be good. That said, the list view is compact and agile.,9,Overall positive. No bugs or issues using Fogbugz, and it was easy enough for managers to learn and for workers to learn. Very low training time and therefore very low cost.
It was hard to fudge details or miss work with Fogbugz. It does not let any project slip through the cracks. This is absolutely valuable for our managers and ultimately for clients as well.
Fogbugz makes sense to laypeople and to developers. It could be considered a compressed solution that could be used by QA teams and Development teams. There would be no need to get Asana for one team and Fogbugz for another - you can use Fogbugz for both.,Asana, Trello and Basecamp,Asana, Basecamp, TrelloBecky Jewell LaughtonFogBugz2017-03-29T19:54:30.617ZUse to track bugs that were found in projects. Used to track the fixing of bugs found during testing. Used to communicate the specs of new projects and to answer questions asked by business owners and QA. Used across whole organization. Addresses teh business problems of communicating with different employees across different time zones and countries.,Good for documenting
Good for attaching things,Missing keyboard shortcuts
Missing a good way to link external documenations,3,Jira,JIRA Software, Microsoft Office 365Gillian HughesFogbugz is simple, flexible and easy to maintain. Great for SMB's, not great for large organizations.2015-02-17T23:07:57.211ZWe are currently using Fogbugz for our internal Production, Development, and Project Management teams. It is serves as a light weight task management system to move/track jobs between departments. it is effectively a virtual job jacket for our creative agency. We introduced the tool to support our teams with tracking fast moving jobs and keeping individuals accountable for responsibilities for a given job. It also helps team member transitions and coverage by showing a quick summary of the job history.
We selected the tool for it's simplicity, flexibility and ease of management because it would be used company wide accommodating varying experience levels of task management literacy.,Simplicity: Compared to other tools like Jira and even Bugzilla, Fogbugz minimizes the number of fields. The general workflow and status' of a given task works well for us. (Assigned, Resolved, and Closed).
Flexibility: The list views are highly customizable. This allows for many ways to display information and create custom lists for teams and departments. It has prebuilt queries, and basic boolean syntax that you can stitch together to build a list.
Easy to maintain: There are just two types of access rights. Regular and Admin. With some training, administration of the tool is done by project managers and a general user admin. We have a self hosted version, so there is an IT component in our maintenance, but it does not requires much attention.,The simplicity of a single admin type user is not great because anyone who can create a job or client in the system, can also add and delete users. Content and User administrative rights should be separated.
There are ways to change the terminology/lexicon within the tool, but we are not able to get it to work even after reaching out to tech support. So we are forced to use the system terminology that doesn't match up to our company making training a bit difficult.
There is a subscribe function that you can opt into, there should be a way to add subscribers as you create a new task.,9,Less downtime of jobs. It is each person's responsibility to check their list to see if they have any pending work.
When people are out sick or busy, a supervisor can easily shift work from one person to another who many have time to cover work.
Management has a quick view into seeing what is happening with a job and can use it as a tool to request addiional resources as needed.,Bugzilla,Workfront,jiraTed Shimizu

We used Fogbugz to manage books that our company was converting from paper to digital versions. For us, Fogbugz was a way to track not just bugs or software improvements, but projects and assignments that the team at large was working on. I oversaw a queue of book projects for five other workers, as well as running my own queue of fogbugz tasks and subtasks.

The case and subcase flow in Fogbugz works well if you want to visualize multi-step processes and how the processes are materializing. It was also good for users to self-refer to their tasks each day.

Tasks, Subtasks, and notes. All three of these areas were critical for our team. Tasks in Fogbugz were a bit easier to see than in more bug based software like Trello or JIRA

The entire screen is used to view a task or case. Clicking on a task or case will open up and take up the entire screen, aside from the sidebar nav columns. I like to see details and I think Fogbugz does this very well, using up as much digital real estate as possible.

Flowcharting in Fogbugz with Creately is nice - instead of getting an exterior flowchart software like Lucidchart, Creately works right in Fogbugz.

Fogbugz is great for case-and-task based businesses. If your business has hundreds of weekly anticipated tasks that exist, such as processes to get files converted, Fogbugz can manage these processes very well. For our team, we knew each week that we would have about 500 tasks or orders to get processed. Fogbugz helped us break down these projects, get them assigned evenly throughout the team, and easily see who is working on what task.

FogBugz is also good for tracking unanticipated tasks like bugs, making notes, flowcharts, and categorizing if the problem is a bug, feature request, etc. For us, it was just the best at nailing down those anticipated tasks.

Use to track bugs that were found in projects. Used to track the fixing of bugs found during testing. Used to communicate the specs of new projects and to answer questions asked by business owners and QA. Used across whole organization. Addresses teh business problems of communicating with different employees across different time zones and countries.

Fogbugz is ok. It's good for bare bones bugs and projects, but lacks the functionality of JIRA. I hate not having shortcuts. I don't like the way the cases are laid out. I don't like the search. I don't really like much about it. It's very simple and bare bones, and just not enough for me.

We are currently using Fogbugz for our internal Production, Development, and Project Management teams. It is serves as a light weight task management system to move/track jobs between departments. it is effectively a virtual job jacket for our creative agency. We introduced the tool to support our teams with tracking fast moving jobs and keeping individuals accountable for responsibilities for a given job. It also helps team member transitions and coverage by showing a quick summary of the job history. We selected the tool for it's simplicity, flexibility and ease of management because it would be used company wide accommodating varying experience levels of task management literacy.

Simplicity: Compared to other tools like Jira and even Bugzilla, Fogbugz minimizes the number of fields. The general workflow and status' of a given task works well for us. (Assigned, Resolved, and Closed).

Flexibility: The list views are highly customizable. This allows for many ways to display information and create custom lists for teams and departments. It has prebuilt queries, and basic boolean syntax that you can stitch together to build a list.

Easy to maintain: There are just two types of access rights. Regular and Admin. With some training, administration of the tool is done by project managers and a general user admin. We have a self hosted version, so there is an IT component in our maintenance, but it does not requires much attention.

The simplicity of a single admin type user is not great because anyone who can create a job or client in the system, can also add and delete users. Content and User administrative rights should be separated.

There are ways to change the terminology/lexicon within the tool, but we are not able to get it to work even after reaching out to tech support. So we are forced to use the system terminology that doesn't match up to our company making training a bit difficult.

There is a subscribe function that you can opt into, there should be a way to add subscribers as you create a new task.

Do you have trouble keeping track of work in progress? Do your jobs jump around alot and often sit idle? Are there process bottlenecks where better access to job/task transparency will help move a job along better? Are there common issues related to coverage and you find yourself digging through emails to figure out job status?