https://bugs.documentfoundation.org/show_bug.cgi?id=167194
--- Comment #5 from Lars Jødal <[email protected]> --- (In reply to Telesto from comment #4) > (In reply to Lars Jødal from comment #3) > > As suggested in the original report, a solution could be to disable the > > feature for a user's own change, as the feature was never intended for > > handling your own changes. > > True. However it's makes life rather inconvenient for QA/testing purposes. > If you have to switch user to test. Agreed. The problem is that the behaviour differs between the two situations: a) One user makes the change, another user uses "Reject but Track". b) The same user (user name) makes the change and uses "Reject but Track". The feature is intended for situation a). If it is tested in situation b), test results can be confusing. So _not_ disabling the feature in situation b) can also make life inconvenient for testing. > I ask myself: is there a downside by allowing to reject but track for your > own change? For normal users, the downside is the risk of confusion when "Reject but Track" is used upon your own insertion: The change simply disappears, so "Reject but Track" in this special case produces the same result as normal "Reject". For testers, the downside is the risk that the test results will be confusing if the tester overlooks the difference in behaviour. Whether these downsides are serious enough to warrant disabling the feature is a different question. At least at present, I have no strong opinion on that. -- You are receiving this mail because: You are the assignee for the bug.
