Uploaded image for project: 'Automation for Jira Server'
  1. Automation for Jira Server
  2. JIRAAUTOSERVER-34

Riada Insight objects no longer auto-populate in set field value screen in Automation for Jira

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: High High
    • 7.2.2, 7.2.3
    • 7.1.7
    • Actions
    • None
    • Severity 2 - Major

      Summary

      A few users of both Automation of Jira and the 3rd party, Insights, app have complained about auto-population of Insight objects no longer working on the Action component to set field value in Automation for Jira (when creating a rule).

      Environment

      • Insights add-on 8.4+
      • Automation app 7.1.3+

      Steps to Reproduce

      1. Setup any version of Jira with Automation for Jira and latest version of Insights plugin installed
      2. Define Insight Objects
      3. Create an Insight custom field with the Insights custom field type of 'Insight Object/s'
      4. In the Action component of your Automation rule, select your Insight custom field
      5. Try to type characters into the value field for Insight Objects

      Expected Results

      Insight Objects should be pre-populated for this field

      Actual Results


      No objects populate even after you start typing
       

      Notes

      App Vendor has given feedback through one of our customers that the API used to retrieve insight objects have change since 8.4 of the Insights plugin (since March). Apparently we are to now use new API:

      GET /rest/insight/1.0/iql/objects?iql=objectTypeId={id} AND anyAttribute LIKE "<text>"
      

      instead of old one:

      GET /rest/insight/1.0/objecttype/{id}/objects?query=<text>
      

      Workaround

      You might be able to use the Advanced field editing - JSON method to set the Insight customfield value. (Expand the More options panel)

      Example configuration for the rule :

            [JIRAAUTOSERVER-34] Riada Insight objects no longer auto-populate in set field value screen in Automation for Jira

            Rodrigo Jose Zaparoli made changes -
            Remote Link Original: This issue links to "A4J-2530 (Bulldog)" [ 559090 ] New: This issue links to "A4J-2530 (JIRA Server (Bulldog))" [ 559090 ]
            Conny Postma made changes -
            Link New: This issue relates to JIRAAUTOSERVER-344 [ JIRAAUTOSERVER-344 ]
            Daniel Ramotowski made changes -
            Attachment New: image-2021-06-11-10-00-51-064.png [ 405347 ]
            Daniel Ramotowski made changes -
            Resolution New: Fixed [ 1 ]
            Status Original: Needs Triage [ 10030 ] New: Closed [ 6 ]
            Daniel Ramotowski made changes -
            Fix Version/s New: 7.2.3 [ 92830 ]
            Fix Version/s New: 7.2.2 [ 92997 ]
            Daniel Ramotowski made changes -
            Remote Link New: This issue links to "A4J-2530 (Bulldog)" [ 559090 ]
            Ruchi Tandon made changes -
            Description Original: h3. Summary
            A few users of both Automation of Jira and the 3rd party, Insights, app have complained about auto-population of Insight objects no longer working on the Action component to set field value in Automation for Jira (when creating a rule).

            h3. Environment
            * Insights add-on 8.4+
            * Automation app 7.1.3+

            h3. Steps to Reproduce
            # Setup any version of Jira with Automation for Jira and latest version of Insights plugin installed
            # Define Insight Objects
            # Create an Insight custom field with the Insights custom field type of 'Insight Object/s'
            # In the Action component of your Automation rule, select your Insight custom field
            # Try to type characters into the value field for Insight Objects

            h3. Expected Results
            Insight Objects should be pre-populated for this field
            !image-2020-06-02-16-38-02-089.png|thumbnail!

            h3. Actual Results
             !image-2020-06-02-16-35-35-074.png|thumbnail!
            No objects populate even after you start typing
             
            h3. Notes
            App Vendor has given feedback through one of our customers that the API used to retrieve insight objects have change since 8.4 of the Insights plugin (since March). Apparently we are to now use new API:
            {code}
            GET /rest/insight/1.0/iql/objects?iql=objectTypeId={id} AND anyAttribute LIKE "<text>"
            {code}
            instead of old one:
            {code}
            GET /rest/insight/1.0/objecttype/{id}/objects?query=<text>
            {code}

            h3. Workaround
            You might be able to use the [Advanced field editing \- JSON|https://support.atlassian.com/jira-software-cloud/docs/advanced-field-editing-json/] method to set the Insight customfield value. (Expand the *More options* panel)
            New: h3. Summary
            A few users of both Automation of Jira and the 3rd party, Insights, app have complained about auto-population of Insight objects no longer working on the Action component to set field value in Automation for Jira (when creating a rule).

            h3. Environment
            * Insights add-on 8.4+
            * Automation app 7.1.3+

            h3. Steps to Reproduce
            # Setup any version of Jira with Automation for Jira and latest version of Insights plugin installed
            # Define Insight Objects
            # Create an Insight custom field with the Insights custom field type of 'Insight Object/s'
            # In the Action component of your Automation rule, select your Insight custom field
            # Try to type characters into the value field for Insight Objects

            h3. Expected Results
            Insight Objects should be pre-populated for this field
            !image-2020-06-02-16-38-02-089.png|thumbnail!

            h3. Actual Results
             !image-2020-06-02-16-35-35-074.png|thumbnail!
            No objects populate even after you start typing
             
            h3. Notes
            App Vendor has given feedback through one of our customers that the API used to retrieve insight objects have change since 8.4 of the Insights plugin (since March). Apparently we are to now use new API:
            {code}
            GET /rest/insight/1.0/iql/objects?iql=objectTypeId={id} AND anyAttribute LIKE "<text>"
            {code}
            instead of old one:
            {code}
            GET /rest/insight/1.0/objecttype/{id}/objects?query=<text>
            {code}

            h3. Workaround
            You might be able to use the [Advanced field editing \- JSON|https://support.atlassian.com/jira-software-cloud/docs/advanced-field-editing-json/] method to set the Insight customfield value. (Expand the *More options* panel)

            Example configuration for the rule :
             !image-2021-03-15-16-38-45-340.png|thumbnail!
            Ruchi Tandon made changes -
            Attachment New: image-2021-03-15-16-38-45-340.png [ 401065 ]
            Julien Rey made changes -
            Symptom Severity Original: Severity 3 - Minor [ 14432 ] New: Severity 2 - Major [ 14431 ]
            Julien Rey made changes -
            Priority Original: Low [ 4 ] New: High [ 2 ]

              Unassigned Unassigned
              takindele Taiwo Akindele (Inactive)
              Affected customers:
              32 This affects my team
              Watchers:
              30 Start watching this issue

                Created:
                Updated:
                Resolved: