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

Inline Subtasks How to Configure


I have a JIRA project setup and I'm trying to remove the Create Sub Task button and instead use the inline subtask where you can easily and efficiently add sub-tasks using the plus/+ link which doesn't require the Create Sub-Task modal dialog to appear.

Here is a sample of the Sub-Tasks with the button that brings up the dialog (yuck).



I have a different JIRA instance where the sub-tasks can be created simply by clicking the plus button in the sub-tasks section:


So my question is how do I stop the dialogs from appearing and the inline sub-tasks additions to be enabled.

For reference the only field on the sub-task that is required is the Summary field.

I've searched high and wide however haven't found an appropriate answer as to how to enable the inline sub-task creation, the dialog is okay however it's so inefficient compared to the inline process.

Many thanks





2 answers

If you're still looking for this @Mark Iveson - you basically have to turn off any required fields for this to work in the creation screen.  I ended up having to use a separate screen for creation that had bare minimum everything *just for creation* so it didn't have any checks or additional screen fields that it wanted to get filled out.

Searching for the same answer here.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events