[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 #8756

Activity

1. arpitsabharwal

   added

   type/questionThis issue is a questionThis issue is a question

   on Mar 8, 2026
2. dosubot

   added

   component/pydevlakeRelates to the Python framework and/or plugin.Relates to the Python framework and/or plugin.

   on Mar 8, 2026
3. dosubot commented on Mar 8, 2026

   

   dosubotBot

   on Mar 8, 2026 – with DosuBot

   Last edited by dosubot

   More actions

   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.

   ---

   Docs are dead. Just use Dosu.

   
4. arpitsabharwal commented on Mar 8, 2026

   

   arpitsabharwal

   on Mar 8, 2026

   Last edited by arpitsabharwal

   Author

   More actions

   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.
5. arpitsabharwal commented on Mar 8, 2026

   

   arpitsabharwal

   on Mar 8, 2026

   Author

   More actions

   @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.
6. dosubot commented on Mar 8, 2026

   

   dosubotBot

   on Mar 8, 2026 – with DosuBot

   Last edited by dosubot

   More actions

   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.

   ---

   Docs are dead. Just use Dosu.

   
7. chussenot commented on May 22, 2026

   

   chussenot

   on May 22, 2026

   More actions

   Hello, guys do you think we are ready to bump the helm chart to use the v0.1.3?
   apache/devlake-helm-chart#373

   Cheers,
8. klesh commented on May 30, 2026

   

   klesh

   on May 30, 2026

   Contributor

   More actions

   no, i am still working on some vulnerability fixes.
9. github-actions commented on Jul 30, 2026

   

   github-actionsBot

   on Jul 30, 2026 – with GitHub Actions

   Contributor

   More 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.
10. github-actions

    added

    Stale

    on Jul 30, 2026
11. github-actions commented on Aug 7, 2026

    

    github-actionsBot

    on Aug 7, 2026 – with GitHub Actions

    Contributor

    More 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.
12. github-actions

    closed this as not plannedon Aug 7, 2026