Sibling actions remain open after baseline action is stopped?

(imported topic written by MattBoyd)

While working on some web report relevance I came across something that doesn’t seem right… the “State” of sibling actions in a baseline remains listed as open even if the parent baseline action has been stopped. Is this a bug?

I was hoping to be able to exclude stopped and expired actions using state of but now it looks like this isn’t always accurate. I don’t want to exclude action group members though…

(imported comment written by MattBoyd)

bump

Am I the only one that has this issue?

(imported comment written by BenKus)

What relevance are you using?

Ben

(imported comment written by MattBoyd)

Here is my relevance, but the console shows the same thing for sibling actions as well…

((id of action of it, name of action of it, (if (group member flag of action of it) then html “Parent Action: " & name of parent group of action of it & " (” & id of parent group of action of it as string & “)” else if multiple flag of action of it then html “Multiple Action Group” else html “Single Action”), name of issuer of action of it, names of computer of it, time issued of action of it, status of it, state of action of it, apply count of it) of results whose (apply count of it > 3) of bes actions whose (now - time issued of it < 100 * day AND not
(name of it as lowercase contains “power profile”) AND id of it > 0 AND (state of it as lowercase = “open” )))

9,525 results

I did find a workaround, but I still don’t think it’s right for the state of the sibling actions to remain set to open after the parent action is closed…

((id of action of it, name of action of it, (if (group member flag of action of it) then html “Parent Action: " & name of parent group of action of it & " (” & id of parent group of action of it as string & “)” else if multiple flag of action of it then html “Multiple Action Group” else html “Single Action”), name of issuer of action of it, names of computer of it, time issued of action of it, status of it, state of action of it, apply count of it) of results whose (apply count of it > 3) of bes actions whose (now - time issued of it < 100 * day AND not
(name of it as lowercase contains “power profile”) AND id of it > 0 AND (state of it as lowercase = “open” AND (if group member flag of it then exists parent group whose (state of it as lowercase = “open”) of it else true))))

7024 results

(imported comment written by MattBoyd)

Also, it looks like this only happens for multiple action groups that are stopped. When the parent action is expired, the sibling actions are expired as well.

(imported comment written by MattBoyd)

anyone?

(imported comment written by BenKus)

What happens when you do this? This should list group members that are open

names of bes actions whose (group member flag of it AND state of it = “Open” and state of parent group of it != “Open”)

Anything in common with those actions? In my deployment, only have 3 of these and they are very old actions…

Ben

(imported comment written by MattBoyd)

Well, we have 1901 of them. Some were issued as recently as yesterday. It doesn’t look like they’re issued by any specific console operator. The parent group’s state for all of them is Stopped (not Expired).

I modified your relevance a bit to get the details:

(names of it, name of issuer of it, name of parent group of it, state of parent group of it, time issued of it as string) of bes actions whose (group member flag of it AND state of it = “Open” and state of parent group of it != “Open”)

By the way, we’re using 8.0.627.0