title: Setting up access control in Hudson for Jenkins Plugin for JIRA
body: <p>I am currently testing <a href="https://marvelution.atlassian.net/wiki/display/JJI/Documentation+Home" rel="nofollow noreferrer">Jenkins Plugin for JIRA</a> as an alternative to <a href="http://www.atlassian.com/software/bamboo/overview" rel="nofollow noreferrer">Atlassians Bamboo</a> Continuous Integration tool for projects that I am working with. After reading documentation and creating some test project I managed to "connect" my Jira instance and my Hudson instance together. This is what I wanted to achieve initially (sequence diagram):</p>
  
  <p><img src="https://i.stack.imgur.com/cROu8.jpg" alt="jira-hudson-svn-integration"></p>
  
  <p>Main use case:</p>
  
  <ol>
  <li>User creates an issue in JIRA (ex. TST-1)</li>
  <li>User resolves it after making some changes to the code. (Resolution: Delegate issue to Hudson CI)</li>
  <li>User commits changes to Subversion (Commit message must contain issue code: TST-1 and 'Autobuild' (optional))</li>
  <li>Build is triggered inside Hudson environment if 'Autobuild' string is found in the commit message</li>
  <li>Hudson updates its copy of the project</li>
  <li>Hudson build the project</li>
  <li>Hudson updates corresponding issues (TST-1) on JIRA and resolves them leaving comment: 'Resolved by Hudson'</li>
  </ol>
  
  <hr>
  
  <p><strong>The actual problem:</strong></p>
  
  <p>If I set access control in Hudson instance to 'Logged-in users can do anything', I can 'connect' my Jira instance with Hudson instance. (I mean that inside Jira in Jenkins Configuration i can see # of Last Builds) But in case if I use 'Matrix-based security' or 'Project-based Matrix Authorization Strategy' access control in Hudson, then I am not able to see # of Last Builds.</p>
  
  <p>More of the problem in screenshots:</p>
  
  <p><strong>'Matrix-based security' Access Control:</strong></p>
  
  <p><img src="https://i.stack.imgur.com/AATBo.png" alt="Hudson access control settings"></p>
  
  <p><img src="https://i.stack.imgur.com/nLU3B.png" alt="Hudson build history"></p>
  
  <p><img src="https://i.stack.imgur.com/pMSxE.png" alt="Jira # of builds"></p>
  
  <p><strong>'Logged-in users can do anything' Access Control:</strong></p>
  
  <p><img src="https://i.stack.imgur.com/XYOyS.png" alt="Jira # of builds"></p>
  
  <hr>
  
  <p>I have tried to install <a href="http://wiki.hudson-ci.org/display/HUDSON/Role+Strategy+Plugin" rel="nofollow noreferrer">Role-based Authorization Strategy</a> plugin and made two groups: Admin and Anonymous (allowing everything for Admin user and nothing for anonymous), but the effect is the same - not able to see # of Last Builds in Jira instance</p>
  
  <p>After every update in Hudson Security, i restart hudson and remove/add application links again from the beginning (just in case..)</p>
  
  <p>Did anyone had similar problems while configuring this plugin? If so, how did you manage to resolve this issue?</p>
  
  <hr>
  
  <p><strong>P.S.</strong></p>
  
  <p>I do not want to use <code>Logged-in users can do anything</code> access control setting, because in this mode Anonymous users will be able to get a lot of sensitive information just by browsing through my Hudson instance</p>
  
  <p><s>While writing this question, I changed from version <code>1.1.2</code> to <code>1.0.1</code> because <code>v.1.0.1</code> seems to be working better for me.</s> Using version <code>1.1.4</code> <a href="https://marvelution.atlassian.net/wiki/display/JJI/Release+Notes" rel="nofollow noreferrer">(versions list)</a>.</p>
  
  <p>Registered issue on marvelution: <a href="https://marvelution.atlassian.net/browse/JJI-41" rel="nofollow noreferrer">https://marvelution.atlassian.net/browse/JJI-41</a></p>
  
  <p><strong>UPDATE:</strong></p>
  
  <h2>The new release `1.2.0` fixed this issue.</h2>
  
  <p>What caused the problem: </p>
  
  <blockquote>
    <p><a href="https://marvelution.atlassian.net/browse/JJI-47?focusedCommentId=15340&amp;page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15340" rel="nofollow noreferrer">when the schedular was triggered the basic header was not added</a></p>
  </blockquote>