Authorization and Subversion Plus

[Deleted user]

We want to use Subversion Plus on our production JIRA systems, but see currently the following deficit:

1. You are the user XYZ and don't have access to the Subversion repository ABC, but you have access to the JIRA project ABC, where the Subversion repository ABC is configured for Subversion Plus.
2. You go to `Project ABC > Subversion` tab and see there all commits on the Subversion repository ABC which contain in their commit message any Issue-ID from JIRA.
3. You see there the revision number (including link), the commit message and all paths of changes in the revision.
4. When you now click on any item, you will be delegated to the login-screen for the repository, where all repository IDs are listed.

We have the following problems here:

• Some of our users (for example customers) should have access to (some issues in) JIRA (by using issue security), but not to all.
• These users should not get any information from our CM system.
• They even should not know which repositories are used in our company.

Do you see any chance to address these topcis in the future? Or is that a configuration we did miss here?

[Pablo Beltran · Accepted solution]

Only users granted with the VIEW_DEVELOPMENT_TOOLS persmission (renamed to VIEW_ISSUE_SOURCE_TAB or VIEW_VERSION_CONTROL depending on your JIRA version) should see Subversion ALM.

By removing that privilege, Subversion ALM should be totally hidden for those users. They should not view neither the Subversion menu, the Issue and Project tabs, nor run any JQL function against Subversion.

[Deleted user]

Thank's a lot, that helps at least to divide between the developers (where it not so critical) and the rest of the crowd. Will see if that is sufficient for our team.