Working with external users

Paweł Czartoryski

Hi,

I am starting with Atlassian and Jira products (we are small software house team). So far I am using bitbucket and starting with Jira cloud. I have not found satisfactory answers so maybe someone can help me.

1. I would like to enable some of the issues to be public for reading and voting to clients who doesn't have any atlassian account (and are not willing to create). Is this possible? Do I need Jira Service Desk for that?
2. I would like to add access for some external partners (from other company) to work on e.g. 'mobileApp' component issues , but they shouldn't see issues from other components - is this possible? Or should I create multiple dashboards/projects for that? What is best aproach to achieve this?
3. We are working on multiple projects and multiple clients - can I set ClientA to see only ProjectA, ClientB to see only ProjectB, etc ?
4. I can't find a simple report with sum of working hours on issues (monthly by employee)

Thanks in advance for your help!

Joe Pitt

The first thing I suggest you do is fix the default permission scheme. 

JIRA works by GRANTING access. You can't restrict access. By default, it grants access to the group used to logon (used to be JIRA-users but may be different on your version).

1. The FIRST thing you need to do to get control is to remove any groups with logon privileges from the permission scheme unless you absolutely want everyone to have that permission.
2. Then I suggest you setup Project Roles for the various functions like, tester, QA, Browse Only, etc.
3. One permission scheme will cover almost all projects. The project admin controls project role membership

1. For voting users will need an account. The only way to control issue access is by applying an Issue Security Scheme. Depending on how many variations you need it may be unmanageable. I haven't used service desk so I can't speak to that.

2. Components are in the project so if they can create an issue they can select any component. Again, look to issue security schemes to restrict issue access. Creating dashboards would be a work around, however they can still directly see the project. 

3. Controlling access to projects is covered in my suggestion to fix the default permission scheme. 

4. I haven't been at a site that used the work log. In my experience the hours aren't reliably entered or consistent.