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

How do I create a subtask and make it appear on my kanban automatically Edited


I am new at Jira,

When I create a new subtask from a task on the kanban, this subtask appear on the right pane in the list of subtasks for that task. If I want to make it appear under the parent task in the Kanban, I have to click on it's link, which takes me to the subtasks page, there I have "READY FOR DEV" button (not sure if it's a generic name or something chosen by our admins).
Pressing that and going back to the kanban view now shows the subtask.
This is a little annoying because I have to do it per subtask.
I tried to find a way to do it from within the "Edit" popup of that subtask which is a little less annoying, but this also does not exist.

What can I do in order to shorten the way I am creating subtasks in the kanban?

1 answer

1 accepted

2 votes
Answer accepted

For an issue to appear in a column on a Kanban board, it needs to be in a status that is mapped into that column.  Your "Ready for dev" button is triggering a workflow transition that changes the status of an issue to one that is in the column. 

This is not an "edit", which is why you can't do it from the edit screen, and yes, it was something set up by your admins - they created the workflow!

You could get your admins to change the project settings such that sub-tasks use a workflow that has "create" land the issues directly into the "ready for dev" status.  But bear in mind this will affect all sub-tasks, including the ones that are part of issues that have not gone on to the board (which will make things look odd - having ready-for-dev pieces of issues that are not themselves ready for dev)

Any way for them to define that if a sub task is created from kanban - check if the parent task is in a status that exists in the kanban and apply that status as default to the child task?

No, there's no way to do this, the create process has no knowledge of how it was started.

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