History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: FISH-115
Type: Improvement Improvement
Status: Resolved Resolved
Resolution: Duplicate
Priority: Minor Minor
Assignee: Tim Pettersen
Reporter: Seon Lee
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
JIRA FishEye Plugin

Display changes/revisions that do not reference a JIRA issue or project key.

Created: 14/Dec/07 12:22 PM   Updated: 11/Apr/08 02:22 AM
Component/s: None
Affects Version/s: 1.1.2
Fix Version/s: 1.5

Time Tracking:
Not Specified

Labels:


 Description  « Hide
The message "There were no changes on this branch in the last 10 days." is misleading.

Currently, changeset listings only display revisions that reference a JIRA issue. Our repository is several years old now and we recently began evaluating/using JIRA.

Can we have an option to display all revisions, regardless of the presence of a project key in the commit log?



 All   Comments   Work Log   Change History   FishEye   Crucible   Related Builds      Sort Order: Ascending order - Click to sort in descending order
Tim Pettersen - 14/Dec/07 08:38 PM
Hi Seon,

I replied to your post on the plugin home page before I realised you'd raised an improvement request:

The FishEye Recent Commits portlet should display all changesets under a particular branch, not just those containing issue or project keys in their comments.

If they're not showing it may be a result of an invalid configuration. Can you double-check that you've specified the correct FishEye branch and repository on the Edit Portlet screen?

If your config appears fine but it's still not showing recent commits, please raise a support request at http://support.atlassian.com under the FishEye project and we'll help you out.

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


Seon Lee - 14/Dec/07 09:49 PM
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!


Tim Pettersen - 11/Apr/08 02:22 AM
This has been fixed for version 1.5 with the implementation of FISH-153