It's all about the answers!

Ask a question

can't get RTC "Plans" to work correctly using SCRUM ALM 2.0


Doug Oreilly (2768) | asked Jun 19 '14, 10:50 a.m.
edited Jun 19 '14, 10:51 a.m.

I am using RTC and the SCRUM ALM 2.0 template

Goal : 

1)  I would like to be able to see my current sprint plan with only the items in that sprint. 
2) I would like to see all items across backlog, release and sprint

Problem - 

1) When I bring up sprint 2 (the current sprint) It shows me backlog items in the taskboard that do not have any parent or child tasks that are in sprint 2.

2) I can create a plan against my Full Plan OR against my backlog.  I can't do it with both of them.  in my project area setup below I have tried to put the backlog inside the full plan but it will not let me and I get the following error

Project area cannot be saved.   Multiple iterations with the same parent use the 'backlog' identifier.ID CRJAZ6033E

Project Area Setup:  My Project area setup is as follows

- Main Development
 Trash
  - Full Plan
       - Release 1.0
           sprint01
           sprint02
       - Release 2.0
           sprint 3
           sprint 4
        - Release 3.0
           sprint 5
           sprint 6 
  - backlog

3 answers



permanent link
Doug Oreilly (2768) | answered Jun 27 '14, 3:11 p.m.
Solution was actually much more straight forward and obvious.  The box for "Include All Items" was check marked.  this brought in all other iterations. 

permanent link
sam detweiler (12.5k6195201) | answered Jun 19 '14, 3:56 p.m.
edit the archived iteration, and change its ID.. (backlog-old)
then the full plan, plan should work.

1) if items (in backlog or sprint 1) are CHILDREN of items in Sprint 2, then they will be dragged into the plan
(children MUST of course be AFTER (or included) the top level work.
you 'might' be able to filter them out with the Plan Exclude sub-iterations.. but as they are super-iterations, maybe not

permanent link
sam detweiler (12.5k6195201) | answered Jun 19 '14, 12:29 p.m.
2) what is the identifier for the 'Full Plan' iteration? 

1) may be caused by 2.

Comments
Doug Oreilly commented Jun 19 '14, 2:21 p.m.

I'm not sure how I ended up with these identifiers, but obviously I didn't but consistent thought into them.  I am not aware of what they drive and why the matter, but sounds like you are going to tell me why.  The identifiers are as follows (In Parenthesis)

- Main Development (Main Development)
 Trash
  - Full Plan (Full Plan)
       - Release 1.0   (1.0)
           sprint01 (1.0 S1)
           sprint02 (1.0 S2)
       - Release 2.0 (Release 2)
           sprint 3 (Sprint 3)
           sprint 4 (Sprint 4)
        - Release 3.0 (Release 3)
           sprint 5 (Sprint 5)
            sprint 6  (Sprint 6)
  - backlog (backlog)


Doug Oreilly commented Jun 19 '14, 2:24 p.m.

I do notice I have an archived "Backlog" with the same (backlog) identifier if that matters?

Your answer


Register or to post 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.