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

Key: JRA-8023
Type: New Feature New Feature
Status: Open Open
Priority: Major Major
Assignee: Unassigned
Reporter: Nick Minutello
Votes: 0
Watchers: 1
Operations

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

Add Filter criteria for version control entries

Created: 22/Sep/05 09:29 AM   Updated: 25/Sep/05 09:53 PM
Component/s: Filtering & Indexing, CVS integration
Affects Version/s: 3.3.1
Fix Version/s: None

Time Tracking:
Not Specified

Participants: Anton Mazkovoi [Atlassian], Nick Minutello and Scott Farquhar [Atlassian]
Since last comment: 146 weeks, 6 days ago
Labels:


 Description  « Hide
Basically, we want to be able to filter on issues on the basis of their SCM information
a) Have some checkins against them (on given branch(es) and commit date constraints)
b) have no checkins against them

We need to do this to find
a) issue fixes that were not checked into the required branches
b) issues that were checked into the right branches - but the fix version in jira is incorrect or missing



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Scott Farquhar [Atlassian] - 22/Sep/05 01:52 PM
Mate - you could probably do this using the remote APIs of both Fisheye and JIRA?

Go through each JIRA issue, and then query fisheye for commits with that issue key in it?

I think that this is probably the way to go?


Nick Minutello - 23/Sep/05 03:59 AM
Ya, thats possible.
However, it would be much nicer to do it all from within Jira.
How difficult would it be to store some version control info in Lucene?

Anton Mazkovoi [Atlassian] - 25/Sep/05 09:53 PM
> How difficult would it be to store some version control info in Lucene?

SHoudl not be too difficult.

I was thinking of doing this next time we revisit CVS integration.