Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Create Issue Permission & Move Issue Permission ?

 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.

3 answers

0 votes
Moses Thomas Community Leader May 27, 2018

@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

@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 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"

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

@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,

Can somebody help me understand this please ?

Suggest an answer

Log in or Sign up to answer
TAGS

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you