Jira Automation Assistance Without Being Able to Import

[Adeel nikama]

I am trying to create a Jira automation and am running into an issue of not being an admin. I was able to create a JSON script, but since I'm not an admin I cannot import it directly to automations. I have included the full prompt and JSON script below, but can someone help me with exactly what to select if I hit Create rule directly from the Automation section of the project?

When the DUE DATE in a ticket is changed and that ticket has a PARENT assigned to it, then change the PARENT DUE DATE if the CHILD'S DUE DATE is a later date than what is on the PARENT ticket DUE DATE or if the DUE DATE in the PARENT ticket is blank.

    {
  "name": "Sync Parent Due Date with Child",
  "description": "When a child's Due Date is updated, update the parent Due Date if the child has a later date or if the parent Due Date is blank.",
  "projects": [],
  "status": "ENABLED",
  "trigger": {
    "type": "FieldValueChanged",
    "field": "duedate"
  },
  "components": [
    {
      "type": "condition",
      "conditionType": "jira.issue.condition",
      "configuration": {
        "field": "parent",
        "operator": "is_not_empty"
      }
    },
    {
      "type": "branch",
      "branchType": "parent",
      "children": [
        {
          "type": "condition",
          "conditionType": "jira.or.condition",
          "configuration": {
            "conditions": [
              {
                "type": "condition",
                "conditionType": "jira.advanced.compare.condition",
                "configuration": {
                  "firstValue": "{{issue.duedate}}",
                  "operator": "isAfter",
                  "secondValue": "{{issue.parent.duedate}}"
                }
              },
              {
                "type": "condition",
                "conditionType": "jira.issue.condition",
                "configuration": {
                  "field": "duedate",
                  "operator": "is_empty",
                  "scope": "parent"
                }
              }
            ]
          }
        },
        {
          "type": "action",
          "actionType": "jira.edit.issue",
          "configuration": {
            "fields": {
              "duedate": "{{issue.duedate}}"
            },
            "scope": "parent"
          }
        }
      ]
    }
  ],
  "schemaVersion": "1"
}

[Nikola Perisic]

Hello @Adeel nikama 

You cannot bypass the creation of automation if you are not the project administrator. This would be a security flaw which would allow any user that is not a project admin to create their automation rules possibly disrupting the project. To answer your question, looking at the JSON script, the trigger is field value changed which exists.Followed by that trigger there is a condition of Parent is not empty which is followed by a branch for every parent that has children and containing advanced comparing with the smart values from your script and another condition when the due date is empty followed by an action to edit the due date.

[Marc -Devoteam-]

Hi @Adeel nikama 

See this example.

btw the JSON has a flaw in the rule, is has 2 conditions for the parent in the branch, this will always fail to edit, because it 1st checks on due date of the trigger issue is after the due date of the parent issue and then check if the parent due date empty.

So it would fail to edit in any case, if the parent due date is empty it would fail in the 1st condition and if not empty it would fail on the 2nd one.

Also the smart values are wrongly formatted.

As I said, here is an example: