Existing work item fields

[Mark Chester]

What work item fields exist by default in Jira (cloud)?  This seems to be super-secret information as far as documentation goes.  All I can find is how to create custom fields, which appears to be what's causing our current problem with the Rovo AI chat and agents.

Specifically, I need to know whether Acceptance Criteria is available as a default field. For some reason, our AC field is a custom field.

[Trudy Claspill]

Hello @Mark Chester 

The tricky part of that question is your definition of "default".

There are many fields that are defined by the Jira system and are locked; i.e. Summary, Sprints, Team, Description. 

There are fields that are automatically created based on the apps (Jira vs. JSM) that you have installed. These fields may still be considered "custom" fields. Usually the Description associated with the field will provide some indication with text like "This custom field was created by Jira." But that is not always the case.

There are fields that are automatically created based on the type of Spaces (formerly known as Projects) you create. Certain Space templates add more custom fields to your environment.

Other custom fields may be added to your system by the inclusion of 3rd party apps.

These are all "custom" fields, even though they may have been created automatically rather than by a person.

If you really wanted to get a list of the "default" fields you could set up a separate subscription of Jira (and JSM, if you use that), create one of each type of Space, and any third party apps you have, and then use the Jira REST API to get a list of all the fields that exist.

https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-fields/#api-group-issue-fields

You might be able to find information about the creation of a field in the Audit Log under Administration > System. But that log generally keeps only 6 months worth of information.

I have a Free Jira/JSM subscription with a handful of apps, and based on the Spaces I've created so far there is no Acceptance Criteria field. 

[Trudy Claspill]

Can you tell us more details about the specific problem you are encountering? 

[Mark Chester]

My definition of "default" is nothing special - the fields that exist in Jira before someone starts creating custom fields.

I am having a hard time getting Rovo to copy acceptance criteria when cloning work items.  And our AC field is a custom field.  I would expect Acceptance Criteria to exist in Jira out of the box, considering how much documentation there is about how to create good acceptance criteria and how central that idea is to an Agile process.

[Trudy Claspill]

Based on my system I would say that "Acceptance Criteria" is not a field that Jira creates by default, though it may be created based on a Space template that I have not yet used to create a new Space.

I have not used Rovo much yet, but if you care to share the details of what you are doing then perhaps I or another community member can provide insights into what might be the root cause of the problem. 

One key piece of information is what is the custom field type of your Acceptance Criteria field?

[Jack Brickey]

Indeed that is not a 'default' field. It either exists because someone added or a third party addon included.

[Sebastian Rawson]

Thank you for your question about default fields in Jira Cloud. The distinction between default and custom fields is crucial, especially for integrations.

Acceptance Criteria is not a default system field in Jira Cloud. In a standard Jira project, the Description field is used to capture user stories and requirements. Any dedicated "Acceptance Criteria" field is a custom field created by an administrator in your specific Jira instance.

To check any field's status in your project:

1. Go to Project Settings > Fields.

2. Find the field in question (e.g., "Acceptance Criteria"). Its type will be listed as "Custom" or show a specific scheme name if it's a modified system field.

This explains the issue with Rovo AI. The AI agent is likely programmed to interact with standard Jira field names and structures. Since your "Acceptance Criteria" is a custom field, the agent cannot recognize or populate it automatically. You would need to map this custom field within the Rovo AI configuration or adjust your process to use the default Description field for criteria that the AI needs to access.