I want to start some thoughts on this question.
When does text become a story?
- When the Product Owner (PO) accepted it?
- When did the Description of Requirements accept it?
- When did the idea emerge somewhere? ...
The idea behind these questions is that any user should be able to state a request, an idea, feedback, ... and therefore create an item.
The PO organizes the backlog, and works with the team to make this item ready to be considered as a "ready" story.
It's up to the Team to decide when an item enters the Product Backlog.
And as soon as it enters, it is then taken care of by the PO with a view to considering it in a sprint backlog.
And again, what I'm saying is MY point of view; the Team is self-organized, it's up to them to decide, to adjust this kind of thinking so that it has its own organization.
But as a result, JIRA, which is just the tool, will have to be configured according to the organization chosen by the Team.
All the cards can change in nature, the nature of the item (Issue) will then determine the possible states and properties of the item.
Passages from one state to another will determine the workflow of items of this type.
And finally, we ask the PO to prioritize the Backlog, people to give feedback, ... but should they be the operators / encoders in JIRA?
If we are in a system where everyone follows the rules, then it's like a wiki, everyone has all the rights and everyone does what they have the right to do. This greatly simplifies the rights management of the JIRA project.
- Let everybody create items (type request/ask/idea/need/feedback/...)
- Let decide the /team "how to convert them to stories"