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 started with Jira Software
New to Jira Software? These short, self-paced courses will teach you what you need to know to get up and running quickly.
The Beginner's Guide to Agile in Jira
Learn what agile, kanban, and scrum are and how agile works in Jira Software.
Realizing the Power of Jira Reporting and Dashboards
Use out-of-the box reporting and dashboard capabilities to view and assess progress and bottlenecks within projects.