title: Best practice for creating a "Roadmap" in Jira
body: <p>We want to implement a solid "road map" for our product development road map.  We use Jira (4.4.3) and Greenhopper for our project management and bug tracking but the Jira Roadmap feature simply shows you a list of the versions you have defined.</p>
  
  <p>However, we currently use our <strong>"Versions"</strong> for each sprint, e.g. "Week 16", "Week 17", etc. which contain all of the tasks/issues for that week's sprint.</p>
  
  <p><img src="https://i.stack.imgur.com/mSkiw.png" alt="Versions Screenshot"></p>
  
  <p>We currently use <strong>"Components"</strong> to keep track of major feature sets and to categorize (e.g. "Integrate with xyz API", "Migrate emails to SendGrid", "Bugs: Code", or "Technical Debt").</p>
  
  <p><img src="https://i.stack.imgur.com/Ar3yQ.png" alt="Components Screenshot"></p>
  
  <p>The Jira <strong>"Roadmap"</strong> feature shows the list of versions and the progress towards each.  However, we're already using Versions for tracking our weekly sprints, and some of these roadmap features will span many releases/versions/sprints.</p>
  
  <p><img src="https://i.stack.imgur.com/z6m1t.png" alt="Roadmap Screenshot"></p>
  
  <p>How can we keep track of our complete roadmap within Jira?  We would really like to see a list of our major initiatives in this roadmap instead of a list of all of our weekly sprints (e.g. "Enable Selenium on CI server", "Extranet MVC3 conversion", "Upgrade production to R2").</p>