Using the JIRA JSON Importer its possible to create issues and sub-tasks for projects. When I created json to import issues that used the subtask attribute on issues, I encounter exceptions that indicated certain fields were not mapped correctly, or were not the same types as the standard issue json object (i.e I couldn't build a full list of issues and nest that with in a parent issue) .
I found that I could create a link with the name of "jira_subtask_link" and it would enable sub task linking (i.e I could build a list of jira issues, and control the sub tasks via links). However, when sub task links are created the sequence of the link is not created (its left null) . Jira outputs an exception whenever sub tasks don't have a sequence.
Is it possible to trigger resequencing of jira issues, so that all subtasks get a sequence ? Is there a sequence option on the JSON Import I can use ? Right now, the only fix is to go into every issue, and get it to trigger a resequence by moving a sub task out of the parent issue. Dose anyone have a solution to get around the exception on issues that have sub-tasks that don't have sequences?
(I created a JIRA issue for the exception showing on the interface, because I think showing an exception when a sequence is missing on a subtask is unexpected behaviour (even if the data was created using the BETA importer) https://jira.atlassian.com/browse/JRA-34729 )
I have added some code to help show things in more detail. https://bitbucket.org/e0150228/one-off-atlassian-perl-work/src
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.