title: JIRA: Epic issue that can last for multiple versions and "Affect versions"&"Fix versions" fields
body: <p>I have a project.
  It is a web-site.
  The project has just started.
  I found reasonable to group all design-related stories into one Epic called "Design"...</p>
  
  <p><strong>BUT</strong></p>
  
  <p>...At the moment I started to fill "Design" epic JIRA card I caught myself at being not sure how to proper handle the epic over versions (especially looking on "Affect versions"&amp;"Fix versions" fields).</p>
  
  <p>The problem is:</p>
  
  <ul>
  <li>from one side this epic could be strictly planned in version 1.0 and finished in this version. In this case the epic should contain only design tasks for version 1.0. The question: how to organize design stories that are beyond version 1.0?? With this approach I cannot put them into this epic. So, where?</li>
  <li>from other side I can place all design specific stories (despite versioning, 'cause some of them are planned to 1.0 release, others are known but planned to further releases) into the same epic. But in this case how to fill "Affect versions" &amp; "Fix versions" fields? How to organize stories inside this long lasting epic?</li>
  </ul>
  
  <p>Personally I feel that the latter option is better but I would like to listen for your thoughts.</p>