Child issues not visible for one user

[Aswathi D]

Hi ,

Say for eg: Ticket number  Mk-1974 .

This ticket has many child issues as well 

Like MK-1873,MK-1788..etcs 

One user is able to see MK-1974 below that he can't see the child issues ..

However he can see MK-1873 ( which is a child issue ) in a seperate new tab .

Why it is behaving like this ?

[John Funk]

Hi Aswathi,

I would use the permission helper in the permission scheme to determine what the problem is. You can put in the specific issue key and the permission you are checking on. 

[John Funk]

@Aswathi D  - Did you try the permission helper?

[Radek Dostál]

Summing up:

 - The 'Issue Links' webpanel does not appear / is empty

 - A linked issue can be browsed by the user

If the issue can be browsed, this rules out missing permissions.

Are other users having the same problem?

Is User A able to see the Issue Links panel, whereas this user cannot?

Can he see issue links on other issues, or is it just this one?

[Florian Bonniec]

Hi 

When you are talking about "Child issue" is it subtask ?

Otherwise it seems to be a permission issues, as he can see at least one issue from the porject I will bet on security level. Is there any security level configured within the project?

[Aswathi D]

Hi @Radek Dostál ,

Answers to your questions 

1- not so far 

2- yes 

3-no he can't see any of the child issues 

[Radek Dostál]

Going by that others can see the linked issues panel, it's just this person who can't, while at the same time, he can view/browse the issues themselves, leads me to no other conclusion that it's on his end - extensions or whatever .js related error.

To my knowledge there is no user permission condition on the panel, so long as the user can browse >= 1 linked issues, which he can.

I'd probably try to:

 - different browser

 - same browser, but with incognito and disabled extensions

 - impersonate the user if you are able to (scriptrunner has a "log in as user" kind of impersonation, I heard of another plugin having that feature but I don't know any names)

 - check if /rest/api/2/issue/<ISSUEKEY>?fields=issuelinks endpoint returns any issue links for the issue, because if it does the web panel should be visible (thus would confirm a browser problem)

 - check the console/javascript part of web dev. tools if there's anything of interest, it might contain several warnings or other errors that might not be related, but just something that seems interesting/related (if you're not sure what to look for then you could attach the HAR file too, but see the page first because you might want to remove sensitive data from it - https://confluence.atlassian.com/kb/generating-har-files-and-analyzing-web-requests-720420612.html)

 - check {{jira home}}/log/atlassian-jira.log for any errors when he's opening an issue view for any suspicious errors (doubtful)

If it's just that one person it's got to be something on his end. If you're providing accurate information he must have browser permissions to the project and the instance must have correct indexes for issue links, so I can think of nothing else.

[Felipe Gomez]

Hi, I am having the same problem, did you managed to solve your problem.

Thanks!