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

Issue with change status from reopen to In Progress

Hi all,

 I got a task with bunch of subtasks. Once I try to change subtusk status from Reopen to to in Progress such message appear. It can be fixed by changing subtask to task and then moving to In Progress and further change to subtask but it doesn't look to be the best option. Did someone reach the same problem or have any suggestion for solution? 


jira status issue.png 

2 answers

1 accepted

2 votes
Answer accepted
Clark Everson Community Leader May 27, 2021

Hi @popatskyi 

that form is saying a field is required.

usually that means a field configuration or a workflow with a condition is set fir that issue type. To get rid of that you would need to update it so the field isn’t required. If it’s only happening for one transition state it’s probably in the workflow. If it occurs whenever trying to save a sub-task it’s the field configuration.


if you’re not the admin of the instance I would recommend talking to them.




Thanks Clark,

I believe it would help

Like John Funk likes this

Hi all,

Most likely the reason why initial issue appeared was due to creation of subtasks instead of tasks directly from Story and subtasks didn't inherit all properties from Story. So the way I found to fix it is convert the subtask to task and the problem disappears. Maybe it will help someone in future.

Suggest an answer

Log in or Sign up to answer
Site Admin
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...

226 views 7 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