Release 2006.6 FAQ

This FAQ applies directly to the new User Story Workspace introduced in R2006.6.

1. I have Program or Enterprise Edition, will the new User Story Workspace affect my work?
   No. The new User Story Workspace will not impact the current Use Case Workspace so you can continue your work in Rally as usual.
   
   
2. I have Team Edition, will the new User Story Workspace affect my work?
   No. Team Editions subscriptions will be automatically migrated to the new User Story Workspace with the release. You will be able to take advantage of the new functionality including the new planning screen, unified backlog and automatic state rollups.
   
   
3. I can't decide what Workspace is right for my new Release? Can you help?
   See the Overview for a description on the characteristics of each Workspace type.
   
   
4. Is there a Card in the new User Story Workspace?
   No. Each User Story contains its own schedule information so this removes the necessity to have a Card. Defect and Defect Suite also have the information necessary to estimate, rank and schedule them.
   
   
5. Are Use Cases available in the User Story Workspace?
   No. If it is critical that you define Use Cases as part of your requirements activities, we recommend staying in the Use Case Workspace. However, there are a couple alternatives to use cases. One option is to use a User Story and create a bulleted list of the steps for the use case. The second (and preferred) method is to define the high-level requirements with User Stories and define the details with a set of Test Cases. (Test Cases have pre/post conditions and a set of steps to define the exact sequence of events).
   
   
6. Can I split a User Story analogous to the splitting of a Card that the Use Case Workspace supports?
   Yes. If you go the User Story detail page, you can split the User Story. When you split the User Story, a copy of the User Story and the selected Tasks are moved to a subsequent Iteration of your choosing.
   
   
7. With the new n-level hierarchy of User Stories, what happens with my associations (e.g. Tasks, Test Cases, Defects, Attachments) if I create a child User Story?
   Only the leaf nodes can have Tasks so the Tasks of a parent story are moved to the child story. Test Cases, Defects & Attachments remain associated with the parent User Story. The values for Release, Iteration, State, Rank, Owner, and Blocked are copied from the parent to the child.
   
   
8. How can I see the new User Story Workspace?
   You can create a User Story Workspace in your current subscription. If you would prefer to use a "test" environment, you can see your data on our Sandbox server. Use your regular login credentials and please remember all data on Sandbox will eventually be reset and lost. However, either of these methods should assist you in understanding the capabilities of the User Story Workspace.
   
   
9. Can I change my current Workspace type at any time?
   You can always create a new Workspace that is a User Story or Use Case type. Once Workspaces are created, they are static and there is no way to switch the Workspace type.
   
   
10. I have existing data in a Use Case Workspace, how do I move this data to the new User Story Workspace?
    Translation (e.g. not a full migration) of Use Case Workspaces to User Story Workspaces will be possible in an upcoming release. We will notify the administrative point of contact for each organization when translation is possible. We are still prioritizing how the translation will be implemented so please email Rally Support if you have feedback.
    
    
11. Once translation is available, are there recommendations for when we should translate our data?
    It is best to translate during a Release or Iteration boundary so it does not disrupt your current work.