What is the benefits of “Move Issue” wizard in JIRA?

1.	What is the benefits of “Move Issue” wizard in JIRA?
Answer» The move issue wizard enables you to specify another PROJECT in your JIRA instance. Move wizard permit you to change certain ATTRIBUTES of an issue like Issue Type: If your issue is a custom issue type and does not occur in your target project, you must choose a new issue type for your issue Issue Status: If you have assigned your issue as a custom issue status and it does not exist in your project, you must select a new issue status for your issue Custom Fields: If you have determined required custom fields for your issue, which do not occur in the target project, you must set values for them

Answer»

The move issue wizard enables you to specify another PROJECT in your JIRA instance. Move wizard permit you to change certain ATTRIBUTES of an issue like

Issue Type: If your issue is a custom issue type and does not occur in your target project, you must choose a new issue type for your issue
Issue Status: If you have assigned your issue as a custom issue status and it does not exist in your project, you must select a new issue status for your issue
Custom Fields: If you have determined required custom fields for your issue, which do not occur in the target project, you must set values for them

Discussion

No Comment Found

Related InterviewSolutions

If you have retrieved the create meta or edit meta of your project and the field that you are trying to analyze may not show up in resulting JSON then what does it mean?
What actions are currently supported in the JIRA advanced fields?
What is the reason for this type of error and how to fix it? The custom field 'XXXX' in the backup project is used by issue types 'AAAA, BBBB' but the field with the same name in the current JIRA instance is not available to those issue types in this project.
If you automate certain tasks in JIRA with help of scripting, then they stop working in different environments due to change of IDs. What is a reliable solution to fix this problem?
How do you perform health check on JIRA Confluence?
What global settings must be exactly same between 2 instances of JIRA while importing and exporting?
What all is not supported by the import and export plugin of the JIRA?
During import of configuration XML, if there is an error about orphan fields then what is the best way to handle?
While importing configuration file, if we receive following error then what is the root cause: “Load failed for reason: Missing a FieldLayoutItem for FieldLayout XXXX and field YYYY”?
What are the most common errors in exporting configuration data in JIRA?

What is the benefits of “Move Issue” wizard in JIRA?

Discussion

No Comment Found

Related InterviewSolutions

Reply to Comment