@gunstr thanks for reporting, we will have to look into this

@SchrodingersGat can we move this to 1.0?

@matmair sure, it requires a bit more attention and I would like to get the new release out.

@SchrodingersGat @matmair is your recommendation not to use the cusom states at all until you have worket this trough a bit more?

@gunstr I think that for this particular issue, you can manually adjust the stock status per stock item, rather than as a group? That is, via the "edit stock item" dialog

@SchrodingersGat Yes, for the UI related issues that is probably OK. I have seen your discussion on the implementation in general and got a bit worried that updating all current stock items with custom states at this stage might be waste of time - but maybe that would not be the case...

As you might remember from previous discussions I pach my local installations for each upgrde with more relevant status names and I'm really looking forward to skip that and use the custom states instead. A few limitations in the UI is OK as long as there are work arounds.

@gunstr I think that for this particular issue, you can manually adjust the stock status per stock item, rather than as a group? That is, via the "edit stock item" dialog

@SchrodingersGat I mentioned already when I wrote the issue that if I set the TestState on an item from the Edit Stock Item modal and then select TestState as a filter to the Stock Item list no items are visble. I do not find any workaround for this and it makes the Custom States less useful, Do you want me to create a separate issue for this so it does not get lost?

@gunstr yes that does sound like a separate issue - please create a new one with as much information as you cna provide