Uploaded image for project: 'Jira Service Management Cloud'
  1. Jira Service Management Cloud
  2. JSDCLOUD-13803

Supportability of placeholders(Filter issue scope) with automation workflow

    XMLWordPrintable

Details

    • 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

      Problem

      At this point, Filter issue scope is not supported with automation workflows as mentioned at the bottom of Configure the Assets objects custom field page. This means that Assets custom fields can't use Filter issue scope to set values if the field is exposed to an automation rule.

      Suggested Solution

      Have an option to use Assets custom field in an automation even when the field has Filter issue scope set.

      Why This Is Important

      In Edit issue and Create issue automation actions, there is a need to set values in Assets custom field after some filtering. The lack of this ability hinders the greater usage of the automation for Assets custom fields.

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

      Attachments

        Activity

          People

            Unassigned Unassigned
            cf3a9e2a2246 Diptajeet Datta
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated: