Skip to main content

Use FieldCraft with AI assistants

FieldCraft gives AI assistants a set of tools for your calculated fields, so you can ask about them in plain words.

You can use the tools in Rovo, and in AI clients that support MCP, such as Claude and ChatGPT.

The assistant can list your FieldCraft fields, explain what each one calculates, and tell you why a value is what it is.

For Jira admins, it can also change and create fields, put them on screens, fill in values and move fields to the trash.

To set it up, see Connect Rovo, Claude or ChatGPT.

What you can ask​

You askWhat happens
"Which FieldCraft fields do we have?"Lists the fields with their type and a JQL tip. When 25 or fewer fields match, Jira admins also see contexts, screens and calculation state
"What does the Cycle time field count?"Describes the field in plain sentences: statuses, calendar, pauses and display
"Why is Cycle time 3d 4h on PROJ-123?"Shows the stored value, the configuration that applies, when and why it was calculated, and a fresh calculation. Nothing is written
"Why is Time in review empty on old work items?"For Jira admins: checks contexts, screens, work items without a value, acknowledgement, settings, the hourly budget, reindexes and recent failures
"Add a Time in review field to the SUP screens"For Jira admins: finds the recipe, matches its statuses to your workflows, previews it, and creates it after you confirm
"Make Cycle time end at Released instead of Done"For Jira admins: plans the change, shows before and after in words, previews it, and changes it after you confirm
"Fill in the new field on existing work items"For Jira admins: estimates and starts a reindex within the hourly budget

Plan first, then apply​

Changes take two steps.

First, the assistant gets a plan. It describes the change in words, and previews it on up to 3 of your work items.

For a field change, the plan also estimates how many work items a reindex would touch.

Nothing changes until you confirm and the assistant applies the plan.

  • A plan works once, and only for the Jira admin who made it.

  • It expires after 15 minutes. Ask for a new plan after that.

  • For a configuration change, FieldCraft refuses the plan if someone changed the field's configuration since.

  • Plans to rename, create, add to screens or trash a field have no such check.

Some fields read data with the app's access: Jira expressions, Parent Field and Rollup. Their plan quotes FieldCraft's warning.

The assistant passes your acknowledgement only when you accept it explicitly. See Acknowledge app access.

A field the assistant creates applies to all spaces and work types.

Who can do what​

Everyone can list fields and field types, and read what a field does.

On work items you can see, you can have a value explained or previewed.

Jira admins can also diagnose fields, see every context and the stored configuration, and preview a draft configuration.

They can change, create and trash fields, add them to screens, and start reindexes.

For the full list, see AI assistant tools.

How the tools reach your data​

The tools run inside FieldCraft, on Atlassian Forge.

Your AI client reaches them through Atlassian's MCP service, after you sign in.

Each tool first checks your permission:

  • For a work item, it checks that your account can browse it.

  • If you can't, the answer says the work item "doesn't exist or you don't have permission to see it".

  • For Jira admin tools, it checks that you're a Jira admin.

After the check, the tool reads Jira as the app, the same way FieldCraft calculates values.

So an explanation can show a value built from data you can't open yourself, like the field on the work item view does.

For fields calculated with the app's access, people who aren't Jira admins don't see the calculation's step-by-step details.

Every result marks the Jira data in it as content, never as instructions for the assistant.

FieldCraft itself calls no AI model.

What your AI client does with the results is up to that service and your agreement with it.

Hourly budget​

The tools' Jira requests count toward FieldCraft's hourly calculation budget.

When the hour's budget runs out, explanations and previews skip the fresh calculation and say so.

The assistant doesn't retry on its own, so ask again after the hour.

License​

The tools need an active FieldCraft license.

If the license isn't active, every tool answers: "FieldCraft's licence on this site isn't active. A site admin can renew it under Manage apps." See Licensing.