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; } } }

Mapping fields

Cristina_qfkh4s

Hi,

I have a csv file, with epics, story, task and substask and i would like to import this file on Jira instance. How i should map all the fields -> at least the epics to create the relation between epic-story? task and substask? epic-task?

Thank you

Accepted answers

Kian Stack Mumo Systems

@Cristina,

Can you try to follow what is outlined in this question?

All comments

Kian Stack Mumo Systems

@Cristina,

Can you try to follow what is outlined in this question?

Cristina - Elena Andrei

Hi @Kian Stack Mumo Systems , thank you for the replay. it's not very understanble for me.

I know that first it's recommended to export epic and import on another instance.

Then export another excel file with standard issuetypes like stories and task , bugs where i have to add a column called epic link. But how i can map epic link and epic name?

Then to import subtask what fields are needed and how i can map those.

Could you please clarify me? maybe some examples could be useful.

Thank you

Kian Stack Mumo Systems

@Cristina - Elena Andrei,

You would do as it says in that discussion:

Issue Type,Epic Name,Summary        ,Epic Link
Epic      ,  my-epic,Build a car    ,
Story     ,         ,Build an engine,  my-epic
Story     ,         ,Buy some tires ,  my-epic

So the Epic Name would be "my-epic" and then the Epic link would be "my-epic" for each of the issues you want linked to the Epic.

In the case of parent tasks and child tasks, you would follow this guide and specifically want to look at this section:

Creating sub-tasks

You can create sub-tasks of issues by:

Adding two columns to your CSV file with the headings "Issue Id" and "Parent Id"
Ensuring each regular (non sub-task) issue is given a unique (sequential) number in the "Issue Id" column. Do not include any value in the "Parent Id" fields for regular issues.
Referencing the unique "Issue Id" number of the regular issue in the "Parent Id" column. Do not include any value in the "Issue Id" fields for sub-tasks.

In this example, the fourth issue will be a sub-task of the second issue if you match the "Issue Id" and "Parent Id" fields in your CSV file to the corresponding issue and parent ID fields in Jira:

IssueType, Summary, FixVersion, FixVersion, FixVersion, Component, Component, Issue ID, Parent ID, Reporter
Bug, "First issue", v1, , , Component1, , 1, , abcde-12345-fedcba
Bug, "Second issue", v2, , , Component1, Component2, 2, , fedcb-12345-edcba
Bug, "Third issue", v1, v2, v3, Component1, , 3, , abcde-12345-fedcba
Sub-task, "Fourth issue", v1, v2, , Component2, , , 2, fedcb-12345-edcba

Welcome!

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

Quick Links

Find more posts tagged with

server

jira-software

jira-software-server