I would like advice on whether a disabled button is better than no button for a certain UI.
Basically, the regular (experienced) users can either comment on an issue or close it; the users with restricted access (such as inexperienced developers) can only comment on the issue.
In this case, there's no way to edit the access restriction directly inside the app, as it fetches information from a separate service. And it is very unlikely that the restricted user will be granted access to the action by simply inquiring it.
Is it worth it to display a disabled button even though the user cannot press it or do anything to enable it, or is it kinder to him/her to just not show the "Close" button at all?
PS There's also a chance that they're using the app with a different team where they do have an access to the "Close" action. In that case, I'm afraid hiding the button altogether when they don't have rights might confuse them when they navigate from one team to another.