-
Suggestion
-
Resolution: Unresolved
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.
- mentioned in
![[Atlassian Documentation] Page](https://confluence.atlassian.com/images/icons/favicon.png "[Atlassian Documentation] Page"){kind=icon}
[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
| Fix Version/s | New: N/A [ 54414 ] |
| Status | Original: Gathering Interest [ 11772 ] | New: Not Being Considered [ 11776 ] |
| Labels | New: jac-cleanup-phase7 |
| Workflow | Original: JAC Suggestion Workflow [ 3022415 ] | New: JAC Suggestion Workflow 3 [ 3641955 ] |
| Component/s | New: Indexing [ 41890 ] |
| 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. |
| Remote Link | New: This issue links to "Page (Atlassian Documentation)" [ 404643 ] |
| Workflow | Original: Confluence Workflow - Public Facing v4 [ 2948733 ] | New: JAC Suggestion Workflow [ 3022415 ] |
| Workflow | Original: FECRU Development Workflow - Triage [ 1596385 ] | New: Confluence Workflow - Public Facing v4 [ 2948733 ] |
| Status | Original: Open [ 1 ] | New: Gathering Interest [ 11772 ] |
Hi everyone,
We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to resolve it as Not Being Considered.
Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Fisheye&Crucible team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Implementation of New Features Policy for more details.
We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication. Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments.
Kind regards
Marek Parfianowicz
Development Team Lead