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

Details

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

    Description

      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

      Attachments

        Issue Links

          is duplicated by

          Suggestion - AUTO-307 Issue field compare condition should use the ID of Request Types

          • Closed

          Suggestion - AUTO-386 When we create a new sub-task via automation, we should be able to set a parent id besides "current issue" or "trigger issue"

          • Closed

          Suggestion - AUTO-523 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

          • Closed
          is related to

          Suggestion - JRACLOUD-61048 As a jira admin asked to rename a custom field, I want to know which filters contain the custom field, so I know which ones to update

          • Gathering Interest

          Suggestion - JRACLOUD-76466 Jira should store the custom field details based on field ID instead of the field name

          • Gathering Interest

          Activity

            People

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

              Dates

                Created:
                Updated: