More Permission Options for Development Tools.

Summary

In JIRA, View Development Tools permission determines which users can view development-related information from integrated applications. Integrated applications here include those listed in JIRA Administration -> Applications -> Integrations:

• Bitbucket Cloud and Github/Github Enterprise - as DVCS Accounts
• Bitbucket Server (formerly Stash), Bamboo, Fisheye/Crucible - as Application Links
• Perforce - Integration to create Perforce jobs from JIRA issues

 Subversion is also included - in the form of the Subversion tab in JIRA issue view

 This means, those users that have View Development Tools permission can view everything, while those without the permission can view nothing. Currently this permission is configurable per project via Permission Scheme.

Use Case

In many cases, for a specific project, an admin would like a user to be able to create Perforce jobs, but not to view Bamboo builds. Similarly another user might see Crucible reviews but not view Github commits. It's not possible to have this flexibility as of now.

Suggestion

It would be great to have one or more permission/s that could restrict access to specific applications only, not all. For example, View Development Tools permission could be split for multiple applications:

• View Development Tools:
  • Bitbucket Cloud
  • Github/Github Enterprise
  • Gitlab/Gitlab self-managed instance
  • Bitbucket Server
  • Bamboo
  • Fisheye
  • Crucible
  • Perforce
  • Subversion

Notes on Perforce

• A user with the permission can create a Perforce job from a JIRA issue and see "Perforce job exists" as the value of the Perforce Job field. A user without the permission, when viewing the same issue, will see the value of the field as "You do not have permission to view the job details".
• On the other hand, when a user without the permission attempts to create a Perforce job from a JIRA issue, the job is indeed not created but the user sees "You do not have permission to view the job details", which confuses him/her. When a user with the permission views the same issue, he/she sees "Perforce job exists", but no job actually exists for the issue.