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.
Uploaded image for project: 'Bamboo Data Center'
  1. Bamboo Data Center
  2. BAM-16187

Using branch plan dependency, branch plan name is checked instead of repository branch name

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

      Using branch plan dependency, branch plan name is checked instead of repository branch name.

      If the branch plan display name is different than the parent branch plan, the dependency is not triggered despite using the same branch from the same repository.

      Point of improvement would be documenting this better to prevent confusion. For instance, updating the description on the Enable dependencies for all branches of this plan option:

      Dependencies are triggered for branches only if there is a branch branch plan with the same name display name within the dependent plan

            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.
            Uploaded image for project: 'Bamboo Data Center'
            1. Bamboo Data Center
            2. BAM-16187

            Using branch plan dependency, branch plan name is checked instead of repository branch name

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

                Using branch plan dependency, branch plan name is checked instead of repository branch name.

                If the branch plan display name is different than the parent branch plan, the dependency is not triggered despite using the same branch from the same repository.

                Point of improvement would be documenting this better to prevent confusion. For instance, updating the description on the Enable dependencies for all branches of this plan option:

                Dependencies are triggered for branches only if there is a branch branch plan with the same name display name within the dependent plan

                        Unassigned Unassigned
                        dlee@atlassian.com Deric Lee (Inactive)
                        Votes:
                        1 Vote for this issue
                        Watchers:
                        3 Start watching this issue

                          Created:
                          Updated:

                            Unassigned Unassigned
                            dlee@atlassian.com Deric Lee (Inactive)
                            Votes:
                            1 Vote for this issue
                            Watchers:
                            3 Start watching this issue

                              Created:
                              Updated: