-
Suggestion
-
Resolution: Unresolved
-
None
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
When releasing a JIRA version, I would like to be able to specify which revision of the source code should be used. The feature is present in Bamboo[1], but not exposed in Jira.
My use case is simply that we tag our releases in git, and I would like to specify this tag (same as I can with the customized build feature in Bamboo) to be the revision to build the release from.
See attached image for the dialog as it currently exist. A field could be added here where it could be possible to specify revision.
There are also some questions on Atlassian Answers asking for this feature or similar[2][3]
[1]: https://jira.atlassian.com/browse/BAM-1640
[2]: https://answers.atlassian.com/questions/11161/specifying-the-source-code-revision-to-build
[3]: https://answers.atlassian.com/questions/15696940/jira-build-release-needs-a-field-revision
- relates to
-
- Closed
[JRASERVER-43648] Specify source revision to build release from
| Workflow | Original: JAC Suggestion Workflow [ 3057014 ] | New: JAC Suggestion Workflow 3 [ 3692829 ] |
| Workflow | Original: Confluence Workflow - Public Facing v4 [ 2603209 ] | New: JAC Suggestion Workflow [ 3057014 ] |
| Workflow | Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2552201 ] | New: Confluence Workflow - Public Facing v4 [ 2603209 ] |
| Status | Original: Open [ 1 ] | New: Gathering Interest [ 11772 ] |
| Workflow | Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2336905 ] | New: JIRA PM Feature Request Workflow v2 - TEMP [ 2552201 ] |
| Workflow | Original: JIRA Bug Workflow w Kanban v6 [ 2128325 ] | New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2336905 ] |
| Workflow | Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2091123 ] | New: JIRA Bug Workflow w Kanban v6 [ 2128325 ] |
| Workflow | Original: JIRA Bug Workflow w Kanban v6 [ 892892 ] | New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2091123 ] |
| Description |
Original:
When releasing a JIRA version, I would like to be able to specify which revision of the source code should be used. The feature is present in Bamboo[1], but not exposed in Jira.
My use case is simply that we tag our releases in git, and I would like to specify this tag (same as I can with the customized build feature in Bamboo) to be the revision to build the release from. See attached image for the dialog as it currently exist. A field could be added here where it could be possible to specify revision. There are also some questions on Atlassian Answers asking for this feature or similar[2][3] [1]: https://jira.atlassian.com/browse/BAM-1640 [2]: https://answers.atlassian.com/questions/11161/specifying-the-source-code-revision-to-build [3]: https://answers.atlassian.com/questions/15696940/jira-build-release-needs-a-field-revision |
New:
{panel:bgColor=#e7f4fa} *NOTE:* This suggestion is for *JIRA Server*. Using *JIRA Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JRACLOUD-43648]. {panel} When releasing a JIRA version, I would like to be able to specify which revision of the source code should be used. The feature is present in Bamboo[1], but not exposed in Jira. My use case is simply that we tag our releases in git, and I would like to specify this tag (same as I can with the customized build feature in Bamboo) to be the revision to build the release from. See attached image for the dialog as it currently exist. A field could be added here where it could be possible to specify revision. There are also some questions on Atlassian Answers asking for this feature or similar[2][3] [1]: https://jira.atlassian.com/browse/BAM-1640 [2]: https://answers.atlassian.com/questions/11161/specifying-the-source-code-revision-to-build [3]: https://answers.atlassian.com/questions/15696940/jira-build-release-needs-a-field-revision |
| Link |
New:
This issue relates to |
| Labels | Original: bamboo jira jw-jim versioning | New: affects-server bamboo jira jw-jim versioning |