-
Suggestion
-
Resolution: Duplicate
-
None
-
None
-
None
-
sql server 2k
tomcat 4.1.30
fedora core 1
-
5
-
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
Currently when you copy/clone an issue the only field which can be modified is the 'Summary' field. If you wish to modify other fields you have to edit the new issue after the copy and this produces additional notifications.
It would be nice to be able to specify system/custom fields to modify when copying the issue as you can when moving an issue. This would speed up the copy process and reduce 'noise' notifications.
- duplicates
-
JRASERVER-16574 Go to "Edit" screen before creating cloned issue
- Closed
-
JRASERVER-5052 Allow different "Clone Issue" options
- Future Consideration
- is duplicated by
-
JRASERVER-7737 Cloning an issue should have an extra step - it should take you to the edit issue screen before saving the cloned issue.....
- Closed
-
JRASERVER-8102 Clone operation should launch create issue page
- Closed
-
JRASERVER-10210 Clone does not respect "Defaul Asignee" definition for a project
- Closed
-
JRASERVER-10483 Clone and edit button
- Closed
-
JRASERVER-17190 Creating issues based on another issue
- Closed
- relates to
-
JRACLOUD-5417 Modify System/Custom Fields when copying an issue
- Closed
-
JRASERVER-9071 Copy issue instead of move - leave old issue in place, generate new, create link automatically
- Closed