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

Allow the actor / author to optionally be retained when importing rules

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

      Description

      Currently, we override the authorAccountId value of rules when they are imported using “Rules Import”. We do this as the authorAccountId could be different across different accounts (DC vs Cloud). Instead, we default the id to the authorAccountId from whichever user uploaded the rule.

      We have had a case where the user knows that the id exists, and is correct, and wishes to instead persist this ID, not the user uploading the rules.

      Steps to reproduce

      1. Export a rule as JSON
      1. Set the authorAccountId value in the JSON to anything you like or leave it be
      1. Using the rule import tool, re-upload the rule
      1. Note that the author field of the rule is not honoured, and is instead set as you (the user uploading the rule)

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

            Allow the actor / author to optionally be retained when importing rules

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

                Description

                Currently, we override the authorAccountId value of rules when they are imported using “Rules Import”. We do this as the authorAccountId could be different across different accounts (DC vs Cloud). Instead, we default the id to the authorAccountId from whichever user uploaded the rule.

                We have had a case where the user knows that the id exists, and is correct, and wishes to instead persist this ID, not the user uploading the rules.

                Steps to reproduce

                1. Export a rule as JSON
                1. Set the authorAccountId value in the JSON to anything you like or leave it be
                1. Using the rule import tool, re-upload the rule
                1. Note that the author field of the rule is not honoured, and is instead set as you (the user uploading the rule)

                        89403358cf11 Charlie Gavey
                        44981f7279ac Greice Faustino (Inactive)
                        Votes:
                        6 Vote for this issue
                        Watchers:
                        2 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                            89403358cf11 Charlie Gavey
                            44981f7279ac Greice Faustino (Inactive)
                            Votes:
                            6 Vote for this issue
                            Watchers:
                            2 Start watching this issue

                              Created:
                              Updated:
                              Resolved: