Bug, Change Request & Issue Tracking

Woodpecker IT is designed for recording and tracking issues, within a freely defined workflow. Woodpecker IT does not predefine the type of issue you want to track. Range of use Woodpecker IT can be used for bug, change request or requirement tracking or as helpdesk solution.

Woodpecker IT differs from other systems in being extrem configurable and fits to the individuality and peculiarity of your project You can configure Woodpecker IT in 3 main parts: Configurability the data structure the workflow and the user rights

Every issue can be spezified by some informations For example: – a category – a description – the user who created the issue – a priority Date structure – any other information

1ProblemHighKurtload project, article = 100 Programm crash 2RequirementLowAlfredDefault setting for article counter This informations will be saved in the Woodpecker IT-database and will be displayed in a table Table 1ProblemHighKurtload project, article = 100 Programm crash

1ProblemHighKurtload project article = 100 programm Crash 2RequirementLowAlfredDefault setting for article counter First you have to define the rows of the table IDCategoryPriorityUserReproductionDescriptionDeveloperEstimat. Time TestCauseDate closed Attachem ent 1ProblemHighKurtload project article = 100 programm Crash 2RequirementLowAlfredDefault setting for article counter Table

1ProblemHighKurtload project article = 100 programm Crash 2RequirementLowAlfredDefault setting for article counter The rows are the central element of the data strucure IDCategoryPriorityUserReproductionDescriptionDeveloperEstimat. Time TestCauseDate closed Attachem ent 1ProblemHighKurtload project article = 100 programm Crash 2RequirementLowAlfredDefault setting for article counter Data structure

1ProblemHighKurtload project article = 100 programm Crash 2RequirementLowAlfredDefault setting for article counter In the data structure will be also defined: IDCategoryPriorityUserReproductionDescriptionDeveloperEstimat. Time TestCauseDate closed Attachem ent 1ProblemHighKurtload project article = 100 programm Crash 2RequirementLowAlfredDefault setting for article counter Data structure the data typ,default values and if the field is required. Data type f.e. drop downs Default Values Username Field is required Data type f.e. text

Workflow The second main part of Woodpecker IT is the workflow. You can build up the individual process of your company in Woodpecker IT.

Created A Customer finds a bug and creates an issue in Woodpecker IT Workflow

A developer is working on the problem Createdin progress Workflow

Createdin progressin test The developer solved the problem Now the bug should be tested again Workflow

Createdin progressin testsolved The tester is testing the bug The bug is no longer reproducible Workflow

Workflow & Data structure IDCategoryPriorityUserReproductionDescriptionDeveloperEstimat. Time TestCauseDate closed Attachem ent 1ProblemHighKurtload project article = 100 programm Crash 2RequirementLowAlfredDefault setting for article counter In Woodpecker IT fields can be assigned to a status IDCategoryPriorityUserReproductionDescriptionDeveloperEstimat. Time TestCauseDate closed Attachem ent 1ProblemHighKurtload project article = 100 programm Crash 2RequirementLowAlfredDefault setting for article counter IDCategoryPriorityUserReproductionDescriptionDeveloperEstimat. Time TestCauseDate closed Attachem ent 1ProblemHighKurtload project article = 100 programm Crash 2RequirementLowAlfredDefault setting for article counter IDCategoryPriorityUserReproductionDescriptionDeveloperEstimat. Time TestCauseDate closed Attachem ent 1ProblemHighKurtload project article = 100 programm Crash 2RequirementLowAlfredDefault setting for article counter IDCategoryPriorityUserReproductionDescriptionDeveloperEstimat. Time TestCauseDate closed Attachem ent 1ProblemHighKurtload project article = 100 programm Crash 2RequirementLowAlfredDefault setting for article counter

User rights The third main part of Woodpecker IT are the user rights. Every user can have different rights. e.g. some user rights, - see charts and reports - set hierarchy of issues - set issues invisible - create, delete, mail, copy and move issue - chat access, data import and export

User rights You can define a complex filter statement to define which issues a user can see. You can also set workflow permission, f.e. - Which status changes can the user do? - Which access type ( no access, read, write) does the user have to a field, referring to the issue status? - Which columns are visible for the user?

Notifications For each status change you can define, which project member should get a automatic mail notification.

Notifications Customer Kurt creates an issue Bernd, the developer and Patrick, the project leader are getting an created Automail to: - Bernd - Patrick

Notifications Tanja, the tester cannot reproduce the bug and sets the status to solved createdin progressin testsolved Patrick and Kurt are getting an and are informed, that the bug is solved Automail to: -Kurt -Patrick

Other Features webbased Licence & ASP-Version locking issues hierarchical issues sending and receiving mails save HTTPS-connection attachements with no limit

Other Features complex user filter generator Reports CSV-Import & Export Multilingual Online-Help history function to each field Chat

Benefits Against other systems Woodpecker IT has clear benefits: flexible configurable  wide rage of use easy to configure /ASP-modell  fast adoption low costs  fast amortization of the investment

Wide range of use unlimited individual fields, configurable with data typ, default value, history and if they are mandatory all status and status changes are free definable references between issue over projects many user rights and visibility settings individual filter generator

Fast adoption ASP-modell  no installation intuitional and user-friendly interface  no training needed consulting on defining workflow and configuration of Woodpecker IT  fast adoption

Fast amortization completly webbased  no client installation ASP-modell  no server installation easy to configure  no training costs/-time for the administrator clear, easy-to-use interface  no training costs/-time for the end user low licence / asp costs / user (licence ca. 100 €, asp ca. 10€ / month)

Customers

Contact You need more information: You want - a personal consulting - a demo account Infoline: +49 (9472) 91120