How should I item a user story without a user in the backlog?

Izumikawa, Masakazu

Hi, I will post for the first time. I can speak a little English, I'm an agile beginner.

My project uses JIRA for embedded software development.

Due to the shortage of semiconductor supply, the work of changing device control according to alternative parts is increasing significantly.
Many types of semiconductors have changed and will continue to be planned.

In my understanding, these are not user-stories, at our self-convenience. And it's not a bug, I'm not sure if it's appropriate to call it "Technical-debt"...

Is it appropriate to enter in the backlog as a (user-absent) story? Stories other than user-stories tend to have ambiguous priorities. But, there is an urgent need to change parts.

What item should I enter to JIRA? Can you tell me some ideas or similar experiences?

Thank you.

Carlos Garcia_9m6um6

Hi @Izumikawa, Masakazu ,

Welcome to the Community! I'm not sure I understood the use case, but if you'd like to categorize these work items differently than user stories, you could create a dedicated issue type (e.g. tech-debt as you mentioned):

(company managed projects)-

https://support.atlassian.com/jira-cloud-administration/docs/add-edit-and-delete-an-issue-type/

(team-managed projects)-

https://support.atlassian.com/jira-software-cloud/docs/set-up-issue-types-in-team-managed-projects/

If this issue type deserves the same priority treatment as the stories, but it's not happening today, I think this would require some adjustments in your processes.

If this wasn't really your question, please let me know, and I'll try to help! Thanks