Uploaded image for project: 'Automation for Cloud'
  1. Automation for Cloud
  2. AUTO-468

Support for field IDs instead of just field names in Automation

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None

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

      Suggested improvements

      • When creating an automation rule using an action to set a field, if a custom field is used any update to the field name (rename) will cause the field to be recognized as a deleted field in the automation rule. For example, if a field is named "Example id" and you change it to "Example ID" it will be recognized as a deleted field due to the capitalization if "id". In the field mapping for the automation rule use the field ID as the mapping variable instead of the field name when using the "Choose which filed to select..." option, so that when a filed name is altered the rule will still map to the renamed field
      • When we create a new sub-task via automation, we should be able to set a parent id besides "current issue" or "trigger issue"
      • Make it easier to work with fields, e.g. Improve Automation Rules so they accept keys and names for the Project and Issue Type fields instead of just the Ids
      • Issue field compare condition should use the ID of Request Types

      .Screen Shot 2022-04-29 at 2.47.32 PM.png

        1. Screen Shot 2022-04-29 at 2.47.32 PM.png
          Screen Shot 2022-04-29 at 2.47.32 PM.png
          154 kB

            Unassigned Unassigned
            emccutcheon Earl McCutcheon
            Votes:
            36 Vote for this issue
            Watchers:
            14 Start watching this issue

              Created:
              Updated: