Bug or not? Parent relations not displayed correct...
Hi Jazz-Team,
I have the following problem. When I plan an item which has some parent items, the parent items hierarchy is displayed sometimes correctly, but sometimes not (in sprint plan). My parent item hierarchy is like the following: Requirement, Use Case, Story, Task. Example: When I plan a task from Backlog to Sprint 1 for example... the task item appears there of course. And normally R, UC and S are displayed too (greyed) with link to "Planned for Release 1.0". But sometimes the top parent item is then UC or just S... And I don't understand why. All items are linked correctly... Can anybody explain me the reason for this? Is this a bug or not? Greetz C. Zndorf |
4 answers
I have the following problem. When I plan an item which has some This sounds like a bug. Do you see this immediately after adding the work item to the plan or re-parenting them? Do you still see this issue after refreshing / reopening the plan? -- MikeS Jazz Agile Planning team |
|
Hello, Michael,
the issue stays after reopening and refreshing the plan. I think it has something to do with the fact that I sort the work items with the help of plain java and the method .setTarget(). I'm not sure, but it could be that the save process does not finish really, and the parent item hierarchy gets unfinished. I tried to put the save process into a thread and putted in a break after each save statement, but it did not help. Any ideas? Greetz C. Zndorf |
the issue stays after reopening and refreshing the plan. I think it There might be an issue with links that exits on the working copy only. I can reproduce the following behavior manually: 1) create a Plan X containing a work item A 2) create a work item B that is not included on the plan X. 3) In the work item editor for B, add A as a child observe: the new parent is not shown in the plan 4) refresh the plan observe: the new parent is still not shown in the plan 4) save work item B, refresh the plan observe: the new parent is shown in the plan however, if you do the linking the other way round in step 3 (ie set in A's editor B as the parent), it works immediately. feel free to open a defect against this behavior. -- MikeS Jazz Agile Planning team |
|
This is not the situation I have. In my plain-Java application, the first step is to create all Work Items in one plan ("Backlog"). In my second plain-Java application I sort the Work Items to the sprint plans. In the first 5 sprints plan everything works well. But when there are more than one children items in the hierarchy, the parent item hierarchy is not correct. The strange thing: The more children items, the shorter the parent item hierarchy. Example:
If there is only one work item in lowest-level container, the whole hierarchy is shown (Requirement , Use Case, Story ,Task). 3 work items means the hierarchy is only shown from Use Case Container on. And so on.... I will try to link now directly to work item instead of linking to working copy. Maybe this will help. Greetz C. Zuendorf |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.