The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Does anyone think cloning is useful?

Benjamin Peikes
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
November 9, 2017

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

Comments for this post are closed

Community moderators have prevented the ability to post new comments.

TAGS
AUG Leaders

Atlassian Community Events