title: How to track 'Implementer' in Jira (vs. Assignee)
body: <p>Our JIRA workflow for development issues goes something like this:</p>
  
  <pre><code>New -&gt; In-Progress -&gt; Resolved -!-&gt; Reviewed -&gt; Closed/Released
  </code></pre>
  
  <p>This is simplified, but should get the point across.</p>
  
  <p>The Jira Assignee for New/In-Progress is simple: It may start out being assigned to anyone, but as soon as it's in-progress the <em>developer</em> that codifies the issues is the Assignee.</p>
  
  <p>When the developer <em>is done</em> he will check-in and set the issue to <code>Resolved</code>.</p>
  
  <p>Now my "problem"(*) starts: Since the developer <em>should not</em> review the issue himself, the issue should be assigned to someone else for review. The reviewer can then approve it and set it to <code>Reviewed</code>, after which it is ready to be included in a release. (details on how that works not relevant here)</p>
  
  <p>The issue then ends up with the Assignee set to the reviewer, where the relevant person for the issue is actually the original developer.</p>
  
  <p>I mean: When looking at Jira issues, I'm mostly interested in the <strong>Implementer</strong>, not the person that approved the change afterwards.</p>
  
  <p>So the question(s) seems to be:</p>
  
  <ul>
  <li>Jira Assignee seems to be <em>thought to</em> change through the transitions of issues.</li>
  <li>The Assignee may then well end up with a only secondary relevant person when the issue is finally closed. <em>This makes filtering on closed issues harder.</em></li>
  <li>Is this a real problem, and what solutions are there for this?</li>
  </ul>
  
  <p>I guess one could add additional fields, but the fact that the defaults only have these two People should hint at something?</p>