Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,362,247
Community Members
 
Community Events
168
Community Groups

Does anyone think cloning is useful?

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.

0 comments

Comment

Log in or Sign up to comment