List of JIRA issues between revisions

zoran_baxshop November 8, 2011

Hello, i was looking for a way in FishEye to get a report of the JIRA issues that where mentioned in commits between revisions. For example, today revision 100 is live. This week some issues are raised in JIRA. Those issues will be fixed and the code is commited. Next week we are at revision 150 and that version is going live. Can i make a report of the JIRA issues that were included in the commit messages between revision 100 and revision 150? (assuming the developers mention the JIRA issue number in their commits)

2 answers

1 accepted

0 votes
Answer accepted
mwatson
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
November 17, 2011

We have just released an unsupported plugin that does exactly what you want, called the Release Report: https://plugins.atlassian.com/plugin/details/772972

zoran_baxshop November 29, 2011

I installed the plugin (had to upgrade to the latest Fisheye version 2.7.6). It does the job. Thank you! Really interested in updates.

0 votes
Felipe Kraemer
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
November 14, 2011

Hi,

I think you could give this FishEye REST API command a try. It'll show a list of changesets from a repository, and you can filter by the repository name and by comment, among other filters.

A usage example is http://localhost:8060/rest-service-fe/changeset-v1/listChangesets?rep=SVN&comment=JRA

Please let us know how it goes...

Cheers,
Felipe Kraemer
Atlassian Support

zoran_baxshop November 15, 2011

Hi there, thanks for your reply.

I can't seem to get an anwser via the REST API.

I changed the url to:

http://fisheye:8060/rest-service-fe/changeset-v1/listChangesets?rep=MY-REP&comment=FOO

Where: My-REP is the name of the repository as defined in FishEye (with a dash '-' in it) and FOO is in multiple of the commit messages for sure. For example "#FOO-3 Fixed some issue" and "FOO-23 Added a new feature"

This is the (empty) result:

<results expand="changesets">
<changesets/>
</results>

The svn repos is accessible via svn://svn, don't know if i should do something with that, because FishEye already knows this (and should know how to authenticate too).

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events