Everything is possible. It is a matter only of time and resources. Your idea however is not effective. Writing a plugin to support that might consume a lot of work. As a alternative Apache is better for that. You can block then paths based on IP or add another layer of authentication if needed but you would still need to figure out how to block filters or dashboards that get issues indirectly (not by specific path). In other ways you might need to block too much basic features. So overall I think it is not effective to block access to projects by IP. Block JIRA access by IP completely -> OK, but individual projects this is not a good idea. Better idea is to work on OOTB permissions to projects and think about granting access using that.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.