Hi guys,
Today, I come with a problem about JIRA’s epics and histories when we uploaded them with a csv.
When we create an epic task with his history (manually way), JIRA clasificate it with an hierarchical structure and we can show their good structure in a JQL (Epic task and his histories after her).
But, when we create this issues with a csv, this structure changes and the issues don’t have an hierarchical organization. I mean, epic tasks and histories don’t show in the correct order when we do a JQL.
Issue’s organization is made with a system field called “Classification” that give to the issues an order number. But, is this number random?
We want to know a way to understand this value and to modify or create it to show epics and histories correctly ordered by classification using the CSV file.
Hello Estefania,
Thanks for reaching out to us about this problem with the ordering of a classification field after importing an epic and associated stories from CSV. I'd like to try and reproduce this in my own environment, but I'll need more information about this field to proceed. Unfortunately, I am unaware of any system field named Classification that contains an automatically generated numerical value. Can you double-check that this is not a custom field? And if so, we need to determine how it is being populated.
Thanks
~Andrew Sweeten
Atlassian Support
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.