Uploaded image for project: 'FishEye'
  1. FishEye
  2. FE-6657

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

XMLWordPrintable

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      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.

            [FE-6657] 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

            No work has yet been logged on this issue.

              Unassigned Unassigned
              ccurti Caterina Curti
              Votes:
              4 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated: