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

            Marek Parfianowicz made changes -
            Fix Version/s New: N/A [ 54414 ]
            Marek Parfianowicz made changes -
            Status Original: Gathering Interest [ 11772 ] New: Not Being Considered [ 11776 ]
            Marek Parfianowicz made changes -
            Labels New: jac-cleanup-phase7
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3022415 ] New: JAC Suggestion Workflow 3 [ 3641955 ]
            Marek Parfianowicz made changes -
            Component/s New: Indexing [ 41890 ]
            Caterina Curti made changes -
            Description Original: h3. Problem Definition
            As described on the [Perforce Jobs in FishEye and JIRA|https://confluence.atlassian.com/display/FISHKB/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.

            h3. 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.             		New: h3. Problem Definition
            As described on the [Perforce Jobs in FishEye and JIRA|https://confluence.atlassian.com/display/FISHKB/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.

            h3. 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.


            h3. Workaround
            Add the Jira issue key to every commit message/changelist description in Perforce.
            Caterina Curti made changes -
            Remote Link New: This issue links to "Page (Atlassian Documentation)" [ 404643 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2948733 ] New: JAC Suggestion Workflow [ 3022415 ]
            Owen made changes -
            Workflow Original: FECRU Development Workflow - Triage [ 1596385 ] New: Confluence Workflow - Public Facing v4 [ 2948733 ]
            Status Original: Open [ 1 ] New: Gathering Interest [ 11772 ]
            Owen made changes -
            Issue Type Original: Improvement [ 4 ] New: Suggestion [ 10000 ]

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

                Created:
                Updated: