Action Execution Settings Being Rest

Usage and Config Platform
1

(imported topic written by SystemAdmin)

Hi,

I just came across this possible bug:-

  1. create an action - it doesn’t matter if it’s from the Tools->Take Custom Action or from the Fixlet/Task ‘Take Action’ button.

  2. in the ‘Execution’ tab, change the ‘Preset’ from ‘Default’ to ‘Policy’

  3. Check the ‘On failure, retry’ box

  4. change the number of times to retry to 23

The Preset ‘Policy’ returns to ‘Default’! Any other value in the ‘times’ box seems to be fine - it just doesn’t seem to like ‘23’.

Is anyone else seeing this?

Mark.

2

(imported comment written by BenKus)

Hmmm… Doesn’t do the same thing for me…

I wonder if you are seeing a behavior where the Take Action Dialog will figure out if your settings match any existing presets and if so, it will revert to that option. So in this case, if you have saved your “default” present as having 23 retries, then this behavior would occur.

You can test this by changing to the “Default” preset and seeing if 23 appears in that box.

Ben

3

(imported comment written by BenKus)

And if this is really a bug based on 23, then it is an awesome bug. I suggest that our only reasonable response will be to instruct our QA team to try every single number in that box (and all boxes) looking for bugs… (oh… and we will release BigFix 9.0 in 2018 after we finish this testing :)…)

Ben

4

(imported comment written by SystemAdmin)

:D:D:D:D

Not sure I can wait that long - I + really, really + need to use ‘23’ :wink: (not)

Hopefully, I’ve managed to attach a word doc with some screen shots…

5

(imported comment written by BenKus)

I can only guess that there is something weird about your default preset…

We can call this the “Michael Jordan Bug”.

Ben

6

(imported comment written by SystemAdmin)

I think I found the offending Preset - but it still doesn’t make sense to me.

I’ve got (or had) a preset (I’ve attached an image) that has some standard settings - except - it’s the only one that had a ‘Revert To Global…’ button instead of a ‘Delete Preset’ button.

I ‘reverted’ it to global and deleted it and I’m not getting the problem any more. I’m not sure how I even got it into a ‘Local’ state?