Cross-project "master backlog"

Thread is closed for posting
2 posts, 1 answers
  1. Matt
    Matt avatar
    9 posts
    Member since:
    Jun 2011

    Posted 10 Feb 2012 Link to this post

    I've read through the blog post here but I don't think this includes what I'm looking for.

    I would like to have the ability to have one "master" backlog, which any created project can pull user stories from.  Is this currently possible and I missed it, or do I have a valid wishlist item?

  2. Answer
    Elena Hristova
    Elena Hristova avatar
    97 posts

    Posted 13 Feb 2012 Link to this post

    Hi Matt,

     We do not support master backlog in the way you want it as we consider each project specific in terms of project template and migrating stories from one project to another may cause validation problems.

     In your case we suggest to create one big project and create hierarchy of iterations to simulate subprojects. something like this:

    • Project
      • Project 1
        • 2012 - Release 1
          • Iteration 1
          • Iteration 2
      • Project 2
        • 2012 - Release 1
        • 2012 - Release 2

     This way you will be able to track each subproject separately - each iteration will show its own burndown; on the story and task board one can select just the iteration for the subproject he is interested in; all the reports can be generated by iteration, so work on separate subprojects will not mix up.

     We will release the cross project view till the end of the week and you will be able to create new hosted trial and try the new xView functionalities.

    All the best,
    Elena Peneva
    the Telerik team
    New Cross Project Perspective in TeamPulse coming soon!
    Want to know how TeamPulse could help you better track all your projects?
    Reserve a seat for the TeamPulse R1 webinar today!
Back to Top