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: 'Automation for Cloud'
  1. Automation for Cloud
  2. AUTO-1373

Audit log message to show when action fails due to rule scope

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

      Issue Summary

      Currently, when the automation rule is scoped to specific projects and you have a component such as "Branch on JQL" that searches for issues from other projects, the audit logs just show that the JQL didn't find any issues rather than informing that the JQL couldn't find issues due to a scope restriction.

      This can be confusing since users might understand that there are configuration issues with the component itself, such as the JQL used in the branch action.

      Suggestion

      Implement logs that inform that the rule didn't work due to scope restrictions when that is the case.

            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: 'Automation for Cloud'
            1. Automation for Cloud
            2. AUTO-1373

            Audit log message to show when action fails due to rule scope

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

                Issue Summary

                Currently, when the automation rule is scoped to specific projects and you have a component such as "Branch on JQL" that searches for issues from other projects, the audit logs just show that the JQL didn't find any issues rather than informing that the JQL couldn't find issues due to a scope restriction.

                This can be confusing since users might understand that there are configuration issues with the component itself, such as the JQL used in the branch action.

                Suggestion

                Implement logs that inform that the rule didn't work due to scope restrictions when that is the case.

                        Unassigned Unassigned
                        09f701f61b25 Mateus Gauto
                        Votes:
                        1 Vote for this issue
                        Watchers:
                        3 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                            Unassigned Unassigned
                            09f701f61b25 Mateus Gauto
                            Votes:
                            1 Vote for this issue
                            Watchers:
                            3 Start watching this issue

                              Created:
                              Updated:
                              Resolved: