...
3. In the resulting window, populate all the required fields (the ones marked with a red asterisk) and specify any relevant information in the other fields, if needed:
...
Required fields:
Project | The name of your project. |
Issues Type | The type of your issue. The following options are available:
|
Summary | A short description of the issue. |
Description | Detailed information about the issue. |
Reporter | The user who reported the issue. |
4. After populating the fields, click Create.
...
6. Click Update to complete the issue creation. Once done, you will be able to find the issue in Jira.
| Info |
|---|
When using Jira for defect tracking, the Jira fields on the Create and Edit screens MUST be the same, otherwise users won't be able to properly file/modify defects. Refer to this Jira resource for more information: https://confluence.atlassian.com/adminjiraserver/associating-a-screen-with-an-issue-operation-938847289.html |
Create a defect from the Test Execution page
...
When creating a defect from the Test Execution page, you can also copy the steps of the failed test to the defect’s Description field. To do that, open the Copy Steps dropdown on the right and choose either As plain text or As wiki markup – Zephyr will automatically copy all the steps in the chosen format:
...
| Info |
|---|
Refer to this Jira resource for more information: https://confluence.atlassian.com/adminjiraserver/associating-a-screen-with-an-issue-operation-938847289.html |
The Update Defect window
The window shows the same values your issue has in Jira, including the values of the Sprint, Epic Link, Linked Issues, and Team fields:
...
2. In the subsequent dialog, populate all the required fields (the ones marked with a red asterisk) and specify any relevant information in the other fields, if needed:
Available fields:
Summary (required) | A short description of the issue. |
Description (required) | Detailed information about the issue. |
Component | The component the defect relates to. |
Version | The current version of your project. |
Status (required) | The defect status. Possible values:
|
Assignee (required) | The user the defect will be assigned to. |
OS | The operating system used. Possible values:
|
Priority | The defect priority that ranges from P1 to P5, where P1 is the highest priority. |
Target Milestone | The target version in which the issue should be resolved. |
Severity | The defect severity. Possible values:
|
Hardware | The type of the computer used. Possible values:
|
3. After populating all the required fields, click Create. The Update Defect dialog will open:
...