Making a template available across projects

[Ken C]

I'd like to be able to use a template that contains a default set of
tasks. I've created that template but it is only for one sub project
under my main project. Can this be done at the upper project level
for all sub projects but not at the system level?

[William Gerardino]

Hello Ken. I am very new to this technology myself so cannot respond with
any authority. Although it seems this should be doable. The question I
would imagine is 'copying' or 'moving' this template to the next level.
How that occurs I am not entirely clear on.

Good luck with it and feel free to contact me.

Thanks.

Bill

>--
>You received this message because you are subscribed to the Google Groups
>"VersionOne-users" group.
>To post to this group, send email to versiono...@googlegroups.com.
>To unsubscribe from this group, send email to
>versionone-use...@googlegroups.com.
>For more options, visit this group at
>http://groups.google.com/group/versionone-users?hl=en.
>

[Steve Paro]

Hi William and Ken,

If you want to make a template available across projects, simply change the Project attribute for the template and select a parent project. For people to use the template, they will need to at least have observer rights to the parent project so that they may find the template.

Steve Paro

[Cadieux, Kenneth P]

Thanks! I appreciate the answer.

[John Ahlstrom]

Friends:

If this is heresy, please put down your torches.

We frequently discover that we have to add or remove TASKS into or out
of an iteration before the iteration is done and closed.

These are intrinsically tasks not backlog items. E.g. we have a
backlog item LDAP Authentication of logins.

I haven't been able to find a way to move these into the next sprint
before closing the current sprint. This
clutters the current sprint detail, member detail, burndown chart, ...

It is really not appropriate to create new backlog items, assign them to
the next sprint and move the tasks being removed from the current sprint
to those backlog items.

Is there any other way?

Thanks

John Ahlstrom

[Brad Laudal]

When this occurs for me, I move the entire card into the next iteration because the card itself isn't complete unless all of its tasks are completed. So the velocity is deferred until the next iteration as well.

There is a way to split cards in V1, and maybe when you split the card you can indicate which tasks should go to the new card and which stay with the old card? I'm not sure about that...we don't split often.

Thanks,
Brad

Friends:

Thanks

John Ahlstrom

--

[Tim Gleason]

When you split a task in VersionOne the following happens:

-A new copy of the story is generated.

-Any open tasks/tests are carried forward to the new story by default (but you can edit them before saving the new copy.)

-Any attachments, links and conversations associated with the original story are NOT carried forward to the new story. This is a pain point for my organization.

Other things may happen as well of which I can't remember.

-Tim

[Vansrmpan]

Is there a way to pull a report on failed test cases? Which ones
failed for which user story?