Assignee is Ignored When Creating Subtasks in JIRA from Crucible

Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.

Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Symptoms

When trying to create a sub-task from Crucible the assignee field is ignored.

Cause

This can be caused due to many reasons:

  1. You have removed the assignee field from the create issue screens.

  2. If you are authenticating with a username and password, who does not have assign issue permission.

  3. If you are authenticating with trusted applications, the logged in Crucible user does not have assign issue permission.

  4. There is a workflow post function that is assigning the issue to the default user

Resolution

Case 1: Ensure that the assignee field is included on the create issue screen.

Case 2 & 3: Ensure that the user has created issue permission.

Case 4: Unfortunately you will need to remove the post function as it is incompatible with the feature.

There may be other causes, in which contact Atlassian Support.

Updated on April 8, 2025

Still need help?

The Atlassian Community is here for you.