As a user, I want FishEye to link the Perforce commit with a linked Job to a JIRA issue, so that I don't have to provide the JIRA issue key on every commit

Problem Definition

As described on the Perforce Jobs in FishEye and JIRA page, when committing a change fixing a Perforce Job, the JIRA issue key has to be provided in the commit message so that the commit is displayed in the JIRA development panel.

Suggested Solution

Since FishEye is aware of the Perforce Job, which has already been linked to the JIRA issue, it would be desirable if the commit was available in the JIRA development panel without having to provide the JIRA issue key.

Workaround

Add the Jira issue key to every commit message/changelist description in Perforce.