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

Automations for Insight: Ability to set a trigger when a specific object attribute is changed from one specific value to another

XMLWordPrintable

    • 5

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

      Problem Definition

      Currently, on Automation for Jira, there is a trigger to detect if an object in Insight has been updated, but there is no feature to detect the old value vs new value of the attribute change. The lack of this makes it not possible to configure an automation rule that triggers when an attribute is updated from one specific value to another.

      It's also not possible to switch triggers on objects at the moment, so it's not possible to configure an automation rule that triggers a change on another linked object when an object is updated.

            [JSDCLOUD-10017] Automations for Insight: Ability to set a trigger when a specific object attribute is changed from one specific value to another

            Muhammad Ramzan(Atlassian Certified Master) added a comment -

            Hi @Alex,

            Thanks for such a nice suggestion, that's a great workaround the only issue here is, how we could know which attributes were updated. There could be more than one, so getting the first record will not solve the issue , unfortunately

            Muhammad Ramzan(Atlassian Certified Master) added a comment - Hi @Alex, Thanks for such a nice suggestion, that's a great workaround the only issue here is, how we could know which attributes were updated. There could be more than one, so getting the first record will not solve the issue , unfortunately

            Iona Augustine added a comment -

            Hi Alex,

            I think you probably misunderstood what was after. Vivian raised this new feature request based on my predicament.

            What was requested was:

            Automatically update a field value in an object when the object being a reference to another object is being replaced i.e. We have an object called 'Object 1234' that has a field of object reference with value of 'SAM 1' that links to object 'SAM 1'. We would like 'SAM 1's status field to change to 'Removed' automatically when we change that field value from 'SAM 1' to 'SAM 2'

             

            Iona Augustine added a comment - Hi Alex, I think you probably misunderstood what was after. Vivian raised this new feature request based on my predicament. What was requested was: Automatically update a field value in an object when the object being a reference to another object is being replaced i.e. We have an object called 'Object 1234' that has a field of object reference with value of 'SAM 1' that links to object 'SAM 1'. We would like 'SAM 1's status field to change to 'Removed' automatically when we change that field value from 'SAM 1' to 'SAM 2'  

            Alex van Vucht (GLiNTECH) added a comment -

            Yes, object history is not available today.
            As a workaround, you could call the GET object history endpoint using {{ object.id}} and work with the first result. You'd have to hardcode the workspace ID, but that doesn't change in a JSM instance.

            I expect it should be similar to the When Issue Updated {{ changelog}} smart value.

            As for the second observation, that's correct and discussed further in JSDCLOUD-10023

            Alex van Vucht (GLiNTECH) added a comment - Yes, object history is not available today. As a workaround, you could call the GET object history endpoint using {{ object.id}} and work with the first result. You'd have to hardcode the workspace ID, but that doesn't change in a JSM instance. I expect it should be similar to the When Issue Updated {{ changelog}} smart value. As for the second observation, that's correct and discussed further in JSDCLOUD-10023

              msingh3@atlassian.com Mandeep Singh
              vchoo Vivian C
              Votes:
              26 Vote for this issue
              Watchers:
              20 Start watching this issue

                Created:
                Updated:
                Resolved: