I am working on a project in which implementation user stories have to go on Jira.
Depends what you mean by “implementation”.
If you mean “rolling out existing software”, then that work can indeed be represented by Stories.
If you mean “programming new software”, then that work can be represented by Tasks (as siblings to associated Stories). But I would instead recommend that such implementation be captured in the Stories themselves (i.e., vertical thin-slicing), in a new custom field called say “Implementation Intention” (during “How” Planning).
Recommended Learning For You
Level up your skills with Atlassian learning
Learning Path
Get the most out of Jira
Start with basic Jira terms and navigation. Then, discover how to effectively organize work and customize your Jira experience.
Learning Path
Atlassian tools and practices for developers
Reduce context switching by making Jira more efficient, and apply collaboration best practices for streamlined team operations.
Atlassian Certified Associate
Jira Essentials certification
Validate your knowledge of key Jira concepts like using work items, spaces, boards, and Rovo.