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: 

clone always does the clone and move in jira 7.2.3

Bhuvana
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
December 25, 2016

When trying to just clone an issue in JIRA 7.2.3, " I am always directed through "Clone and Move". Given I just want to "Clone" I have to "Cancel" then Move which results in warning message.

My expectation is that "Clone" and "Clone and Move" do what they say, with "Clone" creating a duplicate of the issue within the current project without prompting to move the copy to another project

2 answers

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Peter Rawlings
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
March 3, 2017

We too are also seeing this issue since we have upgraded to 7.2.2. We don't want to move the issue, we just want to clone - but, Clone will trigger the Clone and Move. If we disable Clone and Move, the issue goes away. I have just upgraded the Clone and Move plugin to the latest: v 2.8.2, but the problem persists.

 

Is there any update on this?

0 votes
Lynn Huang
February 23, 2017

I met the same problem, and I want to know if this is designed feature or a bug?

TAGS
AUG Leaders

Atlassian Community Events