Defect #32861

Strange issue tree after importing subtasks

Added by Adam Oscilowski over 1 year ago. Updated 12 months ago.

Status:Needs feedbackStart date:
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:Issues
Target version:-
Resolution: Affected version:

Description

We have imported subtasks to RM using csv:
"Temat";"Typ";"Start";"Koniec";"Parent";"Description";"Autor"
"Some Subject1";"Development";"2020-01-15";"2020-03-31";"#68";"some desc";"autor"
"Some Subject2";"Development";"2020-01-15";"2020-03-31";"#68";"some desc";"autor"
"Some Subject3";"Development";"2020-01-15";"2020-03-31";"#68";"some desc";"autor"

Tasks have been imported correctly, according to RM messages. But they are displayed in strange way.
Picture:
1. Looks like this task is assigned to multiple parent tasks?
When I call API http://*/issues.json?issue_id=152, only 68 is mentioned as a parent - OK.
When I call API http://*//issues/68.xml?include=children, 152 is mentioned as a child - OK.
When I call API http://*//issues/65.xml?include=children, 152 is NOT mentioned as a child - OK.
BUT when I open tasks 65-68 via web, I can see task 152 in each of them as a subtask, while it should be a subtask of 68 only. - NOOK.
152 opened via web looks like in attachment.
2. Tasks: 65,66,67,68 have common parent: 64 and are on the same level. In this picture it looks like 65 is a child of 64, 66 a child of 65 and so on. But it looks fine when I open i.e. task 65 - it's a child of 64 only.

new.png (13.6 KB) Adam Oscilowski, 2020-01-24 17:21

History

#1 Updated by Go MAEDA over 1 year ago

Could you try the following command to fix the tree?

bin/rails r 'Issue.rebuild_tree!'

#2 Updated by Go MAEDA 12 months ago

  • Status changed from New to Needs feedback

Also available in: Atom PDF