Comment 6 for bug 1348228

I was just looking at http://git.evergreen-ils.org/?p=Evergreen.git;a=commitdiff;h=2b5fc07b79da80c5aaf25103db3df84d543b0a02

We intentionally changed the behavior of that selector so that it would become sticky and default to the previous selection. I may have even been the person who requested that behavior.

At this point, removing those lines from the code don't seem to reinstate the previous behavior of defaulting to the current fiscal year, so there may more work required if an Evergreen site wanted this default.

I would be hesitant to change this behavior right now without adding some additional backend work. Right now, the current behavior is a problem for our libraries because staff become so accustomed to selecting just a few options on this interface before uploading orders, it's very easy to forget to change the fiscal year when a new year starts.

However, since we don't have a way to define different fiscal years for different org units, if a consortium has mixed fiscal years, I could see where it would be frustrating for their libraries to constantly change the fiscal year because they don't fall within the majority.

I think it would be better to address this with development to a feature with OU-specific fiscal years that can be defined from the client. In that manner, we know we are defaulting to a fiscal year that works for the site in question.

This approach, then, would move this report from a bug fix to wishlist.

When we do have OU-specific fiscal year, it would be great if we could also include a prompt that appears after the fiscal year-end process allowing the user to update their fiscal year information.