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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Assign sub-task to creator when using new view and offer the original modal

When using the new Jira view, I want the streamlined sub-task creation to assign tasks to me when I'm creating them. 


In the old view a modal would open with many of the task details. Now, the stream lined experience only allows me to edit the title, and I must open the sub-tasks individually to assign them to me and to edit descriptions or hours. 

Azure DevOps has this flow down pat and allows me to edit sub-tasks as a card on a board without needing to create the sprint first.

1 answer

0 votes

Hello @Josh Gust

Thank you for reaching out.

Indeed, the inbuilt form displayed when clicking to create a sub-task have a limited number of fields. We have a feature request opened to allow Admins to select which fields are displayed in that form:

Let user customize which subtask fields to see in create issue screen 

Feel free to vote and watch the suggestion to increase its priority and also receive notifications about any updates.

As a workaround, you can enforce the complete form to be displayed when clicking to create a sub-task by adding any field of the form as required.

here are the steps to configure fields as required:

  1. Navigate to your project > Project settings > Fields > Actions > Edit fields
  2. Navigate to the field you want and click on "Required":

    P.S: This change will be applied to all the other projects using that same field configuration. For more details, you can check the documentation below:
    Changing a field configuration 

Let us know if you have any questions.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events