DoDiODev opened a new pull request, #8988:
URL: https://github.com/apache/devlake/pull/8988
### Summary
The jira issue model declares `FixVersions` as `gorm:"type:text"`, but the
original migration `20250619_add_fix_versions_to_issue` created the
`_tool_jira_issues.fix_versions` column as `varchar(255)`. Installations that
ran the earlier migration end up with a `varchar(255)` column that no longer
matches the model and truncates long fix-version lists.
This PR adds a follow-up migration that alters
`_tool_jira_issues.fix_versions` to `text`, aligning the database schema with
the model and allowing values longer than 255 characters.
### Scope
- New migration `20260707_change_fix_versions_to_text.go`
(`AutoMigrateTables` on `_tool_jira_issues`).
- Registration of the migration in the jira `migrationscripts/register.go`.
### Explicitly excluded
- No Grafana dashboard changes.
- No jira model changes (the model already declares `type:text`).
### Testing
- `make migration-script-lint` passes.
- `go vet` and `go build ./plugins/jira/...` pass.
- Manual DB gate on **MySQL** and **PostgreSQL**: upgraded a schema whose
`fix_versions` column was `varchar(255)`; after migration the column is
`text`/`longtext`, existing data is preserved, and a value longer than 255
characters is written and read back unchanged.
### Rollback
Revert the commit; the column type change is additive (widening) and does not
drop data.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
