You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
I had compatibility problems with another plugin that also worked on queries. So I made some changes to your patch by renaming : initialize_available_filters to initialize_available_filters_with_gtt, available_columns to available_columns_with_gtt and issue to issue_with_gtt.
Inside issue_query_patch.rb
At first glance, this doesn't affect the gtt plugin. Perhaps this small change would solve the problem #151, #252 or others.
Thanks for updating to v5.1.0 👍
The text was updated successfully, but these errors were encountered:
Apologies for the delay! It turns out that the conflicting plugin is the paid redmine_db plugin from AlphaNode. This plugin introduces entities similar to those in the redmine_supply plugin, and they both use the output filter tool on their entities. I initially tried modifying their plugin, but unfortunately, it didn’t work. However, when I applied the same changes to the redmine_gtt plugin, there was no conflict this time.
Hello,
I had compatibility problems with another plugin that also worked on queries. So I made some changes to your patch by renaming :
initialize_available_filters
toinitialize_available_filters_with_gtt
,available_columns
toavailable_columns_with_gtt
andissue
toissue_with_gtt
.Inside issue_query_patch.rb
At first glance, this doesn't affect the gtt plugin. Perhaps this small change would solve the problem #151, #252 or others.
The text was updated successfully, but these errors were encountered: