You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
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.