Closed
Milestone
expired on Aug 20, 2020
3.19
Unstarted Issues (open and unassigned)
0
Ongoing Issues (open and assigned)
0
Completed Issues (closed)
120
- Create quick-start video for setting up Code Intelligence in CI/CD
- gitserver: Could not resolve host: github.com
- Optimize reposourceCloneURLToRepoName
- Update ExternalServicesStore.List to support pagination
- monitoring: index_queue_growth_rate firing without hitting threshold
- monitoring: change relevant hard threshold alerts to ratio-based alerts
- Treat trailing parentheses in new parser similar to old parser
- Remove Campaign.Branch field
- Add sync time columns to the external_services table
- redis-cache segfault in single server dogfood instance
- ChangesetConnectionResolver.PageInfo needs to respect repository permissions
- Update call sites of ExternalServicesStore.List to avoid application-level aggregation
- Do not expire the PreviousChangesetSpec of a changeset
- monitoring: difficult to understand 7d provisioning panel
- Research language usage among customers and projects
- RFC 199: Build indexer service
- Update ExternalServicesStore.List to allow filtering by user
- Migrate existing campaigns' names to the new slug-like format
- RFC 199: Index queue API
- RFC 199: Index queue client
- Replace commented-out portion of TestCampaigns in resolvers/resolver_test.go with more extensive test that tests ApplyCampaign
- It is not called out clearly enough in docs that initial permission synching may take several hours
- Change testChangesetResponse in permissions_test.go to include publication status, error and reconciler state
- Implement missing methods in changesetResolver
- RFC 199: Expose internal routes for the indexer
- Implement the "processing?" checks in CloseCampaign/DeleteCampaign
- Allow customers to export their campaigns before upgrading to 3.19
- add syntax highlighting for NOT
- Write a migration that deletes all existing campaigns/changesets when upgrading to 3.19
- Implement the changesetsConnectionStatsResolver
- Implement combined diff stat on changesetspec resolver
- Implement campaignForSpec query resolver
- Implement API to return all involved unsers in a campaign
- Implement GraphQL API that allows to fetch campaigns by namespace
- Formalize managed instances
- Migrate terraform state to GCP
- 3.19 release tracking issue
- Query parser migration
- Add tags to Git-extras extension
- Duplicate results in or-operator merge operation
- Change campaign/campaignSpec URLs to include namespace and fit new schema
- deploy-sourcegraph: prometheus missing in `up` metric
- Persist & accept changeset filter params in the URL
- Record enough information on a campaign to return all involved users in a campaign
- Design a GraphQL API that allows us to make use of the cached diff stats on ChangesetSpecs and Changesets
- Design a GraphQL API that allows us to list campaigns on user and organization pages
- Implement the createCampaign mutation and necessary API fields
- Design the GraphQL API needed to show all users involved in a campaign
- Design a GraphQL API that would allow us to show either the "Update campaign" or "Create campaign" button on the apply page
- Low contrast on search examples
- panic in glob conversion function
- sourcegraph/server:3.18 provisioning indicators panel missing
- monitoring: no easy way to trigger alerts for testing
- Create a dedicated token object that can be used as part of the per deployment encryption
- Generate unique keys on a per deployment basis
- src-expose is first class
- Log 3 click events for new features on Search Homepage and Repo Page
- src-cli: Implement new campaigns workflow
- monitoring: generate alerts as native prometheus alerts, let alert_count depend on alert rules
- Cloud: 3.19 Tracking issue
- Campaigns 3.19 Tracking issue
- auth: password reset page does not respect `auth.minPasswordLength`
- Make license check not fail when our node version is upgraded
- Create web content stylesheet
- Web: 3.19 tracking issue
- ci-db-backcomp.sh is not branch-aware
- Determine state of LSIF-java
- Security: 3.19 Tracking issue
- Key Rotation Should Re-encrypt objects at rest
- Implement a DBEncryptionStore supporting the database back end
- Search 3.19 Tracking issue
- Create a dedicated token object for returning the raw and masked tokens
- monitoring: better advice for alerts that do not have an entry in alert_solutions
- add negation/NOT for file contents
- monitoring: link back to grafana service dashboards in alert notifications
- campaigns: GitLab webhook support
- Sourcegraph OSS user settings not accessible
- Separate Secrets Access from Secrets Storage
- Implement Schema for Secrets Storage
- frontend: hard errors alerts as ratio/percentage instead of absolute-value
- Query definition and hover provider so we can correctly badge results
- Code Intelligence 3.19 Tracking issue
- monitoring: migrate existing alert rules to generator
- Implement better nearest commit queries
- Visible at tip calculation is racy
- Remove cloneInProgress option from Repositories API
- deploy-sourcegraph-dhall: symbols: implement generate reading from config
- deploy-sourcegraph-dhall: searcher: implement generate reading from config
- deploy-sourcegraph-dhall: repo-updater: implement generate reading from config
- deploy-sourcegraph-dhall: replacer: implement generate reading from config
- deploy-sourcegraph-dhall: jaeger: implement generate reading from config
- deploy-sourcegraph-dhall: precise-code-intel: implement generate reading from config
- deploy-sourcegraph-dhall: query-runner: implement generate reading from config
- deploy-sourcegraph-dhall: postgres: implement generate reading from config
- deploy-sourcegraph-dhall: github-proxy: implement generate reading from config
- deploy-sourcegraph-dhall: cadvisor: implement generate reading from config
- Better account for peaks / max resource usage in monitoring
- Approved: Proposal: RFC-189: Support per-team alerts and on-call rotations
- Distribution: 3.19 Tracking issue
- Add CTAs and what cloud searches message
- Rename default branch to `main`
- Add CLI option to update a campaign
- Remove Gitolite blacklist configuration option
- Bitbucket Server native integration prevents file header text from wrapping
- Browser ext links to Sourcegraph don't appear on repos when branches specified
- Support or-expressions for repo: and file: parameters
- Backend: New campaign flow
- Frontend: New campaigns flow
- Remove on-demand implementation of permissions
- Add Repository / Update Repository actions unclear
- Decompose and/or add more tests for CampaignDetails
- mail package deprecated
- Ability to disable SMTP TLS verification
- Sourcegraph.com - add redis-store & precise-code-intel-bundle-manager snapshotting
- Unable to perform a literal search with a query that contains a `:`
- Support unix-style globbing patterns for search field values
- Add NOT as syntactic sugar for negatable fields
- Creating larger campaigns using src-cli fails with 413
- Dogfood the monitoring we ship with Sourcegraph
- Send new users (added by site admin) the password reset URL over email
Loading
Loading
Loading