Uploaded image for project: 'Bamboo Data Center'
  1. Bamboo Data Center
  2. BAM-1362

If a commit is associated with a JIRA issue, Bamboo modifies the issue state based on the test outcome

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Obsolete
    • None
    • JIRA integration
    • None
    • 3
    • 10

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

      Bamboo should store be able to associate a JIRA project with each build, along with a SOAP login for that JIRA instance. When an CVS/SVN commit is made, Bamboo should parse the comments. If the comments begin with a JIRA issue identifier such as BAM-123, then once the test has been completed, Bamboo will use the JIRA SOAP interface to perform an workflow transition or add comment operation on that issue.

      For example, when a user commits a bug fix with a reference to the JIRA issue of that bug in the commit comments, the bug gets closed automatically if the tests pass. Any text following the JIRA issue identifier will be posted as a comment to the issue.

      Commit Result JIRA Issue State JIRA WorkflowTransition Operation
      Pass Open Resolve Issue (Fixed) Add comment
      Fail Open None Add comment
      Pass Resolved None Add comment
      Fail Resolved Reopen Add comment

      Thoughts:

      • This would need to deal with custom workflows, possibly by downloading the list of workflow operations and criteria to allow customisation.
      • How to populating required fields for transitions, eg from the comments?
      • Optionally, you could associate the workflow operation or comment with the JIRA account of the committer, but this would require a mapping between CVS/SVN user accounts and JIRA user accounts
      • This issue could be implemented as a Bamboo plugin

            [BAM-1362] If a commit is associated with a JIRA issue, Bamboo modifies the issue state based on the test outcome

            Amit Anand added a comment - - edited

            Refer this url as alternative approach https://dzone.com/articles/auto-transition-of-jira-issue-with-bamboo-build-re

            Amit Anand added a comment - - edited Refer this url as alternative approach  https://dzone.com/articles/auto-transition-of-jira-issue-with-bamboo-build-re

            tarunsachdeva86 added a comment -

            @Krystian Brazulewicz Could you please share the link to one of the points you mentioned above i.e. Improving permission system in Bamboo? I would like to know more details of what is happening there.

            tarunsachdeva86 added a comment - @Krystian Brazulewicz Could you please share the link to one of the points you mentioned above i.e. Improving permission system in Bamboo? I would like to know more details of what is happening there.
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3016332 ] New: JAC Suggestion Workflow 3 [ 3608688 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Krystian Brazulewicz made changes -
            Resolution New: Obsolete [ 11 ]
            Status Original: Gathering Interest [ 11772 ] New: Resolved [ 5 ]

            Krystian Brazulewicz added a comment - - edited
            Atlassian Update

            Hi everyone,

            Thank you for your interest in this issue.

            We understand the problem described in this issue as capability to provide Jira users with the the status of builds related to a specific Jira issue. The solution proposed here is very specific and thus not really adaptable to needs of different customers. While we believe in power of automation we believe even more in power of making informed decisions.

            For a while now, issue view in Jira is able do display development panel. Bamboo - Jira integration allows Jira users to see status of all builds and deployments related to a specific issue. This flow prevents Bamboo from polluting Jira issue with build-related comments and provides users with enough data to make decision if issue can be closed as resolved.

            Given that a solution for the problem exists we don't plan to work on this for the foreseeable future. We understand this decision will be disappointing to everyone who voted for this issue. After careful review of the most pressing needs of our customers, we've decided to prioritise other areas of the Bamboo roadmap, including:

            1. Robustness of Plan Branches
            2. Performance and stability improvements
            3. Providing building blocks for High Availability and Disaster Recovery solutions
            4. Improving permission system
            5. Allowing per-project allocation of resources
            6. Improving Bitbucket Server and Jira integrations

            We hope that you appreciate our candid and transparent communication. You can learn more about our approach to highly voted server suggestions here.
            To learn more on how your suggestions are reviewed, see our updated workflow for server feature suggestions.

            Kind regards,
            Bamboo Team

            Krystian Brazulewicz added a comment - - edited Atlassian Update Hi everyone, Thank you for your interest in this issue. We understand the problem described in this issue as capability to provide Jira users with the the status of builds related to a specific Jira issue. The solution proposed here is very specific and thus not really adaptable to needs of different customers. While we believe in power of automation we believe even more in power of making informed decisions. For a while now, issue view in Jira is able do display development panel . Bamboo - Jira integration allows Jira users to see status of all builds and deployments related to a specific issue. This flow prevents Bamboo from polluting Jira issue with build-related comments and provides users with enough data to make decision if issue can be closed as resolved. Given that a solution for the problem exists we don't plan to work on this for the foreseeable future. We understand this decision will be disappointing to everyone who voted for this issue. After careful review of the most pressing needs of our customers, we've decided to prioritise other areas of the Bamboo roadmap, including: Robustness of Plan Branches Performance and stability improvements Providing building blocks for High Availability and Disaster Recovery solutions Improving permission system Allowing per-project allocation of resources Improving Bitbucket Server and Jira integrations We hope that you appreciate our candid and transparent communication. You can learn more about our approach to highly voted server suggestions here . To learn more on how your suggestions are reviewed, see our updated workflow for server feature suggestions . Kind regards, Bamboo Team
            SET Analytics Bot made changes -
            UIS Original: 2 New: 3

            yuryf added a comment -

            Hi

            Any progress on this issue?

            Kind regards

            Yury

            yuryf added a comment - Hi Any progress on this issue? Kind regards Yury
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2703846 ] New: JAC Suggestion Workflow [ 3016332 ]
            SET Analytics Bot made changes -
            UIS Original: 3 New: 2
            SET Analytics Bot made changes -
            Support reference count Original: 9 New: 10

              Unassigned Unassigned
              david.soul@atlassian.com David Soul [Atlassian]
              Votes:
              67 Vote for this issue
              Watchers:
              40 Start watching this issue

                Created:
                Updated:
                Resolved: