So, you need to map the status and fields while selecting the destination project and issue types. If issue types use different workflows, you may lose data when bulk moving issues. The issues in your destination project might have different settings than your source project, even if they are named the same. Or, you can bulk move issues between issue types in the same project, giving them the correct workflow and fields that best tracks the work needed. This can help you keep your project workspaces clean and all their issues relevant to the team who’s working on them. You can bulk-move issues to other projects on your Jira site. Select destination project and issue types while bulk moving issues Learn more about the things to keep in mind while moving between projects. Once you move the issues, this information is permanently removed. Issue component and version Information isn’t retained when you move issues from company-managed to team-managed projects. Some data is not transferred when moving issues from company-managed to team-managed projects.
Organize your projects better and maintain a cleaner backlog.Ĭater to your team’s requirements and much more. Try a different style of project (either team-managed or company-managed). You can move multiple issues to another project at once using a bulk operation.
If available, decide whether you'd like to send email notifications and select Next. This bulk change allows you to delete multiple issues at the same time. Review your bulk edits and select Confirm. Select a value for any required fields and, if available, decide whether you'd like to send email notifications before selecting Next. This bulk operation allows you to edit multiple issues at the same time. The available bulk edit operations depend on the issues selected and the nature of the fields you want to change. Review your bulk operation, and select Confirm when you are happy with the operation. Select a value for any required fields for this transition, and if available, decide whether you'd like to send email notifications. The actions available are dependent on the issues (and their associated workflows) that you have selected. Select Transition Issues and select Next. For example, to close multiple issues, you will need to provide a value for the Resolution field, such as Done, Fixed, or Won't Fix. You will also need to provide any values required to complete the transition. You can only perform one transition bulk operation at a time. This bulk change allows you to transition multiple issues through a workflow at the same time. This avoids notification overload for everyone working on the issues being edited. Notifications, if sent, will likely go to anyone watching an affected issue. #Bulk edit board view asana update#
You can choose to deselect Send mail for this update option when you choose what to update for the issues. Once you've done this, you can move on to transition, delete, move, edit, or watch/unwatch issues.
Select the issues you'd like to perform the bulk operation on, and select Next. Adjust the search criteria to show the appropriate list of issues. Search for and select the list of issuesįor each of the below procedures, you'll need to perform a search with the required filters to produce a list of issues. For example, you would need to have the Move Issue project permission and Make bulk changes global permissions to move a group of issues at the same time. To perform a bulk operation, you'll need the global Make bulk changes permission and the relevant permission for each project. The issue detail view will look a little different, some procedures will change slightly, and we have a new editor with markdown support. Take a look at What is the new Jira issue view? to see what's changed. We've released a new issue view for Jira Work Management.
0 kommentar(er)
