Search, Linking, and Issue List not working - Githubissues

nanego / redmine_multiprojects_issue

A Redmine plugin which allows you to specify several projects per issue

http://www.redmine.org/plugins/redmine_multiprojects_issue

MIT License

57 stars 29 forks source link

Search, Linking, and Issue List not working #54

Closed mjungowski closed 1 year ago

mjungowski commented 2 years ago

After our recent update from Redmine 4.0.9 to Redmine 4.2.2 I am seeing a weird issue with the latest version of this plugin (master-branch cloned in August and again today). I can use the plugin just fine and assign additional projects to issues perfectly fine. Users, that are members of one of the projects selected can then open the issue directly via URL, however:

The issue does not show up if they search for its ticket number
The issue does not show up in the secondary project's issue overview
The issue is not highlighted as clickable in-text link anymore

The logs don't show anything unusual or any errors, and I cannot really put my finger on it.

nanego commented 2 years ago

Hello I tried, but couldn't reproduce the errors. We are using the latest version of the plugin in production, issues are listed in secondary project's issues page. Can you be more specific on how to recreate these problems? Are you using other plugins? If any, did you try without them?

mjungowski commented 2 years ago

Thank you for checking and verifying, @nanego. Yes, we use variety of plugins in addition to multiprojects_issue, both free and commercial. I will try to narrow this down today by disabling all plugins, and then reenabling them one by one to find the culprit.

mjungowski commented 2 years ago

I have tried with all plugins except for multiproject, deface, and stimulusjs removed and am still seeing the same behavior. And yes, I did perform a full database migration (bundle exec rake redmine:plugins:migrate NAME=plugin_name VERSION=0 RAILS_ENV=production) prior to removing the plugins.

While trying to trace back the steps I did, however, identify the culprit. I realized that it worked as expected when using the admin user but did not work when using regular non-admin users. And lo and behold there is a new permission under roles named "View multi-projects issues" that wasn't there before we updated. We were running a much older version of multiprojects_issue before so that might have been the only problem here.

This non-issue is therefore resolved and can be marked as layer 8 problem. @nanego, thank you very much for your quick response.