Hiding some ticket-types from client & client facing boards

Question

Hi all,

We are looking into redefining how we are using Jira internally & how we share it with our clients.

The 'wishlist' we put together is quite an odd and complicated one, not sure at what level is achievable.

In a software development project, we would like to have the followings:

* one board for the developers, with all the tickets (Epic, Story, Bug, etc)
* the client should have a separate board, where they can track features & should not have access to the developer's board or see any ticket of it. The clients should be able to add bugs& track them

Thank you in advance.

Best regards,
Botond György

Trudy P Claspill · Answer

Hello @Botond Gyorgy

I see you made a new Question for your last questions about permissions, and already have answers there.

https://community.atlassian.com/t5/Jira-Software-questions/Limit-user-permission-to-ticket-creation-and-commenting/qaq-p/2251354

Botond Gyorgy · Answer

Hi @Trudy P Claspill

Thank you for your answer.

Re this part: "Additionally, you would set up your client users in a User Group or Role that you could use in the project's Permission Scheme to give them the Browse Projects permission and the Create Issues permission, which would enable them to look at issues in the project (the ones they are permitted to see per the assigned Issue Security Level) and create issues."

Is it possible to restrict user/user group permissions to:

* allow ticket creation
* view-only permission to the board - so they should not be able to move tickets across the board, 
* should be able to add comments & tag people

Best regards,
Botond György

Trudy P Claspill · Answer

Hello @Botond Gyorgy

If you are using the Jira Software product only, be advised that you will have to grant licenses to your client users to enable them to interact with the system to see and create issues.

If your issues are in a Company Managed project then you can use Issue Security to define Issue Security Levels that specify who can see each issue. You assign and Issue Security Level to each issue. You would have an Issue Security Level that says "this issue is viewable by all users", and a level that says "this issue is viewable only by non-client users".

With that in place you could use one board for both your client and non-client users. When viewed by client users, they would see only the issues they are permitted to see.

Additionally, you would set up your client users in a User Group or Role that you could use in the project's Permission Scheme to give them the Browse Projects permission and the Create Issues permission, which would enable them to look at issues in the project (the ones they are permitted to see per the assigned Issue Security Level) and create issues.

There is not a feature specifically for limiting the types of issues a user can create. The workaround is to add a Validator to the Create transition to say if the Reporter has to be in a specified group or role to complete creation of the issue. If they are not in that group/role the issue will not be saved. You would have to have a separate workflow for your Bug issue type vs. your other issue types to make that distinction.

If you don't want to grant product licenses to your client users, then you could look at adding the Jira Service Management product to your environment. With that, you client users would submit their Bugs through a customer service portal. You could automatically create comparable issues in the Jira Software project used internally, link it to the issue submitted by the client, and keep the information between the two synchronized. Clients accessing Jira Service Management portals do not consume licenses. But, they also cannot interact with your Software project directly nor view agile boards, dashboards, etc.