-
Suggestion
-
Resolution: Won't Do
-
None
-
1
-
NOTE: This suggestion is for JIRA Software Server. Using JIRA Software Cloud? See the corresponding suggestion.
Hi,
Recently, during a release procedure, I came across behaviour that seems erroneous. Here's what I did, as far as I can remember:
1. I had 3 issues with 3 BitBucket pull requests associated with them, visible through the Development panel on the Issue page.
2. I accepted the pull requests into the develop branch. The Version page showed no warnings, as no issue was under review any longer.
3. I created another pull request to merge develop into master. BitBucket detected the issues as being associated with the pull request.
4. The Version page showed 3 warnings, saying that there are unmerged pull requests.
At this point, hovering over "Under Review" for each issue on the Version page showed a popup stating that there is 1 pull request. Clicking "Under Review" reveals 2 pull requests, one of which is the original pull request for the issue, and the other one is the one from develop into master. On the Issue page for any of the 3 issues, similar behaviour could be observed: the "Development" panel shows 1 pull request with status "Open". Clicking it reveals 2 pull requests, one of which is the develop -> master pull request with status "Open" and the other one is the original issue pull request with status "Merged".
- is related to
-
JSWSERVER-15493 Inconsistent numbers of Pull Requests popping up from Development Panel
-
- Gathering Impact
-
- relates to
-
- Closed
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSWSERVER-14942] Pull requests wrongly associated with issues
| Workflow | Original: JAC Suggestion Workflow [ 3070010 ] | New: JAC Suggestion Workflow 3 [ 3662702 ] |
| Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
| Workflow | Original: Confluence Workflow - Public Facing v4 [ 2625656 ] | New: JAC Suggestion Workflow [ 3070010 ] |
| Resolution | New: Won't Do [ 10000 ] | |
| Status | Original: Gathering Interest [ 11772 ] | New: Resolved [ 5 ] |
| Support reference count | New: 1 |
| Workflow | Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2327467 ] | New: Confluence Workflow - Public Facing v4 [ 2625656 ] |
| Status | Original: Open [ 1 ] | New: Gathering Interest [ 11772 ] |
| Workflow | Original: JIRA PM Feature Request Workflow v2 [ 2044305 ] | New: JIRA PM Feature Request Workflow v2 - TEMP [ 2327467 ] |
| Workflow | Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2032508 ] | New: JIRA PM Feature Request Workflow v2 [ 2044305 ] |
| Workflow | Original: JIRA PM Feature Request Workflow v2 [ 1599799 ] | New: JIRA PM Feature Request Workflow v2 - TEMP [ 2032508 ] |
| Description |
Original:
Hi,
Recently, during a release procedure, I came across behaviour that seems erroneous. Here's what I did, as far as I can remember: 1. I had 3 issues with 3 BitBucket pull requests associated with them, visible through the Development panel on the Issue page. 2. I accepted the pull requests into the {{develop}} branch. The Version page showed no warnings, as no issue was under review any longer. 3. I created another pull request to merge {{develop}} into {{master}}. BitBucket detected the issues as being associated with the pull request. 4. The Version page showed 3 warnings, saying that there are unmerged pull requests. At this point, hovering over "Under Review" for each issue on the Version page showed a popup stating that there is 1 pull request. Clicking "Under Review" reveals 2 pull requests, one of which is the original pull request for the issue, and the other one is the one from {{develop}} into {{master}}. On the Issue page for any of the 3 issues, similar behaviour could be observed: the "Development" panel shows 1 pull request with status "Open". Clicking it reveals 2 pull requests, one of which is the {{develop -> master}} pull request with status "Open" and the other one is the original issue pull request with status "Merged". |
New:
{panel:bgColor=#e7f4fa} *NOTE:* This suggestion is for *JIRA Software Server*. Using *JIRA Software Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JSWCLOUD-14942]. {panel} Hi, Recently, during a release procedure, I came across behaviour that seems erroneous. Here's what I did, as far as I can remember: 1. I had 3 issues with 3 BitBucket pull requests associated with them, visible through the Development panel on the Issue page. 2. I accepted the pull requests into the {{develop}} branch. The Version page showed no warnings, as no issue was under review any longer. 3. I created another pull request to merge {{develop}} into {{master}}. BitBucket detected the issues as being associated with the pull request. 4. The Version page showed 3 warnings, saying that there are unmerged pull requests. At this point, hovering over "Under Review" for each issue on the Version page showed a popup stating that there is 1 pull request. Clicking "Under Review" reveals 2 pull requests, one of which is the original pull request for the issue, and the other one is the one from {{develop}} into {{master}}. On the Issue page for any of the 3 issues, similar behaviour could be observed: the "Development" panel shows 1 pull request with status "Open". Clicking it reveals 2 pull requests, one of which is the {{develop -> master}} pull request with status "Open" and the other one is the original issue pull request with status "Merged". |
Hi,
Thank you for raising this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request now. Sometimes potentially valuable tickets do get closed where the Summary or Description has not caught the attention of the community. If you feel that this suggestion is valuable, consider describing in more detail or outlining how this request will help you achieve your goals. We may then be able to provide better guidance.
For more context, check out our Community blog on our renewed approach to highly voted Server suggestions for Jira and Confluence.
Thanks again.
Regards,
Jira Product Management