This would be nice already in RF 4.1.

Too big task for RF 4.1. I moved this tentatively to RF 5.0 scope but we haven't yet started more detailed planning of that release and it's not clear will this one be actually included or not. If you find this important, comment here and explain your use case!

Oooops, there's PR #3869 adding this functionality. If the PR implements what's needed and doesn't have problems, this certainly can be included into RF 4.1 I don't have time to review the PR right now, but I moved this issue back to RF 4.1 to make sure I don't forget about it.

PR #3869 is a good start. There is, however, so much work still to be done both internally to handle custom statuses and in log report to show them nicely in statistics and elsewhere that I move this issue to RF 5.0 scope.

I would like to add here a wish that custom statuses would be recorded in the output.xml in some way (no opinion on how exactly) that for example the RF Jenkins plugin could easily still show only PASS/FAIL/SKIP, even if the report itself has custom statuses. We try to keep the statistics minimal (for backwards support), and CICD anyway (outside of RF Jenkins plugin) will rely on the return code of RF to know if execution ought to be stopped or not.

Given RF Jenkins Plugin is in Java, meaning we cannot leverage the parser, it means we have to support this by parsing the output.xml ourselves.

I just rechecked PR #3869 and noticed that there's even more work, including big design decisions, to be made for this to be reasonable enhancement in RF 5.0. In fact, it's way too big even for RF 5.1 that is going to b a relatively small release. On top of that, there hasn't been too much interest towards this issue. I still consider this a nice enhancement but we can return to it later if there's more interest.

Hi Pekka Klärck !
it's a very interesting feature !
do we know when it could be developed?

This feature isn't currently targeted for any planned release. If someone is interested to look at developing it, I'd be happy to help. Paying for the development is possible as well. The best way to get started with that would be joining the Robot Framework Foundation.