[Bug] Find/Replace > Row selection automatically advances only once

[tyler.bennett]

Issue Description:
When using the Find/Replace functionality of Ignition Designer, if you select a row from the search results then click the Replace button the replacement will be implemented for the selected row and then the selection in the search results will auto-advance by one row (expected). If you then click the Replace button again the replacement will be implemented for the selected row but the selection in the Results table does not auto-advance.

Expected Behavior:
I’d expect the selected row in the Results table to auto-advance after each click of the Replace button allowing the user to rapidly apply replacements without having to continually select each row in the results table before each click of the Replace button.

Ignition version: 8.1.15 (b2022030114)

[PGriffith]

Yes, this is a known bug on our backlog:

[Bug-5505] Find/Replace does not skip to next item consistently

When using the [Replace] button the next element in the “Results” list usually gets selected. -However this only works 1 time / if the Results list is in focus. pick your choice. -Next time I press [Replace], the next item is not alway selected. Instead the current item seems to be re-evaluated. -This will probably work in some cases. -However if you search and replace using a pattern which still exist in the current item after the replace-operation -it does not. ex: Find: “pump”, replace …

[tyler.bennett]

Where should I check before submitting bugs (to avoid duplication) and is this the right place to submit them?

I posted in the forum due to this post (linked below) but am curious if there is a preferred feedback method.

[Bug] How to write a quick and useful bug report

A good bug report needs four pieces of information to help us find, understand and fix the problems you share with us. 1. The behavior you unexpectedly encountered - One line is fine, and you can also use it as your post title (though remember to start your title with “[Bug]”). You may also paste a stacktrace or lines from the log here. 2. The behavior you were expecting to see - again, one line is fine. 3. A list of the steps you took that exposed the issue - including your starting point. …

[Kevin.Herron]

You’ll probably have a tough time avoiding duplication for sure, there’s nothing public but what you find here.

Submitting bug reports here is fine, but sometimes we miss them, or sometimes they just don’t get prioritized or the importance gets reported lower than it should be…

The official way to report a bug is through support.

The post you’re quoting was from a time we were running an early access public beta of Ignition 8 and support was not the right channel.