Update Form Answers
jira_update_proforma_form_answersUpdate Jira form field answers using the Forms REST API. Specify question IDs, answer types, and values to modify form data. Note: For DATETIME fields, use direct custom field updates instead to preserve time components.
Instructions
Update form field answers using the Jira Forms REST API.
This is the primary method for updating form data. Each answer object must specify the question ID, answer type, and value.
⚠️ KNOWN LIMITATION - DATETIME fields: The Jira Forms API does NOT properly preserve time components in DATETIME fields. Only the date portion is stored; times are reset to midnight (00:00:00).
Workaround for DATETIME fields: Use jira_update_issue to directly update the underlying custom fields instead:
Get the custom field ID from the form details (question's "jiraField" property)
Use jira_update_issue with fields like: {"customfield_XXXXX": "2026-01-09T11:50:00-08:00"}
Example:
# Instead of updating via form (loses time):
# jira_update_proforma_form_answers(issue_key, form_id, [{"questionId": "91", "type": "DATETIME", "value": "..."}])
# Use direct field update (preserves time):
jira_update_issue(issue_key, {"customfield_10542": "2026-01-09T11:50:00-08:00"})Automatic DateTime Conversion: For DATE and DATETIME fields, you can provide values as:
ISO 8601 strings (e.g., "2024-12-17T19:00:00Z", "2024-12-17")
Unix timestamps in milliseconds (e.g., 1734465600000)
The tool automatically converts ISO 8601 strings to Unix timestamps.
Example answers: [ {"questionId": "q1", "type": "TEXT", "value": "Updated description"}, {"questionId": "q2", "type": "SELECT", "value": "Product A"}, {"questionId": "q3", "type": "NUMBER", "value": 42}, {"questionId": "q4", "type": "DATE", "value": "2024-12-17"} ]
Common answer types:
TEXT: String values
NUMBER: Numeric values
DATE: Date values (ISO 8601 string or Unix timestamp in ms)
DATETIME: DateTime values - ⚠️ USE WORKAROUND ABOVE
SELECT: Single selection from options
MULTI_SELECT: Multiple selections (value as list)
CHECKBOX: Boolean values
Args: ctx: The FastMCP context. issue_key: The issue key containing the form. form_id: The form UUID (get from get_issue_proforma_forms). answers: List of answer objects with questionId, type, and value.
Returns: JSON string with operation result.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| issue_key | Yes | Jira issue key (e.g., 'PROJ-123') | |
| form_id | Yes | ProForma form UUID (e.g., '1946b8b7-8f03-4dc0-ac2d-5fac0d960c6a') | |
| answers | Yes | List of answer objects. Each answer must have: questionId (string), type (TEXT/NUMBER/SELECT/etc), value (any) |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |