It's all about the answers!

Ask a question

"No Work" in a Plan View

Murat Isleyen (191620) | asked Jan 24 '14, 6:52 a.m.
In the plan view, any work item suddenly does not appear. In the plan details, the burndown chart is fine. It shows the correct number of work items. Under the plan title, "0 items: 0 open, 0 closed" is written.

Also, some of plans looks like correct. But I can't identify the reason (because the owners are the same, a project area).

I have tried the following actions
  • Cleared the browsers' caches.
  • Changed the owner of the plan and iterations.
  • Checked the work items (under the plan) and "Planned For" field is seen as to be which shows the relevant iteration.
  • Removed any exclusion in plan view.
  • Created a new plan with different scenarios.

And I can not find the history information about the plan, such as who and when changed what.

Any idea on how these work items are gone?

Krzysztof Kaźmierczyk commented Jan 24 '14, 7:07 a.m.

hi Murat,
Please check ccm.log file on your server. You might have any error there.
Also what is your RTC version?

Murat Isleyen commented Jan 24 '14, 8:35 a.m. | edited Jan 24 '14, 9:02 a.m.

Hi Krzysztof,

RTC version is 4.0.3.

I checked the ccm log file and I can find the following lines related to the plan/iteration, I guess.

2014-01-23 15:40:11,247 [http-bio-9443-exec-7204 @@ 15:40 071357 /ccm/service/]  WARN .team.repository.servlet.AbstractTeamServerServlet  - CRJAZ1163I IllegalArgumentException processing POST request for CRJAZ1170I The request was made by user "071357" from "".CRJAZ1166I The stack trace hash is 1D6C2E5077156F21B8A883B4F9E4F4B21950D2EF.
java.lang.IllegalArgumentException: _in predicate value array is empty

2 answers

permanent link
Murat Isleyen (191620) | answered Jan 29 '14, 6:55 a.m.
The reason is that the timeline for the team area is assigned as "Unassigned" without any interaction. Everything is clear right now. Thanks.

permanent link
Krzysztof Kaźmierczyk (7.4k370102) | answered Jan 24 '14, 9:04 a.m.
Hi Murat,
It is known issue and has been described in following technote:
Please let us know if resolution steps from that technote helped you.

Your answer

Register or to post your answer.