Vote #80627
未完了Strange issue tree after importing subtasks
ステータス:
Needs feedback
優先度:
通常
担当者:
-
カテゴリ:
Issues_2
対象バージョン:
-
開始日:
2022/05/09
期日:
進捗率:
0%
予定工数:
Redmineorg_URL:
category_id:
2
version_id:
0
issue_org_id:
32861
author_id:
440562
assigned_to_id:
0
comments:
2
status_id:
10
tracker_id:
1
plus1:
0
affected_version:
closed_on:
affected_version_id:
説明
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:
- 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.
- 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.
journals
Could you try the following command to fix the tree?
<pre>
bin/rails r 'Issue.rebuild_tree!'
</pre>
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
いいね!0