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

ITOps Automation: support for the Affected Services field - allow dynamic values to be set, smart value support

    XMLWordPrintable

Details

    • Suggestion
    • Resolution: Unresolved
    • None
    • None
    • 3
    • 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 Definition

      Currently, the Affected Services field cannot be dynamically updated by using smartvalues or copying values from other fields. The values can only be selected from the pre-defined list.

      Suggested Solution

      • Set a value for the Affected Services field by copying the value from other fields or using smartvalues
      • It would be nice if users could select is one of when using the Affected services condition in Automation as currently, users must either create multiple rules or a branched rule which takes far more time to setup and also requires a more complicated setup.
      • Automation for Jira's conditions are not working properly towards the JSM field Affected services. - make them work
      • Ability to remain the existing "Affected Services" field value when using "Edit Issue" action to update the field via automation

       

      Attachments

        Issue Links

          Activity

            People

              36bd3fea80e3 Makarand Gomashe
              bd0e47de2684 Yuri Moura
              Votes:
              23 Vote for this issue
              Watchers:
              18 Start watching this issue

              Dates

                Created:
                Updated: