...
This section provides a detailed introduction of the four three most common types of Jira issues involved in QA Testing: the Story, the Task, the Bug/Defect, the Enhancement, and the Test Case.
Task
The Task is an OLE Jira issue type that serves as a "to do" item in developing a piece of functionality. SME (Subject Matter Expert) teams create parent Jira tickets and attach specifications to them. The development team reviews the specifications and then determines what Tasks need to be accomplished in order to establish the requested functionality. Breaking up specifications into Tasks allows for faster and more incremental development
Bug/Defect
Like the Task, the Bug/Defect issue type also serves as a "to do" for developers. In this case, the "to do" is to notify programmers that an already-established, previously tested piece of functionality is no longer working.
...
The Test Case is the basic OLETS issue type. Test Cases tend to represent one item from the Acceptance Criteria of a Functional Specification document. Alternately, a Test Case can represent one Bug/Defect item which is ready for testing.At At the time of testing, a Test Case should include a descriptive statement of what is to be tested (purpose statement), as well as a set of general instructions (steps) for how the test should run. By the time the Test Case is ready for review by the QA team, it should also include a Selenium script recording all the steps undertaken during testing of the issue.Test Test Cases will relate to the Story Enhancement containing the relevant functional specifications, and to either a Task or a Bug/Defect establishing the functionality to be tested.
...