User Story "Assigned to"

[Walter]

Hello,

we work like that:

Keyusers are responsible for defining requirements and testing them after they have been implemented by the developers. During the process of user requirement definition the key user's name is in the "assigned to" field. If a key user finished the definition of a user story and its is assigned to an iteration we change the user story state "to in development". Furthermore we assign the developer lead to the user story. (so he gets an email notification) If the user story have been implemented by the developers the "assigned to" should be changed back to the keyuser who defined the requirement and has the overall responsibility for the user story. Unfortunately the information who created the requirement is nowhere in the system anymore.

That's why I think it would be good to have 2 name/person fields at the user story.

• the person who has the overall responsibility for the use case (this person should have the possibility to the define in the setup if he/she would like to be informed always if the user story changes)
• the person who is assigned to the use case (and its current state, like development, testing) at the moment. In certain project stages (e.g. requirement definition) the responsible person and the assigned to person could be the same, during other stages they could be different (e.g. key user and developer).

Please let me know what you think about it.

Kind regards
Daniel

[Jordan]

Hi Daniel,

 We have a few requests to be able to assign a story to multiple people. Our solution for such cases is to assign a story to the key user and to create a tasks and assign them to different users - Dev for the development tasks, QA for testing tasks, etc.
What do you think about that solution?

Kind regards,
Jordan
the Telerik team

[Walter]

Hello,

Unfortunately that does not work for us.
We want to track the hand-over of requirements to the developer team lead. I as a team lead would like to have the possibility to filter use cases which have been already assigned to me but are not scheduled for development.
I would appreciate if I could assign a use case to a person who has the overall responsibility but additionally to sub-team leaders (e.g. developer lead, q/a lead ...)

Both should have the possibility to get automatic email notification if the user story changes or if the are assigned to a user story.

Thank you
Daniel

[Velin]

Hi Daniel,

Thanks for the detailed information.

Your scenario makes sense to us but unfortunately this functionality has not been scheduled for any specific release yet. I have added one more vote for it to higher its priority when planning future releases.

In the meanwhile you could also use the tagging functionality to get multiple users emailed on item change.
For example, if you add tag with the name of the user interested in the work item - that person could filter the backlog by his name and subscribe for email notifications for each item. I know this solution is not perfect, but could do the job until we come up with a better solution.

Kind regards,
Velin
the Telerik team

[Ralf]

We have developers working in joint cooperation, some times on a daily basis, so we would also very much like to be able to assign multiple users to task, storyboards and iterations...
I haven't been able to find that type of functionality, with multiple users...

*Regards Ralf

[David Harris]

Hello Ralf,

It is not currently possible to assign an item to more than one user at a time. I would encourage you to visit our feedback portal and enter a new item describing the situation and your desired idea to resolve it. These items are often reviewed and can be used to open up a dialog with other customers and internal team members on how best to use or improve the product. In many cases these items will directly impact the features added to future releases of TeamPulse.

You can find the feedback portal at the following location: http://feedback.telerik.com/Project/8/

Regards,
David Harris
the Telerik team