We are unable to create subtasks within one of our projects. How can we fix this?

[Kerry K]

We're unable to create subtasks as child issues of stories/tasks in a particular project of ours. The configuration of this project is identical to others in our Jira Cloud instance which don't share this problem.

Here are some screenshots of what happens:

1. Creating a subtask 

2. Click enter

3. The subtask is nowhere to be found

[Pallavi Shirodkar]

Hi @Kerry K 

Confirm if "Sub-task" issue type is actually added to the project's issue type scheme. Even in "identical" configuration, the issue type scheme can be slightly out of sync. In company-managed projects, it must be present in the scheme. In team-managed projects, there may be a single sub-task type at the bottom of the list, and you should confirm it's correctly enabled.

In addition you can also check the following steps

Verify the existence of subtasks and compare the problem type scheme side by side across projects.

Examine the default assignee and project permissions.

Check the sub-task creation process; depending on the project type, use the "Add Child Issue" or "Create Sub-task" options from within the parent issue.

To get rid of authorization issues, test with an administrator.

Look for recent rule or editor modifications that might have inadvertently prevented the development of subtasks if you're utilizing automation or workflows.

Hope this helps!

[Valerie Knapp]

Hi @Kerry K , thanks for your post.

Did you used to be able to create sub-tasks in this project and it stopped working?

Is anyone able to create sub-tasks? and it is just specific users who cannot?

Can users create other work items but not sub-tasks?

Whether you are using sub-tasks is a global configuration, so it sounds like they are switched on in the site.

Can you check please if sub-tasks are in the Issue (work item) type scheme? It might be that you just have Epics and Stories for example.

Please check the configuration of the work item type scheme here - https://support.atlassian.com/jira-cloud-administration/docs/add-edit-and-delete-an-issue-type-scheme/ and share your findings.

Best wishes

[Kerry K]

I tested this issue in another project with identical settings and was able to create a subtask successfully.

The problem project shares the exact same settings (per the Project Settings > Summary) page as the 'control' project.  I'm at a loss for what could be causing this in the problem project.

I am a global admin so I'm not restricted by permissions, etc.

[Valerie Knapp]

Hi @Kerry K , thanks for your feedback.

Being a Jira admin doesn't necessarily mean you have create access in every project. Even where projects share a permission scheme, if you are not assigned to the role that gives the create permission, you won't be able to create. Are you able to create other work items in the 'problem' project and just not sub-tasks?

Best wishes

[Kerry K]

Hi @Valerie Knapp , yes I am able to create other work items in the problem project.

[Valerie Knapp]

Hi @Kerry K , thanks for your reply.

Is there any chance there is work item / issue security configured? https://support.atlassian.com/jira-cloud-administration/docs/configure-issue-security-schemes/ 

Otherwise, I am running out of ideas.

@Trudy Claspill , do you have any suggestions? @Marc - Devoteam , what about you?

Best wishes

[Trudy Claspill]

Hello @Kerry K 

In the second picture there is a progress bar shown in the subtasks area, which indicates that the does have some number of subtasks.

Can you click on the ... button and select View In Search? Do you get a list of the subtasks associated with the issue?

Can you check if a Security Scheme has been applied to this project? Navigate to the gear icon near your avatar and select Work Items.

Find the Work Items Security Schemes item in the navigation pane and click on it.

Check the resulting list to see if your space/project has been associated with a Security Scheme.

You should also be able to see that in the Summary page for the space/project settings.

Immediately after creating a subtask, have you check in the Global Automation page to see if any rules were triggered after the creation of the item? Perhaps execution of an automation rule caused the item to be moved or deleted or otherwise changed.