We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.

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

      Hi, we here develop a desktop application and do support several past versions. We use the cascade merge option. In the development cycle we get to a point when we freeze a release candidate (RC) branch or a service pack branch (SP). We don't want to disrupt them with cascading bugfixes, but any merge to them - critical fix - should fall down eventually to master. So.

      It would be nice to have the option to shape the merge cascade. My vision is that release branches (maybe other branches as well, it depends) would have a target cascade branch specified for each of them. This way admins could control, how the cascade looks. Take out branches like RC branches if needed. It would clash with the cascade prediction system, but I think this should replace it all together. So a desired look is another page in settings, where a target cascade branch could be selected - at least for release branches.

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.

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

                Hi, we here develop a desktop application and do support several past versions. We use the cascade merge option. In the development cycle we get to a point when we freeze a release candidate (RC) branch or a service pack branch (SP). We don't want to disrupt them with cascading bugfixes, but any merge to them - critical fix - should fall down eventually to master. So.

                It would be nice to have the option to shape the merge cascade. My vision is that release branches (maybe other branches as well, it depends) would have a target cascade branch specified for each of them. This way admins could control, how the cascade looks. Take out branches like RC branches if needed. It would clash with the cascade prediction system, but I think this should replace it all together. So a desired look is another page in settings, where a target cascade branch could be selected - at least for release branches.

                        Unassigned Unassigned
                        175ede71677c Vaclav Mares
                        Votes:
                        0 Vote for this issue
                        Watchers:
                        2 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                            Unassigned Unassigned
                            175ede71677c Vaclav Mares
                            Votes:
                            0 Vote for this issue
                            Watchers:
                            2 Start watching this issue

                              Created:
                              Updated:
                              Resolved: