Issues in this epic is not visible for other user accounts (epic issue type)

[Vishnu Chinnaraj]

Issues in this epic is not visible for other user accounts (epic issue type)

[Andy Heinzer]

I would not expect a Jira Core or Jira Service Desk only user to be able to see the issues in an epic.  Since Epic issue type are special to Jira Software functionality, in order to fully utilize that issue type each user has to be a Jira Software licensed user.

Otherwise they can at least see that the issue exists, but they don't have any of the Jira Software features if they are not a licensed user.

Does this explain your situation?  I am interested to learn if there is some other condition where a Jira Software users would be unable to see these issues when they have the permissions to do so.

[Marcos Rivoira]

Hi Andy, can I give you another point of view? 

Since you can use an Epic as a super task, and maybe the person responsible for that task is any pepple that does not have a software license, that person should be able to see the incidents within that epic as you see the subtasks within a task.

We have a license for 100 users of Jira Core and 50 user licenses of Jira Software, and we have many people responsible for those supertasks (epic) that do not use any Agile functionality, and they have to apply a solution that is not comfortable to see how it is composed that epic.

Maybe you can add a special permission to see that links? 

[Andy Heinzer]

Hi Marcos,

Thanks for sharing your point of view here on Community.  I do appreciate that different users will see this differently.  However I do not see how this could be feasibly accomplished within the Jira Core product itself. The full functionality of epics is expected to be leveraged against sprints and agile boards: both of which are also features that require the user to have a Jira Software license. 

I realize that you are perhaps only looking to see the child issues of this epic.  But in order for your users that might be assigned to an epic to get the most out of that issue type, these users really are expected to be licensed Jira Software users.  So to assign that issue to them would be very limiting since they can't leverage the features that epics provide.  While Jira will let you do this, it might be a good tactic to change the permission scheme where epics are located.

While I don't think that this would make a good feature request, you could create this as an issue type suggestion on our public tracker https://jira.atlassian.com/issues/.  In this case, I believe this suggestion would fall under either the JRASERVER project for Jira Core Server, or the JRACLOUD project for Jira Core Cloud depending on your platform.

Instead of creating a new feature request, I would instead look to prevent Jira Core users from being assigned these Epics as a means to avoid this problem for Jira Core users.  If you were to put all the epics into their own project, you could then create a new permission scheme just for that project.   Once you do that you can then switch the assignable user permission away from "Any logged-in user" to only be granted to the application access role of Jira Software users.  This way, no one could assign epics in that project to Jira Core users. This is one way that Jira could prevent users from assigning epics to users that can't truly utilize those issues types to their fullest.

Sorry this may not be the solution you are looking for.  However I don't believe that it will be feasible to grant your request to Jira Core users.  The alternative that I would suggest would be to adjust the licensing of these users that need to utilize Epics to be Jira Software users.

Andy