We've been trying to use Jira as a workflow tool so we've created "template" issues, which have a bunch of subtasks associated with them. We then try to use the clone functionality to create a new instance of one of these issues.
The clone works and copies the subtasks, but the Reporter stays the same. It does not change to the person who performed the clone. Does anyone else find this ridiculous?
The documentation states that the only way to get Jira to set the Reporter to the user performing the clone, would be to remove the ability of the user to change the Reporter on tickets. This seems completely backwards.
How do other people set up "template" tickets that they can reuse? Workflows are often not enough, we often want a piece of work to come along with subtasks.
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.