A maximalist request from a user could be phrased as: Do complete refresh of all queries of a repository after any change done by the user to an issue in the IDE, in order to keep the Tasks view always up-to-date with the activities done in the IDE (leaving the periodic autorefresh only for syncing with external changes). That would be nice from user point of view, but such a refresh can be quite costly. We probably don't want to do it this way.

But perhaps there are some specific operations and situations that would deserve such an automatic refresh. The main candidate is creating a new issue in a team project, and possibly also closing it.

Creating a new issue is not done very often and overall it is an operation that takes some time to the user (so additional time for the refresh is much smaller and not looking inappropriate, and it would not be happening frequently either). But mainly, in the team projects with the predefined queries like All Tasks and Open Tasks, it looks strange when a new issue is created and it does not appear anywhere. The user is surprised and most likely will look for a refresh anyway (wants to see the issue is there). I'm mentioning team project because I'd say this is not perceived as such a problem for standalone repositories with custom queries (the need for a refresh seems less surprising as the user is more aware of the queries).

So I would suggest on issue creation to refresh all queries of the team project repository that have autorefresh on (i.e. not turned off). Same on issue closing (and reopening, i.e. changing status) would also be nice.