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-17313

Add more logging information to a parent plan when a child plan does/doesn't execute.

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

      I'd like to see a feature that lets us know through a log file (and perhaps other configurable ways) that a child plan was triggered, or not triggered.

      In the case of not being triggered, explain why.

      For example:
      Setup 'planA' with a dependency to 'planB'.
      planA has 3 branches: master (default), foo, and bar.
      planB only has 1 branch: master (default)

      The 'foo' branch in planA is triggered.
      Even though planA is configured to trigger child planB when it completes successfully, it won't because planB doesn't have the same branch.

      Of course, this is documented, but the interface doesn't lend itself to understanding the chain of events if a problem occurs. This leads to difficult to diagnose situations that is more guess work than definitive logging output.

      I'd like to see an option that allows us to get better information about these chains of plans.

            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-17313

            Add more logging information to a parent plan when a child plan does/doesn't execute.

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

                I'd like to see a feature that lets us know through a log file (and perhaps other configurable ways) that a child plan was triggered, or not triggered.

                In the case of not being triggered, explain why.

                For example:
                Setup 'planA' with a dependency to 'planB'.
                planA has 3 branches: master (default), foo, and bar.
                planB only has 1 branch: master (default)

                The 'foo' branch in planA is triggered.
                Even though planA is configured to trigger child planB when it completes successfully, it won't because planB doesn't have the same branch.

                Of course, this is documented, but the interface doesn't lend itself to understanding the chain of events if a problem occurs. This leads to difficult to diagnose situations that is more guess work than definitive logging output.

                I'd like to see an option that allows us to get better information about these chains of plans.

                        Unassigned Unassigned
                        997de50ee6d6 KurtN
                        Votes:
                        0 Vote for this issue
                        Watchers:
                        2 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                            Unassigned Unassigned
                            997de50ee6d6 KurtN
                            Votes:
                            0 Vote for this issue
                            Watchers:
                            2 Start watching this issue

                              Created:
                              Updated:
                              Resolved: