nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to import bulk defects into Jira ??

unknown

Accepted answers

Manoj Kumar Gangwar

Hi @[deleted] Welcome to the community!

To import bulk defects into Jira using a CSV file, you can do the following:

Go to Issues > Import Issues from CSV
Select the CSV source file
Click Next to go to the Settings page
Fill out the required fields and click Next
Map the column headers of the CSV file to the fields in the selected project
Click Begin Import

Here are some things to keep in mind when importing defects into Jira:

To import issues into multiple projects, add two columns to the CSV file with the headings "Project Name" and "Project Key".
To treat special characters literally, use double-quote marks around the section of text.
The summary field is required and should be a short description of the issue.
The import status is visible on the project page, and an email is sent once the import is complete.
If the import fails or is partially complete, an error log is available for download.
If usernames are not already defined in Jira, Jira will automatically create them based on the data in the CSV file.

All comments

Manoj Kumar Gangwar

Hi @[deleted] Welcome to the community!

To import bulk defects into Jira using a CSV file, you can do the following:

Go to Issues > Import Issues from CSV
Select the CSV source file
Click Next to go to the Settings page
Fill out the required fields and click Next
Map the column headers of the CSV file to the fields in the selected project
Click Begin Import

Here are some things to keep in mind when importing defects into Jira:

To import issues into multiple projects, add two columns to the CSV file with the headings "Project Name" and "Project Key".
To treat special characters literally, use double-quote marks around the section of text.
The summary field is required and should be a short description of the issue.
The import status is visible on the project page, and an email is sent once the import is complete.
If the import fails or is partially complete, an error log is available for download.
If usernames are not already defined in Jira, Jira will automatically create them based on the data in the CSV file.

unknown

Thanks Manoj !! am getting below error:

    "errors": [
        {
            "elementNumber": 0,
            "errors": {
                "customfield_10155": "Field 'customfield_10155' cannot be set. It is not on the appropriate screen, or unknown.",
                "customfield_10153": "Field 'customfield_10153' cannot be set. It is not on the appropriate screen, or unknown."
            }

Manoj Kumar Gangwar

Hi @[deleted] Please check both customfields if they are added to the issue create screen or not. If not then ask project admin to add both fields in the create issue screen.

unknown

Thank you Manoj!!

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira-service-management

jira-service-desk-unknown-hosting-type

jira-service-management-unknown-hosting-type