Not to get too meta, but I was just about to write up a story to add "require priority justification when changed" to our company's Scrum software. And I was thinking, as a Scrummaster, that's not one of the two things that we need spelled out to get things done (i.e. the user story and acceptance criteria). But I'd like to add it to some stories so that the PO can know why I think it might be a higher priority even though I'm not the one doing the final prioritization.
So, is it useful information in Scrum for the person writing the story to say why they think they need it sooner than later or does this information just get lost in the weeds usually?