Issue Register /Issue Log is a documentation element of software project management. An issue log contains a list of ongoing and closed issues of the project.
An issue log is usually blank at the beginning of the project [1], but this is not always true for subsequent releases.
It helps you to monitor the status of your issues and track the actions taken to resolve them.
By using an issue log effectively, you can minimize the impact that issues have on your project, thereby increasing your chances of success.
The Issue Register or Issues Log helps you track the:
- Priority of each issue raised
- Impact that the issue is having on the project
- Actions taken to resolve the issue
Issue log-guided projects may be easier to manage in terms of completion time and progress estimation.
Basic Issue Information
- Issue reference number (ID): Typical number to identify different issues.
- Issue name: Issue's name.
- Description: Briefly describe what the issue concerns.
- Issue author: The person who raise this issue.
- Parties: all the people involved in solving the issue.
Issue Categories
- Issue type: what knowledge domain the issue belongs to. (E.g. IT infrastructure, IT application, etc.)
- Issue priority: it determines which issue is the most urgent and should be solved first. (E.g. the priorities may encompass Immediate, Soon, Later, etc.)
- Issue severity: how bad the consequence would be if the issue is left unsolved. (E.g. the severity may encompass Vital, Major, Medium, Minor, etc.)
Issue Date Information
- Date raised: when the issue is raised.
- Date assigned: when the issue is assigned.
- Deadline: when is the final date to get the issue settled.
- Date resolved: when the issue is actually solved.
Issue Status
- Current status: the current status the issue is within. (E.g. Investigating, escalated, resolved, etc.)
- Actions updating: Actions performed before issue is resolved (List all the actions according to dates.)
- Resolution: The final resolution to settle the issue.
Other Information
- Notes: Some ideas or things to remember.
| Issue ID | Issue name | Description | Issue author | Parties | Type | priority | Severity | Date raised | Date assigned | Deadline | Date resolved | status | Actions | Resolution | Notes |
| 0001 | Sample Issue1 | Sample Description | Mr.A | Mr.A,B; Mrs.C | IT Application | High | Critical | 20091010 | 20091011 | 20100101 | 20091015 | Resolved | Some Actions | Resolutions | Things to do |
| 0002 | Sample Issue2 | Sample Description | ... ... |
Issue-tracking systems
| | | | | |
| 1. HP Quality Center 2. IBM Rational Team Concert 3. ManageEngine ServiceDesk Plus 4. JIRA 5. Request Tracker 6. Team Foundation Server 7. Web Help Desk 8. BugTracker.NET 9. Bugzilla | 10. Assembla Tickets 11. Bontq 12. The Bug Genie 13. FogBugz 14. Fossil 15. Gemini 16. GNATS 17. GLPI 18. Google Code Hosting 19. IBM Rational ClearQuest 20. ikiwiki 21. Cerebro 22. codeBeamer 23. Debbugs | 24. FIT Issue Management 25. Flyspray 26. IssueNet 27. IssueTrak 28. iSupport 29. Launchpad 30. Liberum Help Desk 31. Kayako SupportSuite 32. LibreSource | 33. MantisBT 34. Microsoft Dynamics CRM 35. Mojo Helpdesk 36. OnTime 37. org-mode 38. OTRS 39. Planbox 40. Pivotal Tracker 41. Plain Ticket 42. Projistics 43. Redmine | 44. Remedy Action Request System 45. Roundup 46. StarTeam 47. Supportworks 48. Teamwork 49. Trac 50. Unawave 51. Wrike 52. YouTrack 53. Zentrack 54. Zoho BugTracker |
Reference: Link1
Thanks & Regards,
| Arun Manglick Digital Group InfoTech Pvt. Ltd. Pyramid building, Plot No.5 Rajeev Gandhi InfoTech Park, Phase I, Hinjewadi, Pune - 411057, India Office: +91 20 66532084 Fax: +91 20 66532052 Mobile: +91 9850901262 |
No comments:
Post a Comment