BugTracker.NET Documentation

sponsors

Axosoft OnTime 2008
A bug tracker, project wiki, requirements manager, and help desk solution that manages the development process so developers can focus on coding. Windows, Web, and VS.NET interfaces. Free single-user licences and 30-day Team Trials

Gemini Project Issue Management - Free 5 User License
Gemini is a leading .NET issue management platform used worldwide. Web, Windows, VSS and Outlook integration. Free download or host with us! Special licensing for qualifying OSS projects and non-profits. http://www.countersoft.com

JIRA 3.12.3 - Free Evaluation License
Brilliantly Simple, Incredibly Powerful bug and issue tracking software used by more than 8,700 organizations in over 97 countries.
Get your free evaluation copy now.

After you log in, the first page you see is bugs.aspx, which shows a list of bugs. The dropdown at the top of the page gives you a choice of which "query" is used to fetch the list of bugs. The query controls which rows and columns are visible.

You can define a workflow by having your statuses (or other data) and queries to work together. For example, you can create a status "ready for QA testing" and then create a query "Bugs Ready for Testing" that shows ONLY bugs in the "ready for QA testing" status. You can then set the default query of your QA tester to "Bugs Ready for Testing". Since you can define any status and any query you want, you have complete control.

1. Beginner: Using the search page. Enter your search criteria and then click the "save sql as query" button.

2. Advanced: Edit the SQL by hand via the queries page. This option gives you complete control. By editing the list of columns after the "SELECT" keyword, you control which columns are visible in the bug list. By editing the "where" clause, you control which rows are visible.

You can use a BugTracker.NET macro your SQL, "$ME", which is the userid of the current user. Using the $ME variable would allow you to write queries like, "Only Bugs Assigned to Me", or "Only Bugs Reported by Me".

BugTracker.NET is able to display issues with different statuses or priorities using different fonts and/or colors. For example, you can configure BugTracker.NET to display high priority bugs with a bold red font and a yellow background. What makes this possible is that your SQL must be structured in a particular way. The first column must be either a color starting with "#" or a CSS style class. If it does not start with "#" it will be interpreted as a CSS style class. View example on how to use priority and/or status to determine the CSS style.

"$FLAG" is another macro. It creates the column of blank/red/green squares that a user can click to flag a bug for himself.

If you add custom fields, they fields automatically appear in the search results page, which uses a built in query, but not on the bugs page, which you control. So, you probably want to add custom columns to your queries too.

BugTracker.NET Home Documentation Home Is BugTracker.NET helping you? Donate!	sponsors Axosoft OnTime 2008 A bug tracker, project wiki, requirements manager, and help desk solution that manages the development process so developers can focus on coding. Windows, Web, and VS.NET interfaces. Free single-user licences and 30-day Team Trials Gemini Project Issue Management - Free 5 User License Gemini is a leading .NET issue management platform used worldwide. Web, Windows, VSS and Outlook integration. Free download or host with us! Special licensing for qualifying OSS projects and non-profits. http://www.countersoft.com JIRA 3.12.3 - Free Evaluation License Brilliantly Simple, Incredibly Powerful bug and issue tracking software used by more than 8,700 organizations in over 97 countries. Get your free evaluation copy now. Bug queries [back to contents] After you log in, the first page you see is bugs.aspx, which shows a list of bugs. The dropdown at the top of the page gives you a choice of which "query" is used to fetch the list of bugs. The query controls which rows and columns are visible. You can define a workflow by having your statuses (or other data) and queries to work together. For example, you can create a status "ready for QA testing" and then create a query "Bugs Ready for Testing" that shows ONLY bugs in the "ready for QA testing" status. You can then set the default query of your QA tester to "Bugs Ready for Testing". Since you can define any status and any query you want, you have complete control. There are two ways to create queries: 1. Beginner: Using the search page. Enter your search criteria and then click the "save sql as query" button. 2. Advanced: Edit the SQL by hand via the queries page. This option gives you complete control. By editing the list of columns after the "SELECT" keyword, you control which columns are visible in the bug list. By editing the "where" clause, you control which rows are visible. You can use a BugTracker.NET macro your SQL, "$ME", which is the userid of the current user. Using the $ME variable would allow you to write queries like, "Only Bugs Assigned to Me", or "Only Bugs Reported by Me". BugTracker.NET is able to display issues with different statuses or priorities using different fonts and/or colors. For example, you can configure BugTracker.NET to display high priority bugs with a bold red font and a yellow background. What makes this possible is that your SQL must be structured in a particular way. The first column must be either a color starting with "#" or a CSS style class. If it does not start with "#" it will be interpreted as a CSS style class. View example on how to use priority and/or status to determine the CSS style. "$FLAG" is another macro. It creates the column of blank/red/green squares that a user can click to flag a bug for himself. If you add custom fields, they fields automatically appear in the search results page, which uses a built in query, but not on the bugs page, which you control. So, you probably want to add custom columns to your queries too.


Corey Trager ctrager@yahoo.com http://ifdefined.com.