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

Your Points Tracker
  • 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
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?
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

set new status when moving an issue

Hi everyone,


when i move an issue,

in some cases the 'map statuses' step is available,

and in some cases it's skip on this step ans i cant set the new status.


Does somone know why and also-

How can i set a defult value for the new status?





1 answer

0 votes

Hi, @noa harel !

This steps depends on workflow of new "issue type"(or "new project" with the similar "issue type"). 

If workflow exists that status - "map status"-step wll be skiped.

If it does not exist you should set another status from the workflow from another issue type (or project with the same issue type, but different workflow).

Also you can read it in the documentation:

Issue Status — You may have set up custom issue statuses as part of a workflow. If you have assigned a custom status to your issue, and it does not exist in your target project, you must select a new issue status for your issue. You cannot arbitrarily change the issue status, i.e. the option to change the issue status will only appear if you are required to change it.

Hi Alexander,


Im not quite sure i got you.


with your permission, i'll explain my use case:

We dont use portal.

We have built an integration from our mobile app which create an issue with deafult request type in jira service managemrnt.


Then an agent classifies it to the right issue type by "move operatin" which cause the "request type" become "none".

Maybe is there a way to set the request type while moving the issue to the right issue type?

Hi, @noa harel !

It looks like a new question =) 

In that case I can recommend you to configure "field configuration scheme", where you set field "request type" required - How to make a field required or optional.

In that case your Agents can't move/create issues in that issue type with out "request type" and can set it during "moving"-operation.

Also can set different schemes for each issue type(if you need it).

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

340 views 9 7
Read article

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