[Question][General] Is there a list of open defects / bugs identified in v1.0.3-beta9, v1.0.3-beta8 and v1.0.3-beta7

[arpitsabharwal]

Question

Hi folks, I wanted to use devlake for github, jira and pagerduty , due to jira removing support for some api which have been used in devlake@v1.0.2 , i have to use devlake@v1.0.3-beta7 or ahead

I wanted to understand whether to use any of these 3 is suggested since i am doing a POC , if i shall proceed and try the beta,

1. which of 3 beta versions is recommended to use
2. is there a list of open issues in all the 3 versions
3. is there a list of integration test report which i can generate and see the list of failing cases in 1.0.3.beta7, 8 and 9 which are passing in 1.0.2

Screenshots

If applicable, add screenshots to help explain.

Additional context

Add any other context here.

[dosubot]

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

Here's a summary of known bugs across these beta versions:

v1.0.3-beta7

• Backend crashes on startup due to NULL priority column values (fixed in beta8)
• PostgreSQL migration failure - ORDER BY on JSON columns doesn't work (unresolved)

v1.0.3-beta8

• GitHub connection error with token_expires_at datetime value (fixed in PR #8667)
• JIRA Cloud data collection 500 error during collectIssueField

v1.0.3-beta9

• Bitbucket PR extraction fails on microsecond timestamp parsing (fix in progress)
• MySQL 8.x incompatibility with q_dev plugin migrations (fixed in PR #8745)
• Jira Cloud case-sensitivity bug causing it to use deprecated /api/2 endpoint (fixed in PR #8608)

Recommendations for your POC:

1. Avoid beta7 entirely due to the startup crash
2. beta8 is more stable but has GitHub/JIRA issues
3. beta9 has multiple active bugs, including the Jira API endpoint issue you're trying to avoid

For Jira Cloud specifically, ensure your endpoint ends with /rest/ (e.g., https://xxx.atlassian.net/rest/).

Unfortunately, I couldn't find formal integration test reports or release notes comparing these versions - the information above comes from GitHub issues. Since several critical fixes were merged after beta9, you may want to check if a newer release (or RC) is available that includes all these patches.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

   

[arpitsabharwal]

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

Here's a summary of known bugs across these beta versions:

v1.0.3-beta7

• Backend crashes on startup due to NULL priority column values (fixed in beta8)
• PostgreSQL migration failure - ORDER BY on JSON columns doesn't work (unresolved)

v1.0.3-beta8

• GitHub connection error with token_expires_at datetime value (fixed in PR #8667)
• JIRA Cloud data collection 500 error during collectIssueField

v1.0.3-beta9

• Bitbucket PR extraction fails on microsecond timestamp parsing (fix in progress)
• MySQL 8.x incompatibility with q_dev plugin migrations (fixed in PR #8745)
• Jira Cloud case-sensitivity bug causing it to use deprecated /api/2 endpoint (fixed in PR #8608)

Recommendations for your POC:

1. Avoid beta7 entirely due to the startup crash
2. beta8 is more stable but has GitHub/JIRA issues
3. beta9 has multiple active bugs, including the Jira API endpoint issue you're trying to avoid

For Jira Cloud specifically, ensure your endpoint ends with /rest/ (e.g., https://xxx.atlassian.net/rest/).

Unfortunately, I couldn't find formal integration test reports or release notes comparing these versions - the information above comes from GitHub issues. Since several critical fixes were merged after beta9, you may want to check if a newer release (or RC) is available that includes all these patches.

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other

   

@dosu
when is the next planned release date which has addressed the open issues, some of the PR's are merged for the open issues mentioned in 1.03.9.beta.

[arpitsabharwal]

@dosu
when is the next planned release date which has addressed the open issues, some of the PR's are merged for the open issues mentioned in 1.03.9.beta.

[dosubot]

I couldn't find a specific release date announced for the next version after v1.0.3-beta9.

Based on what I found:

• The project follows a bi-weekly release cadence (7 days development + 3 days bug-fixing/release)
• Historically, when critical fixes are merged, the team has released new beta versions within days
• v1.0.3-beta9 was released in January 2026 and remains the latest version

Since several critical PRs (like #8608, #8667, #8745) have been merged after beta9, a new beta or RC release could come soon, but no official date has been announced. I'd recommend monitoring the GitHub releases page for updates, or you could ask the maintainers directly in this issue about the timeline.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}