I can't create subtasks. Error indicates “Category: Category is required”?

[William Asbill]

This issue is similar to Charlotte’s Question from August of ’22.
Solved: Why can't I create subtasks? States 'Support Categ... (atlassian.com)

Like Charlotte, when trying to create a sub-task, I get a similar message, but slightly different, in that the message references “Category”. This just started happening mid-day today, where several sub-tasks had been created prior to this error manifesting later in the day.

When I go to Field Configuration and find “Category”, it’s indicated as being locked. I’m not sure whether Jira or a plugin app has this field locked. But the result is that, if it’s Required for Sub-Tasks, I cannot make it Not Required.

I checked the App Log Files and I do see where an app was recently added; GitHub for Jira was added 7 days ago. I’m not sure if this plugin locks “Category” or not. But, again, this issue suddenly appeared seemingly out of nowhere later today . . .a real mystery.

*Installed app GitHub for Jira (com.github.integration.production version 1.1.28-AC)

Your help will certainly be appreciated!

[John Funk · Accepted solution]

Hi William,

What type of project are you using? Team-managed? Company-managed? Jira Work Management? 

I know that the Category field has been added to Jira Work Management, but it should never be mandatory. Is there any Form attached to that project and issue type that might have the Category field marked as required? (Considering that it is not marked as required in the Field Config).

If not, I would open a support ticket with Atlassian to see why this is happening all of a sudden. 

[William Asbill]

Hello John,

Our project is Company-Managed. (I think that the forms capability is just for the Work Management option, correct?)

[John Funk]

Forms can be on JSM projects also. The other option is to check the workflow. Go into Edit mode for the workflow then click on the Create transition. Then click on Validators on the right side to see what is there. 

[William Asbill]

John, this is what I get:

[John Funk]

Okay, so looking at the bug that Trudy posted, make sure the Category field is not on the Create screen. This happens with the Resolution field sometimes also. Also, be sure to go ahead and open a support ticket and let me know if affects you and site the bug number. 

[Trudy Claspill · Accepted solution]

I have seen this new issue created in Atlassian's backlog:

https://jira.atlassian.com/browse/JSWCLOUD-24061

It includes this:

Workaround

Please create a Support Ticket with us and mention JSWCLOUD-24061 if you are experiencing this issue.

[William Asbill]

Thank you, Trudy, John and all.  On our side, the issue appears to be resolved/addressed for now. Suddenly, we can create Sub-Tasks again. Apparently, Jira rolled back a change or has provided some sort of remediation or work-around for the "required Category" issue from what I understand. 

Many thanks for your help.

[Rilwan Ahmed · Accepted solution]

Hi @William Asbill ,

One more user reported same issue here

If there are no validators added for the create transition of your workflow,  I would suggest to contact Atlassian support directly https://support.atlassian.com/contact/ 

[Trudy Claspill]

Hello @William Asbill 

Please check the Workflow for this type of issue in your project. Check the Create transition to see if an Validator (or Rule in Team Managed projects) has been added to require an entry in the Category field when this type of issue is created.

[William Asbill]

Hello @Trudy Claspill

In checking the Workflow, I don't see anything indicating that a Validator is being used.  In addition to looking at the flow, I see no mention of Validators in the Workflow area. 

[Nic Brough -Adaptavist-]

You need to be in edit mode in the workflow, and click on the transition to pop the triggers/conditions/validators/post-functions box up.

[William Asbill]

Trudy and Nic, there is just this 1 validator: