user story feedback
This user story sounds good, right? "As a participant, I want to get #21KK14 notification when submitting my option, so I am notified that my vote was sucessfully submitted."
BUT: a participant would never know the code of a notification. It would be better to state: As a participant, I want to be notified (within a certain timeframe) that my vote was processed, so I know that my vote was succesful."
The goal of a User Story is not to explain something to the end user, it is to describe the problem that needs to be addressed in as detailed and exact language as needed in order to successfully do so. If the participant can receive multiple notifications associated to the option, stating specifically which notification is important helps to clarify the problem.
If we want to get picky, your "within a certain timeframe" is too ambiguous unless you are going to clarify that in the Acceptance Criteria. For example, the Development Team could satisfy that criteria by giving the participant notification 3 years after their vote has been processed. Would you agree that solution is satisfactory?
I will also add that the two story statements you provided are different problems. The first is to notify that "my vote was sucessfully submitted" and the second is to notify that "my vote was processed". From my knowledge of processing things, submitted and processed are two different operations. In reality I would see your first story as part of the solution of the second. Because as a participant, I'd like to know my submittal was received and that the vote has been processed. Especially if there was a possible lag between the two.