User Stories being carried forward to a new sprint and % complete

Hi Naomi, 

Your best bet is to leave the user story under the RBL project, and then create sub tasks that you will later move to the relevant iteration and create a shortcut under the original user story.  That way your RBL will reflect your exact progress and if tasks need to be carried over into another iteration, you can create a new task under  the user story and close out the task in the previous iteration. 

There is a custom action that I can send you that will actually move a work item to an iteration and create a shortcut under the original parent, let me know if you need it. 

Another option is to create custom fields on task levels that will indicate that a task is being continued in the next iteration.  But this may not be the way you want to work. 

Let me know if you have any other questions. 

Thanks!

Helena

Hi there, I would like to create user stories, however how do I specify this to be a user story. In the agile demo there is a column ts_Workitem that displays user story, Where do I find this?

Many thanks,

Imran.

The user story is essentially the task name.  A task object with the category of "user story" is used to represent user stories.  If you look at the team board, it is giving you the project's tasks in a SCRUM-oriented view.

Thank you for this, however in the Clarizen Agile demo, there is a field column called (TS_WorkItemType) which displays the task as a user story in the workplan view.   Is this a custom field I need to create?

This is included in the Team Board app from our app store: http://www.clarizen.com/appsmarketplace/item/Team-Board.html

Got it. Brilliant!

Thank you.