Ticket (Story) Type : Feature / Bug / etc

8 posts, 0 answers
  1. Sebastian Talamoni
    Sebastian Talamoni avatar
    32 posts
    Member since:
    Mar 2008

    Posted 26 Apr 2010 Link to this post

    Hi,

    When working with stories one of the most basic/important features that I am missing is the concept of Work item Type.
    All other software packages have either a flexible list of types or a fixed list of types.
    But it seems that TeamPulse only support "Stories" as the only ticket type.

    If this is done deliberately it means that the planning will not allow me to separate bugs from features.
    For our team this is a very important metric since it help us finding quality levels. (  a bigger % of bugs --> we are working with < quality)

    Is this already in the roadmap/plans to be added to the product? 
    Am I missing something? Will integrating with TFS help me in some way?


  2. Ryan
    Admin
    Ryan avatar
    164 posts

    Posted 26 Apr 2010 Link to this post

    Hi Sebastian Talamoni,

    Implementing support for Bugs and Tasks in some manner is in our backlog. We are aware that Bug tracking and metrics are important when planning. Hopefully some of these features make it into our next release. Only supporting Stories was just a choice we made for the beta release.

    Regards,
    Ryan
    the Telerik team

    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.
  3. Sebastian Talamoni
    Sebastian Talamoni avatar
    32 posts
    Member since:
    Mar 2008

    Posted 05 Oct 2010 Link to this post

    Hi Ryan, 

    I'm back to re-evaluate TeamPulse for our team.
    Although I see lots of nice features have been added to the product the bug tracking issue is still a TODO item.

    Several thread are pointing to the same need: 1st Post , 2nd Post, etc

    My question is :
    • Is this "really" going to be added?? When? How?

    Suggestion : Why not integrating with your PITs ?

    Thanks in advance,




  4. Ryan
    Admin
    Ryan avatar
    164 posts

    Posted 07 Oct 2010 Link to this post

    Hi Sebastian Talamoni,

    Bug tracking is still an important item in our backlog. However we are busy right now with adding TFS Sync into TeamPulse and therefor Bug Tracking will not be in our 2010 Q3 release. It will be considered for our 2011 Q1 or Q2 releases.

    Once we have TFS sync, perhaps managing Bugs in TFS can be a temporary option for you?

    When we do add bug tracking to TeamPulse, we want to be sure to do it right. Are there any particular must have features you look for in a Bug Tracking tool?

    As for integrating TeamPulse with PITS, we have this in our backlog. But, I think it makes sense to implement Bug Tracking in TeamPulse before integrating with PITS.

    Sincerely yours,
    Ryan
    the Telerik team
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
  5. Sebastian Talamoni
    Sebastian Talamoni avatar
    32 posts
    Member since:
    Mar 2008

    Posted 08 Oct 2010 Link to this post

    Hi,

    I'm actually trying to get out from TFS ;) We are currently using ONLY tfs for the tickets and I want to get out of it. We don't use any other feature of TFS ( Source control = no , Build server = no ) so it makes for us to use a simpler (TFS is just too complex ) system.

    Could you explain how the Sync it's achieved ?? What are the rules for the sync?

    We also have our OWN Bug tracking system working years now so If we could interface it with teamPulse == problem solved. Is this possible? I would expect to have an ICustomBugTrackingProvider
    • IEnumerable<IBugItem> GetBugsForStory ( int storyID) 

    If you give this entry point as an interface/pluggable service then :
    • You can hook with TFS
    • You can implement your own TeamPulse tables / entry forms for bugs
    • I can implement that interface against my own bug tracking system.


    The most important thing is the relation between tickets (bugs /extra non-planned tasks) and TeamPulse.

    If a User Story is closed but a bug is found and related to the user story the "normal"flow is to put back that user story in the backlog but a special status "reopened".  (Please don;t send me links telling that it should not happen according to Agile methodologies because it still does happen no matter how intense you make your specs + tests .. )

    It's extremely important to navigate from the Story to the Bugs found.  I would expect an "extra tab" called "Inicidents" (if you agile people find bugs too old fashion term ;) ) Those Incidents are taken from whatever system you want  ( TeamPulse , TFS o other). It's basically impemented with a call to IEnumerable<IBugItem> GetBugsForStory ( int storyID) .

    In your Q3 Roadmap it's mentioned that you are going to improve the developers point of View. And it's true that's REALLY needed. Several developers in my team said to me: "nice tool but where is my task list!! "  So obviously it's not clear from their POV. For a DEV that works on a much deeper/atomic layer than PM's they need to have the MyTasks (currently not present!).

    My conclusion so far is : If you don't have a relation with a ticketing system you can't use TeamPulse for Developers and that breaks the concept of the tool.Because you don;'t want to ADD Bugs as stories.

    I was expecting TeamPulse to be the "entry" point for my developers. Currently it's not practical without the MyTasks concept.

    MyTask
    • Stories assigned to ME for this iteration (ok, this is the only thing in TeamPulse today) +
    • Tasks for this iteration  (not included in TeamPulse) (unbelievalbe I can't find this currently on team pulse, don't forget that a User Story has 1 Assigned to but inside the story there are tasks assigned to other people, this flow is currently not good implemented in TeamPulse) . As A developer I want at least to know that in 2 days i need to do something related to another developers user story. This tasks assigned to me ARE part of my Tasks.
    • Bugs in Stories inside this iteration  (not included in TeamPulse) : currently this need to be solved with other tools.
  6. Ryan
    Admin
    Ryan avatar
    164 posts

    Posted 13 Oct 2010 Link to this post

    Hi Sebastian Talamoni,

    Our sync implementation for the Q3 release will only support syncing to TFS. However, we will be looking into expanding it in the future to support syncing to other systems, or perhaps even allowing users to code their own providers that can communicate with our sync. We will be posting a blog in the next week or so giving more information about TFS sync.

    The scenarios you suggest related to Bug Tracking seem valid to me. I will make note of them in our backlog.

    The 'My Tasks' feature that you mention is high on our list to add into TeamPulse. It will be considered for our Q1 or Q2 release in 2011.

    Thus far, we have been putting much of our focus on the Planning features of TeamPulse. And we have extended this even further with 'Idea Management' which will be available in our Q3 release. 

    For more information out the Q3 beta release that came out today see: http://www.telerik.com/team-productivity-tools/products/teampulse/teampulse-beta.aspx

    Thanks for all your feedback,
    Ryan
    the Telerik team
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
  7. David Sandor
    David Sandor avatar
    16 posts
    Member since:
    May 2009

    Posted 02 Dec 2010 Link to this post

    I agree 100% with Sebastian. 
    I would love to use the product but need to be able to see my bugs associated with a Story.  With that alone I would be able to use the product for my team.


    Optionally it would be nice to include as children of a Story a TFS Task or TFS bug or TFS *.  The mapping is great but you seem to have hardcoded Stories -> Requirements and Tasks -> Tasks (for my CMMI template at least).  I would love to be able to map Story children of any TFS type.

    Thanks,
    David Sandor
  8. Ryan
    Admin
    Ryan avatar
    164 posts

    Posted 06 Dec 2010 Link to this post

    Hello David Sandor,

    Thanks for the feedback. 

    I am happy to say that we are targeting to add bug support into TeamPulse for Q1 2011. 

    All the best,
    Ryan
    the Telerik team
Back to Top