• Icon: Suggestion Suggestion
    • Resolution: Duplicate
    • None
    • None
    • 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.

      Currently in JIRA you can have relationships between tickets. One can block, or depend, or simply is related to another ticket. Pull requests in Stash should be capable of the same. I should be able to create a parent pull request 'group' or 'cluster' of different pull requests and define relationships between those children.

      Additionally if different pull requests have the same name, aka repo_a feature/new_awesome and repo_b feature/new_awesome, they should automatically group themselves (Or offer it as an option to the reviewers/Merge manager).

      Lastly, potentially if there are relationships defined between JIRA tickets (DEV-566 is blocked by DEV-555) and you are submitting pull requests for both, it seems that that relationship should follow the pull requests too. This should at least notify the merge manager of an order to merge the features (or reject them) so that your CI server build doesn't fail when Part B is merged before Part A.

            [BSERV-7773] Add relationships to pull requests

            Thanks Kody,

            Having reviewed BSERV-4577 I think the spirit of your suggestion is covered, so let's track it there.

            Roger Barnes (Inactive) added a comment - Thanks Kody, Having reviewed BSERV-4577 I think the spirit of your suggestion is covered, so let's track it there.

            Please add anything you feel is missing from this ticket into the others and feel free to close this as duplicate.

            Thanks.

            Kody Ensley added a comment - Please add anything you feel is missing from this ticket into the others and feel free to close this as duplicate. Thanks.

            Thanks for the suggestion, Kody. We've heard this a bit, and in fact have 2 slightly different variations that I believe duplicate your requirement. If you disagree or having something to add, let me know and I'll either open this up or augment the other issues to capture the need.

            Roger Barnes (Inactive) added a comment - Thanks for the suggestion, Kody. We've heard this a bit, and in fact have 2 slightly different variations that I believe duplicate your requirement. If you disagree or having something to add, let me know and I'll either open this up or augment the other issues to capture the need.

              Unassigned Unassigned
              33028c378e9c Kody Ensley
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: