Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

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

Subtasks type get changed on transition from a screen to create issue screen

While creating subtasks on story page (shortcut link), I am asked to select a subtask type. Once selected, it takes me to create issue screen where my previously selected subtask type is reset. I blindly go ahead and create the subtask assuming it should be the same I selected on previous screen. BOOM! It is NOT!! Serious Bug? Or I'm missing something here?

1 answer

1 accepted

0 votes
Answer accepted

Hello @Pooja Heda

Sorry to hear you are facing this problem.

Per your description, I can clearly understand that the sub-task issue type selected in the parent view is not carried over to the pop-up opened when finishing the sub-task creation.

Indeed, this is a bug with JIRA application that we've already reported to our developers:

Creating Sub-Tasks where create Sub-task screen is required does not preserve selected sub-task type 

Feel free to vote and watch the bug to receive notifications about its fix implementation and possible workarounds.

At this moment, it's possible to work around the problem by removing the required fields from your sub-task "create screen", so the pop-up will not appear and the selected issue type would be respected and use the required fields for the next status of the sub-task (With validators). We understand this is not a very useful option, so we're currently working to definitely fix it.

Please, let me know if you have any questions.

Thanks @Petter Gonçalves for your response. 

As this is a BUG and not a feature request, I expect you guys @Jira to pick this on priority. We're working on multiple sub task types each having different workflow. It definitely affects our workflows and creates a mess. Hoping you guys would take this up and get back asap. 

You are welcome, @Pooja Heda

Indeed, bugs are treated with a higher priority, but also considering the impact on the experience of the customers.

As you mentioned, this bug can be very impactful when you use several sub-task issue types, so we will absolutely take your feedback into account and let you know as soon as we have any update about it in the reported bug.

Thanks again for sharing your thoughts.

As a blind user, I am also will be waiting for the updates. Thanks for your understanding.

Suggest an answer

Log in or Sign up to answer

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