[Bug][Jira] Error: Data too long for column 'field'

[rifat-tfs]

Search before asking

• I had searched in the issues and found no similar issues.

What happened

I am getting error when collecting data from Jira:

Error running pipeline 77. Wraps: (2) Error running task 734. | Wraps: (2) subtask extractIssues ended unexpectedly | Wraps: (3) error adding result to batch (500) | Wraps: (4) Error 1406 (22001): Data too long for column 'field' at row 201 (500) | Wraps: (5) Error 1406 (22001): Data too long for column 'field' at row 201 | Error types: (1) *hintdetail.withDetail (2) *hintdetail.withDetail (3) *hintdetail.withDetail (4) *hintdetail.withDetail (5) *mysql.MySQLError Error types: (1) *hintdetail.withDetail (2) *errors.errorString

What do you expect to happen

The data collection must not fail. The length of the string can be trimmed if possible or increase the length of the column.

How to reproduce

Since I don't know what in jira data maps to 'filed' column, it's not possible to say how it can be reproduced. However it happens for a few projects.

Anything else

No response

Version

v1.0.2

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[dosubot]

Hi @rifat-tfs! I'm Dosu and I’m helping the incubator-devlake team.

The error happens because the Jira plugin tries to insert a field name from a Jira issue changelog into the field column of the jira_issue_changelogs table, which is defined as varchar(255). If Jira returns a field name longer than 255 characters (possible with custom fields), MySQL rejects the row and you get this error. There’s currently no trimming or resizing of this value before insertion, and no config or code path in v1.0.2 to handle it automatically.

To resolve this, you can either:

1. Increase the column length in your database migration/model (e.g., to varchar(500)), but keep in mind MySQL index length limits if the column is indexed (see discussion).
2. Implement string trimming in the extraction code so values longer than 255 characters are truncated before insertion (recommended approach).

Let me know if you want details on how to make either change!

To reply, just mention @dosu.

---

Share context across your team and agents. Try Dosu.

[tc-jason-gregory]

I see this same sort of error with extractEpics. Version: v1.0.3-beta4@c5a4fbf

time="2025-08-28 09:55:04" level=error msg=" [pipeline service] [pipeline #823] [task #61040] subtask extractEpics ended unexpectedly\n\tWraps: (2) json: cannot unmarshal object into Go struct field .fields.description of type string\n\tWraps: (3) json: cannot unmarshal object into Go struct field .fields.description of type string\n\tError types: (1) *hintdetail.withDetail (2) *hintdetail.withDetail (3) *json.UnmarshalTypeError"

[klesh]

Try the "Full Sync" which would delete the existing collected data.

[tc-jason-gregory]

Try the "Full Sync" which would delete the existing collected data.

"Full Sync" did not resolve the issue for me. Errors (3) from the affected stages (Jira Tasks)...

subtask extractEpics ended unexpectedly Wraps: (2) json: cannot unmarshal object into Go struct field .fields.description of type string Wraps: (3) json: cannot unmarshal object into Go struct field .fields.description of type string Error types: (1) *hintdetail.withDetail (2) *hintdetail.withDetail (3) *json.UnmarshalTypeError

subtask extractEpics ended unexpectedly Wraps: (2) json: cannot unmarshal object into Go struct field Comment.fields.comment.comments.body of type string Wraps: (3) json: cannot unmarshal object into Go struct field Comment.fields.comment.comments.body of type string Error types: (1) *hintdetail.withDetail (2) *hintdetail.withDetail (3) *json.UnmarshalTypeError

subtask extractEpics ended unexpectedly Wraps: (2) json: cannot unmarshal object into Go struct field .fields.description of type string Wraps: (3) json: cannot unmarshal object into Go struct field .fields.description of type string Error types: (1) *hintdetail.withDetail (2) *hintdetail.withDetail (3) *json.UnmarshalTypeError

[davinogueiradev]

Hi @tc-jason-gregory to Epic errors, the PR #8559 related from this issue #8558 will solve it.

[klesh]

@d4x1 will release a new beta ASAP to include the fix.

[tc-jason-gregory]

Issue is resolved for me with latest v1.0.3-beta5@5da21bf. Thanks all!!!!

[d4x1]

@tc-jason-gregory v1.0.3-beta5 is released.

[github-actions]

This issue has been automatically marked as stale because it has been inactive for 60 days. It will be closed in next 7 days if no further activity occurs.

[github-actions]

This issue has been closed because it has been inactive for a long time. You can reopen it if you encounter the similar problem in the future.