|
|
|
Hi Tim, thanks for responding so quickly.
I've run the plugin with debug messages enabled, and the queries being sent to the EyeQL api contain a where clause that looks specifically for comments with <projectkey>[0..N]+ in them. I am absolutely certain that the queries as designed are not doing what you described – they are definitely constraining the results to only revisions which reference the projectkey in the commit log. If you need the specific queries I can get them for you also. Cheers! This has been fixed for version 1.5 with the implementation of
|
|||||||||||||||||||||||||||||||||||||||||||||||||
I replied to your post
on the plugin home page before I realised you'd raised an improvement request:
I'm assuming you're talking about the FishEye Recent Commits portlet due to the message There were no changes on this branch in the last 10 days. This should have the functionality you're talking about..
cheers,
Tim