We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.

      Issue Summary

      Currently - missing objects are flagged per import configuration.

      So, if the same object type is being updated by two different Import configuration - both with "Missing Objects" set to update a Status Attribute, with any threshold. After the threshold is reached on either import - the Status Attribute across all objects will fluctuate, depending on which Import was running last.

      Steps to Reproduce

      1. Configure 2 Import configurations (A, B) both updating the same Object Type for example: Importing from 2 Azure Subscriptions into the same Structure, with the Predefined mapping
      2. Let each import run on schedule to accede the Threshold
      3. Missing Objects Update on some object types is set to Update the Status Attribute to "Not found", Assume threshold is 2 syncs - for the explanation below
      4. Notice Object A (included in Import A) and Object B (included in Import B) both belong to the same object type X

      Expected Results

      Requested:

      If an objects in the same object type is updated by any import, the Missing Object's Counter is reset:

      Following the Imports along a timeline:
      Import A is running creating Object A

      Import B is running creating Object B, flagging Object A as a Missing Object

      Import A is running - Identifying Object A, Resetting Object A Flag, flagging Object B as a Missing Object

      Import B is running - identifying Object B, Resetting Object B Flag, flagging Object A as a Missing Object

      and so on - the end result: Status is not updated, unless an object is missing in BOTH the Imports for the given threshold

      Actual Results

      Following the Imports along a timeline:
      Import A is running creating Object A

      Import B is running creating Object B, flagging Object A as a Missing Object

      Import A is running - Identifying Object A, flagging Object B as a Missing Object

      Import B is running - identifying Object B, updating Status of Object A to "Not Found"(Threshold was reached)

      Import A is running - identifying Object A, Updating Status of Object A to "Running", updating Status of Object B to "Not Found" (Threshold was reached)

      Import B is running - identifying Object B, Updating Status of Object B to "Running", updating Status of Object A to "Not Found" (Threshold was reached)

      and so on.

      ...
      

      Workaround

      Either create a Root Object Type per subscription, so that each Import configuration will actually update its own Object Types,(Pros - Missing Objects will act as expected, Cons - hard to maintain, troubleshoot and requires more administration)

      or;

      Set Missing Objects to Ignore and configure an Automation rule to run on Schedule, and update Status to not found, if the object was not updated for a set period (Updated < now(-2d) - assuming that each Import will actually update the Objects (Pros - disregard the Missing Objects causing the Status to fluctuate. Cons - requires and Object update as a condition, and may add to performance when running)

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.

                Issue Summary

                Currently - missing objects are flagged per import configuration.

                So, if the same object type is being updated by two different Import configuration - both with "Missing Objects" set to update a Status Attribute, with any threshold. After the threshold is reached on either import - the Status Attribute across all objects will fluctuate, depending on which Import was running last.

                Steps to Reproduce

                1. Configure 2 Import configurations (A, B) both updating the same Object Type for example: Importing from 2 Azure Subscriptions into the same Structure, with the Predefined mapping
                2. Let each import run on schedule to accede the Threshold
                3. Missing Objects Update on some object types is set to Update the Status Attribute to "Not found", Assume threshold is 2 syncs - for the explanation below
                4. Notice Object A (included in Import A) and Object B (included in Import B) both belong to the same object type X

                Expected Results

                Requested:

                If an objects in the same object type is updated by any import, the Missing Object's Counter is reset:

                Following the Imports along a timeline:
                Import A is running creating Object A

                Import B is running creating Object B, flagging Object A as a Missing Object

                Import A is running - Identifying Object A, Resetting Object A Flag, flagging Object B as a Missing Object

                Import B is running - identifying Object B, Resetting Object B Flag, flagging Object A as a Missing Object

                and so on - the end result: Status is not updated, unless an object is missing in BOTH the Imports for the given threshold

                Actual Results

                Following the Imports along a timeline:
                Import A is running creating Object A

                Import B is running creating Object B, flagging Object A as a Missing Object

                Import A is running - Identifying Object A, flagging Object B as a Missing Object

                Import B is running - identifying Object B, updating Status of Object A to "Not Found"(Threshold was reached)

                Import A is running - identifying Object A, Updating Status of Object A to "Running", updating Status of Object B to "Not Found" (Threshold was reached)

                Import B is running - identifying Object B, Updating Status of Object B to "Running", updating Status of Object A to "Not Found" (Threshold was reached)

                and so on.

                ...
                

                Workaround

                Either create a Root Object Type per subscription, so that each Import configuration will actually update its own Object Types,(Pros - Missing Objects will act as expected, Cons - hard to maintain, troubleshoot and requires more administration)

                or;

                Set Missing Objects to Ignore and configure an Automation rule to run on Schedule, and update Status to not found, if the object was not updated for a set period (Updated < now(-2d) - assuming that each Import will actually update the Objects (Pros - disregard the Missing Objects causing the Status to fluctuate. Cons - requires and Object update as a condition, and may add to performance when running)

                        Unassigned Unassigned
                        8cdc82c96fd5 Yinon Negev
                        Votes:
                        18 Vote for this issue
                        Watchers:
                        17 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                            Unassigned Unassigned
                            8cdc82c96fd5 Yinon Negev
                            Affected customers:
                            18 This affects my team
                            Watchers:
                            17 Start watching this issue

                              Created:
                              Updated:
                              Resolved: