I don't think you can easily restrict view access to specific metadata columns.
Short Answer: Use a Page with embedded library web-parts, custom views and Audience Targeting.
For Forms: Use the same principle (audience targeting) to provide links for custom forms.
Instead of accessing the library directly (I would make the 'Issue Status' column hidden in the default view), the users can access the page with the library embedded instead. You could then either make different pages based on group (with different permissions for each page, or use Audience Targeting (which I recommend, but I can't confirm that it will work with the modern UI).
Essentially, create a New Page and embed the library in a webpart twice. Then set webpart 1 to the 'Owners' view, and set the audience targeting (in the webpart settings) to only display to owners, then for webpart 2 set the view to 'Users' and change the audience targeting settings to users only.
Only the library which is targeting them should be displayed with it's respective view (so one library will be hidden at a time).
You can repeat this process with embedded hyperlinks as webparts which will link to custom forms, but I think custom forms is a more complex subject than I should explain here, so I'll just link to reference.