Uploaded image for project: 'Bitbucket Data Center'
  1. Bitbucket Data Center
  2. BSERV-4351

Populate Pull Request title from linked JIRA issue

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Answered
    • None
    • Pull Requests
    • None
    • We collect Bitbucket feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      When I create a Pull Request from a feature branch, the PR title defaults to the branch name. If the branch names follow an issue key convention, then the PR title is nothing more than the issue key. This isn't terribly helpful when faced with a list of PRs.

      It would be better, perhaps, if any JIRA issues linked to the PR could be used to populate the PR title. It gets a bit fuzzy when there are multiple linked issues, though.

            [BSERV-4351] Populate Pull Request title from linked JIRA issue

            Roger Barnes (Inactive) added a comment - - edited

            Hi Kenny,

            I think the suggestion has merit, but I don't think it's something we will address specifically in the near future. The multiple issues question is just one about how best to implement this.

            That said, I suspect this idea might get raised again in future as integration work progresses.

            Roger Barnes (Inactive) added a comment - - edited Hi Kenny, I think the suggestion has merit, but I don't think it's something we will address specifically in the near future. The multiple issues question is just one about how best to implement this. That said, I suspect this idea might get raised again in future as integration work progresses.

            Kenny MacLeod added a comment -

            I agree with bplump, we could just use more descriptive branch names. That would be an all-round general good thing. However, I still think getting this metadata from JIRA is a more robust solution, if for no reason other than to keep the JIRA issue name and Stash branch name consistent with one another, e.g. if the JIRA issue name changes.

            Kenny MacLeod added a comment - I agree with bplump , we could just use more descriptive branch names. That would be an all-round general good thing. However, I still think getting this metadata from JIRA is a more robust solution, if for no reason other than to keep the JIRA issue name and Stash branch name consistent with one another, e.g. if the JIRA issue name changes.

            Roger Barnes (Inactive) added a comment -

            kmacleod or mcook, any comments?

            Roger Barnes (Inactive) added a comment - kmacleod or mcook , any comments?

            Brent P added a comment -

            kmacleod,

            We've actually tackled this from a different angle. The "Create Branch" button in JIRA makes a branch in Stash containing the JIRA key and the JIRA description. But I'm guessing your team's convention is to have branch names containing only the JIRA key? It looks like some of the Confluence branches have a description after the key. Would you consider trying that?

            I'm not suggesting that to get you off my back. I really believe it's nice to have the issue summary after the branch name (especially when you've got the git branch showing on the command line).

            That said, maybe mcook would like to hear this suggestion for JIRA/Stash integration...

            – Brent

            Brent P added a comment - kmacleod , We've actually tackled this from a different angle. The "Create Branch" button in JIRA makes a branch in Stash containing the JIRA key and the JIRA description. But I'm guessing your team's convention is to have branch names containing only the JIRA key? It looks like some of the Confluence branches have a description after the key. Would you consider trying that? I'm not suggesting that to get you off my back. I really believe it's nice to have the issue summary after the branch name (especially when you've got the git branch showing on the command line). That said, maybe mcook would like to hear this suggestion for JIRA/Stash integration... – Brent

              Unassigned Unassigned
              kmacleod Kenny MacLeod
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: