Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,368,846
Community Members
 
Community Events
168
Community Groups

Sub-Task not viewable by Customer ?!

Hi, I have created a Sub-Task but when the user tries to access it, its not viewable by the user. Instead he seem the below image.
Capture.JPG
What could be the issue ?
When in a normal ticket, the same user is able to see the ticket, only the subtask ticket he is unable to see.
Thank You

1 answer

1 accepted

0 votes
Answer accepted

Sub tasks are not visible on JSM portals for customers. They are meant for Agents to break down and individually assign parts of the request amongst each other.

If you want to create a linked issue to the original I suggest that you use "create a linked issue" and ensure that the issue you create is of another issue type than subtask plus that it has a request type configured. 

In Jira software project it's another ball game. There everyone that has browse permissions to the project have permissions to everything - all types of issues. (if there is no issue security scheme in place).

Sorry for the bad news, but I hope it helped a little anyway

 

/L

I'm going through the Issue Security Scheme.

In the mean time I have created a new Role, and added the customer to that Role. Now when I share 1 ticket with the customer, he is able to see all tickets in the Project, whether they are shared with him or not.

How can I disallow him from seeing all tickets and instead only see the ticket shared with him ?

Or is this related to Issue Security Scheme too ?

Hi,

Given the classification in your community post you are on Cloud and the issue is about Jira Service Management. 

In JSM  the role "customer" does not cost a license, and people invited to portals as customers should ONLY see the portal view and only see their own Requests (or request specifically shared with them). 

In JSM the role "agent" cost a JSM license and they are allowed to work with requests in Jira and have full access to the project, its issues, all types of issues etc.

  • Firstly control who you give "product access" to - ie who is an agent in your site. It might be that you have invited your customer to become an agent. This will cost you and also totally bypass the whole idea of the customer vs agent collaboration via a JSM portal
  • Then control the user accounts connected to what role in the specific project (if customer is anything else than role customer then you risk to display more than intended). Check the "People" list under project config. 
  • Then control the permission scheme of the specific project. What permissions is given the different roles? If the customer has multiple roles they might have more permission than you intend. Check the permission scheme under project config.

You should really keep the roles to a minimum in Jira.

Good documentation for understanding users, roles, permissions is found here: https://support.atlassian.com/jira-cloud-administration/docs/manage-users-groups-permissions-and-roles-in-jira-cloud/

Thank You Lisa, appreciate the clarification.

Like Lisa Förstberg _Riada_ likes this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS

Atlassian Community Events