Using the Bika Issue Tracker
Create an accountOnly authorised user can log issues, comment on and eventually close them. Once logged in, users have access to prioritised boards configured per Epic, issues combined in Sprints, reports and road maps Configure the Create screenOnly a few parameter are required when issues are logged and the Create screen is a little cluttered. Trim it down for your user Log an issueBugs, Improvement and Feature requests, Tasks New Bika Jira Issue Tracker |
Important Issue logging conventionOne issue per tracker itemSeparate different issues to make them easier to manage and look up Meaningful subject linePlease give issues meaningful titles to make it easier to find them on list displays, in email folders and on-line searches Answer these questionsWhat did you try to do? What did you expect to happen? What happened? Provide the page address or URLAttach Screenshots*Attach relevant data filesE.g. in the case of an Import. If the file contains sensitive information, upload it to the project's private Google folder and paste the link in the tracker comment Error messagesPlease copy error message text into the issue description, not a screen shot, we need to search on the text and IDs NB Images can be pasted directly from your clipboard into description and comment fields |
Resolution workflowIssue CreationIssues are created with status Open. Managers assign open issues to technicians, and when they start work on an issue, move it on to In Progress Technicians Resolve an issueWhen fixed. This is the bug reporter's signal, delivered per email, to re-test Re-Open or Close the issueIf the issue persists, the reporter comments and re-opens it, and the cycle repeats When the issue passes testing, watch it disappear from the to do list and experience some feelgood!
Atlassian once more makes Jira - the best software development, issue and team management tool there is - available to Open Source Bika project gratis. Many many thanks
|