The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)
× Create
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Community resources
Community resources
Community resources
How to configure a workflow so setting a sub-task to Done does not set the Resolution for the parent
Christie_Circle
May 22, 2020 edited
Our team needs to create a project with a custom issue type that can accept sub-tasks, however, I need to alter the issue processing such that setting all the existing sub-tasks to Done does not set the Resolution for the parent Issue. I understand why JIRA does this as default, but in this instance, closure of all the sub-tasks should not predicate an assumption that the parent has a Resolution. I understand just linking items could be a workaround, but that is not what our team wants to do with this particular project and custom Issue. Thanks so much!
0 answers
Comments for this post are closed
Community moderators have prevented the ability to post new answers.
TAGS
Community showcase
Atlassian Community Events
Copyright © 2026 Atlassian