Definition of Move Issue Permission
Move Issues
Ability to move issues between projects or between workflows of the same project (if applicable). Note the user can only move issues to a project he or she has the create permission for.
A section of the above definitions says, " ...between workflows of the same project " . Is this about issue transition in a workflow or am I understanding it wrong ? Because we have Transition Issues Permission which I believe controls workflow transition.
Can somebody help me understand this please ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Also I believe a user should have Move Issue permission in source project as well as destination project for " Move Issue between Projects" to work - I guess, that's what my common sense says :p
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Vickey Palzor LepchaYou don't need to have move permission in the destination project, source project is enough.
Second part,
ie.Once you are performing the move operation and change Issue type for destination project, jira will give you option to chose new statuses base on the work flow of the new issue type which you have just chosen is using. Also if you don't change issue type during move it will use the work-flow this issue type is using in destination project / same project(if you want to move within)
Note Moving issue to another project, will cause issue in this project to use workflow with transition in destination project defined for the destination issue type. In case of same project you can only change issue type and issues will use transition define in the workflow for the destination issue type in this project.
Best,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Vickey Palzor Lepchayou can move issues between projects and you need to have the move/create permission in permission scheme.
see documentation: https://confluence.atlassian.com/jiracoreserver073/moving-an-issue-861257345.html
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Moses Thomas I understand that " Move Issue " permission allows us to move issues between projects.
But I am confused about the second part of the definition - between workflows of the same project.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You need "move" permission to change the issue type inside a project when the source and target issue types have different configurations. Think of it as being the same as a "move but without selecting a new project"
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.