THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
| Issue Type | Definition and when to use this type |
|---|---|
| Bug | A bug is generally a problem with code or data which is not functioning correctly. |
| Improvement | An improvement is something that enhances the functionality of an existing feature |
| New Feature | New functionality that does not already exist (What is the difference between this and Wish? Proprosal: Proposal: All potential improvements could start as a Wish. When they have been discussed / reviewed by the community then they can be changed to be an approved New Feature) |
| Task | A Task is an action that needs to be carried out that does not fall under any of the other issue types. (NOTE: We have used Tasks in the past - maybe need to specify more clearly when to use....) |
| Test | A Test is a unit test or integrated test |
| Wish | A Wish is a requirement for new something that does not already exist (What's the difference between this and New Feature? Proposal: All potential improvements could start as a Wish. When they have been discussed / reviewed by the community then they can be changed to be an approved New Feature) |
| Sub Task | This task is a child of another JIRA (NOTE: We use sub-tasks but not Tasks.....) |
Description
The issue description is the most important part of the JIRA issue as it provides information that will allow someone else to investigate and resolve it. It must be written in such a way that it is clear enough for someone to easily replicate the problem. This means that you need to include information about
What you were doing when the issue occurred? (e.g what application, screen)
Clearly highlight the steps that you went throu. o that someone with
Guidelines for writing JIRA mentioning clarity, provision of solution.
Priority
All JIRA issues need a priority as it determines what needs to be worked on. This is important because it helps to ensure that the community is focussed and working on the right tasks.
...