2 answers
1 accepted
Hello markus.neuwald@canon.at
Do I understand correctly that you have existing standard-type issues that you want to make children of existing Epic-type issues?
If so, there is a flaw in your reasoning.
JIRA does not allow to directly move an standard issue-type to an epic -> first it is necessary to convert it to a sub-task, and within the tool i can set the new parent (epic).
Jira absolutely allow you to set the parent of a standard-type issue to an existing Epic through the UI without converting it to a sub-task.
One method is to view the standard-type issue and click the Add Parent option in the breadcrumbs above the summary.
Another option is to ensure you have the Parent field included in the Layout of the issue and then click there to insert the key for the Epic.
With regard to the failure in the import process, we must first know a few things:
1. What type of project does this concern? Get that information from the Type column of the View All Projects page under the Projects > More Projects menu.
2. How exactly are you accessing the CSV import process? Are you accessing that through System > External System Import, or are you accessing it from the Search Work Items screen and selecting Import Work Items from CSV?
3. Show us a screen image of the field mapping you are creating when you execute this import.
Hi Trudy,
about the project type - i'm not sure, but isn't it the information i already posted in the screenshot above? Projecttype = JIRA-Softwareproject
CAT-7528 - issuetype = epic
CAT-5921 - issuetype = standard-issuetype (Pre-Sales Deal Support)
Can you show us the Issue Types available to the project as shown through the Project Settings?
about the project type - i'm not sure, but isn't it the information i already posted in the screenshot above? Projecttype = JIRA-Softwareproject
There are two elements to the project type:
Company Managed vs. Team Managed
Business vs. Software vs. Service Management.
The View All Projects page includes both pieces of information.
What you pointed out tells us only that it is a Software project, not whether it is Team Managed or Company Managed. However, looking at both types of projects on my own instance I see that the Team Managed Software project currently doesn't include that field in its Project Settings Details page at all. So I am concluding that your project is Company Managed Software.
At this time, there are two CSV formats and field mappings you can use to update existing Standard issues to make them children of existing Epics.
Option 1: Use Epic Link in the field mapping
CSV File:
issuekey,type,summary,parent
ABC-1,Epic,Epic's summary,
ABC-2,Story,Story's summary,ABC-1
Field mapping:
Option 2: use issue ID
You don't have to have the issue's actual ID.
CSV File:
id,issuekey,type,summary,parent
1,ABC-1,Epic,Epic's summary,
2,ABC-2,Story,Story's summary,1
In the "parent" column you put the ID from the "id" column from the row that has the Epic's details. The row for the Epic should be before and standard issue that you want to assign to that Epic. The "id" values can be any unique set of numbers.
Field mapping:
I tested both of the above methods with pre-existing Story (level 0) issue types and pre-existing Epics (level 1) issue types. Both worked.
good morning,
here is the information about project-type:
you are right -> it is company managed software.
Next, i will try your suggestion and come back.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.