Skip to main content

Development Insights sync status and user mapping, resumable repository ingestion, and session management

· 4 min read

Development Insights now shows the state of each collection, so you know whether your dashboards are current. Repository ingestion picks up where it stopped after an interruption, and you can end browser and app sessions from your account. Bitbucket Cloud connections need action: switch to an API token.

Action required: switch Bitbucket Cloud connections to an API token​

Bitbucket Cloud no longer accepts app passwords. Venue.sh now connects with an API token and the email of the Atlassian account that owns the token.

If a Bitbucket Cloud connection still uses an app password, create an API token and update the connection with the token and the email. Until you do, Venue.sh cannot read from Bitbucket Cloud through that connection.

See Bitbucket Cloud.

See current data and know when a collection is behind​

Each repository, Jira board, and Jenkins job has its own collection with a status, so you can tell whether a chart is current before you rely on it. This covers GitHub, GitLab, Bitbucket Cloud, Jira, and Jenkins.

  • A first collection of a large repository does not fail when the provider limits how many requests Venue.sh can send. The collection pauses and continues when the limit allows.
  • Dashboards show a collecting state while a new source loads, instead of empty panels.
  • The date range uses whole days. A range that starts on a day now includes the first rows of that day.

See Development Insights and Dashboards.

Check each source on the sync status page​

The Sync Status page lists every repository, board, and job with the state of its latest collection. You can retry a run that failed. You can also start a manual refresh for one source. Venue.sh allows one manual refresh per source each hour, so a second request in that hour is declined and tells you when to try again.

See Sync Status.

Match people across tools​

The new User Mapping page links the accounts that Git, Jira, and Jenkins report to the people in your organization. Person panels group the work of one user across tools. You can filter by state, search, relink or unlink an account, and invite or ignore accounts that have no match.

Ask the Assistant about Development Insights​

The Assistant and MCP tools for DORA and engineering metrics answer from the same data as the dashboards you see in the portal.

Resume repository ingestion after an interruption​

A repository ingestion that stops partway, for example after a restart, now continues from the saved progress instead of starting again. Unchanged content keeps its existing embeddings, so repeat ingestions take less time. Search and the Assistant keep reading the last complete version of a repository while a new one is built.

The new ingestion progress page in Settings > AI Settings shows each run, its phase, and real progress.

See Ingestion and summary.

End sessions you do not recognize​

The Account page now groups your sessions into browsers and apps. Browser sessions show a device label such as "Chrome on macOS". You can end one session or sign out of all the others. Ending an app session does not sign you out of other logins to the same app.

Admins can see the sessions of a member on the member profile and end one or all of them. Each admin action appears in the activity log.

See Settings.

Assistant improvements​

The Assistant can read a file from an ingested repository by path and can look up Venue.sh documentation. It keeps its thinking steps visible in the conversation.

Other fixes​

  • A server-side check now enforces password complexity.
  • Sessions end when a password is reset or changed.
  • Select lists no longer scroll sideways when the list scrolls.
  • AWS Cost Insights accepts only valid AWS region codes.
  • Data grid toolbars and headers keep their spacing on wide and narrow screens.
  • Several API routes now check the organization and role of the caller more strictly.