Story ID not visible and Ticket deeplink

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

    Posted 26 Apr 2010 Link to this post

    Note: I am not yet testing the link with TFS but TeamPulse claims to be also independent from TFS so I think this applies even if TFS is not used.

    When talking to my team it's very common that we use the Ticket# (or StoryID) to refer to an atomic work Item.
    Maybe i am missing something but this information is not shown in any of the Views.

    Furthermore it's very common to use an URL to discuss a specific item wiht another team member.

    TeamPulse exposes an URL with the Ticket ID but trying to paste it raises the following error:

    Exception Type: System.NullReferenceException
    Exception Message: Object reference not set to an instance of an object.
       at Titan.Client.Presentation.Stories.EditStoryPresenterModel.LoadRefData()
       at Titan.Client.Presentation.Stories.EditStoryPresenterModel.Activate(NavigationContext navigationContext)
       at Titan.Client.Presentation.View.Activate(NavigationContext navigationContext)
       at Titan.Client.Presentation.Page.Page_Loaded(Object sender, RoutedEventArgs e)
       at MS.Internal.CoreInvokeHandler.InvokeEventHandler(Int32 typeIndex, Delegate handlerDelegate, Object sender, Object args)
       at MS.Internal.JoltHelper.FireEvent(IntPtr unmanagedObj, IntPtr unmanagedObjArgs, Int32 argsTypeIndex, String eventName)

    Trick: if the TeamPulse user is alreadly logged-in (session) and the project is open then it works. So it looks like the Deeplink concept is not yet fully implemented. By knowing the ticketID should (IMHO) open that specific project automatically.

    Is this the direction you are going with the product? Will integrating with TFS help in any aspect? 

  2. Ryan
    Ryan avatar
    164 posts

    Posted 26 Apr 2010 Link to this post

    Hello Sebastian Talamoni,

    Both of these features (Displaying StoryID, and deeplinking by ID) are scheduled to be implemented before the next release. I cannot guarantee they will make it in, but they are very much on the radar. We also plan to display the related TFS WorkItemID of a story if it has been synced.

    Thanks for helping confirm the necessity of these features.

    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.
Back to Top