Pipelines builds to update JIRA issue

Issue #14849 resolved
Lucas Moura created an issue

This is a request to have an option similar to Smart commits but that would work based on the results of a Pipeline builds. The JIRA issue would be updated accordingly with the results a Pipeline build

Comments (17)

  1. Aneita Yang staff
    • changed status to open

    Hi Lucas,

    Thanks for the suggestion. I'll open this issue to gauge the interest of other users on this feature; however, the team is currently working on higher priority features, so this isn't something that we'll work on anytime soon.

  2. Aneita Yang staff

    Hi everyone,

    Thanks for your interest in this issue.

    I'd like to get a better understanding of the use cases for this feature. If you're interested in discussing your use cases, please reach out to me at ayang@atlassian.com and we can schedule a quick 30 min chat.


  3. Luke Jacobs

    I'm surprised this type of functionality isn't already existing.

    @aneita I can't speak for the OP, but I know that I would love to see this integration as well. As far as details, what I would envision is something similar to the smart tagging in a git commit.

    Right now, if you commit and you include the Jira issue as a tag and a status, it will automatically update the Jira issue status to done. Ie: "git commit -m 'PROJECT-123 #done Fixed the bug referenced'".

    If you had something similar as part of pipeline builds, it may be integrated into the bitbucket-pipeline.yml file itself as a new setting.

    Say you had a Jira workflow of "Open" -> "In Progress" -> "In Testing" -> "Approved".

    You also have the following branches on the relevant repo, "master", "staging", "production".

    Your build may deploy to a server based the branch that a commit is merged into.

    Lets say there's a branch build step for "staging" and "production". As part of that branch build settings, you may also have "smart_status: In Testing" and "smart_status: Approved" as part of the respective steps.

    When you want to make a code update, you'd create a branch with the name of the tag "PROJECT-123", make your changes and push them up. You submit a pull request to "staging" and when it's approved/merged, the build process starts, and once it's successful it will update the Jira "PROJECT-123" ticket to status "In Testing".

    When it's merged into production, it's status is updated to "Approved".

    Whether or not this is the best workflow remains up for debate, but if you wanted this workflow, you'd have to be able to have smart jira tagging worked into the pipeline build process.

    Alternatively, someone may decide to have Jira status updates be the trigger that sets off a build pipeline -- in which case I think we'd need the ability to connect a Jira project to a specific repository by default (opposed to how "create branch" will let you create a branch in ANY repository you have permission to access right now). That way, it would know where to look for the correct build configuration automatically.

  4. Johnathan Gilday

    @aneita my team uses Jira for issue tracking, Bitbucket for source control and peer reviews, and we are currently transitioning our builds and deployments from Jenkins to Bitbucket Pipelines project by project. Our Jira workflow considers an issue completed when it has been deployed to production. We would like to start using Bitbucket Pipelines deployment tracking with Jira to automated this Jira workflow transition. When a change is deployed to the production environment, we would like to trigger an update to the Jira issue

  5. Vlad Iacob

    Is there any current update to this feature? One of our main motivations for moving to bitbucket / pipelines was for seamless JIRA integration. @aneita

  6. Aneita Yang staff

    Hi everyone,

    We've begun investigating the work required to surface build and deployment information on Jira issues as part of issue #13129, which we hope to have available to customers later this year. The next step as part of the Bitbucket/Jira integration is to support transitioning of issues when certain actions take place in Bitbucket. This is something that still needs some further investigation on our end but is on our medium-term roadmap.


  7. Mark Harwood

    Just having the ability to trigger a release as a step within Pipeline would be a huge step forward!

  8. Jason D'Amour

    Any update on this? On this atlassian blog, it contains this picture Screen Shot 2018-10-01 at 11.05.21 AM.png Which implies that this feature already exists... I would like to at least see the pipeline status, and would like to trigger builds as well.

  9. José Filipe Neis

    +1 @Phunky

    Right now we have to manually create/assign JIRA releases to every feature that is built. It would be great if JIRA could create/assign a release based on commit messages.

    Also, we use sequential build numbers on master. This way, if version 29 was released, it means that all features contained in releases <29 were also released. I understand this release hierarchy would be something new to JIRA itself, but would be great to a CD pipeline IMO.

  10. Brian Maissy

    I'd also like the ability to create a JIRA bug report from failing tests on the pipelines page, and have the resulting ticket automatically linked back to the relevant pipelines run and code commit on which it ran

  11. Aneita Yang staff

    Hi everyone,

    We recently shipped Bitbucket Pipes which make it easier to build powerful, automated CI/CD workflows in a plug and play fashion without the hassle of managing integrations. We’ve worked with industry leaders including Microsoft, AWS, Slack and more to build over 30 supported pipes that help automate your CI/CD pipeline.

    One of the available pipes is a Jira pipe, which lets you transition a Jira issue within your pipeline. To use this pipe, add the YML snippet to your bitbucket-pipelines.yml file and add the variables required by the pipe to work. You can do this via the online editor (which gives you a nice experience with browsing the information about the pipe) or via your IDE.

    For more information about pipes, check out our documentation.

    Given the Jira pipe gives you the ability to configure an issue transition which was the original request, I'm going to close this issue. If you have a use case that isn't covered by this addition, please raise a new ticket with an explanation of your use case so that we can track it separately.


  12. Giovanni Giordano

    Hi @Aneita Yang ! We are using jira-transition pipe to transition Jira issues but we are using it in deployment steps. When we merge 2 branches into master, 2 pipelines are triggered, each one deploying onto the same environment, so one of them is stopped automatically and the jira-transition pipe is not invoked.

    How do you suggest to handle this situation?

  13. Log in to comment