Issues
- [BE] Do not allow scaling down disk sizeEVEREST-1928
- [BE] Do not allow changing storage size after creationEVEREST-1927
- [Operator] Manual storage scaling for PostgreSQLEVEREST-1926Mayank Shah
- [BE] Implement blacklisting mechanismEVEREST-1925Oksana Grishchenko
- [UI] Update the logout flowEVEREST-1924
- Invalidate session for logged out usersEVEREST-1923Oksana Grishchenko
- Session ManagementEVEREST-1922
- DB version upgrade modal should not allow to select the current versionEVEREST-1921Fábio Da Silva
- [UI] Custom number of nodes for PG is not visible properly in cluster overviewEVEREST-1920Diana Birsan
- [BE] Prevent duplicate netmask entries for external accessEVEREST-1919
- [UI] Prevent duplicate netmask entries for external accessEVEREST-1918tigran.papikyan
- E2E tests - Improve uninstall checksEVEREST-1917Edith Erika Puclla Pareja
- Doc - Enable PSMDB sharding section is misleadingEVEREST-1915rasika.chivate
- [UI] Remove focus state after the user clicks out (different places)EVEREST-1914Diana Birsan
- Missing option and information to add more than one backup storage location for PG backup schedulesEVEREST-1913Fábio Da Silva
- Display storage class on the database overview pageEVEREST-1912tigran.papikyan
- [UI] Empty state briefly appears before first DB cluster is displayedEVEREST-1911Fábio Da Silva
- E2E tests - Add tests for editing existing clusterEVEREST-1910Resolved issue: EVEREST-1910Tomislav Plavcic
- Prevent duplicate IP/Netmask entries for external access in DB clustersEVEREST-1909
- Add support for PSMDB operator v1.20.0EVEREST-1908
- Fix backup storage testEVEREST-1907Resolved issue: EVEREST-1907Tomislav Plavcic
- Mysql - Restore from PITR is unavailable until data is added to the db clusterEVEREST-1906
- Update PITR test with additional caseEVEREST-1905Resolved issue: EVEREST-1905Tomislav Plavcic
- Check advanced database config parametersEVEREST-1904Resolved issue: EVEREST-1904Tomislav Plavcic
- [CLI] Show Everest Version when UninstallingEVEREST-1903
- [UI] Monitoring Endpoint URL HandlingEVEREST-1902tigran.papikyan
- [UI] Backup Bucket Name Trimming IssueEVEREST-1901tigran.papikyan
- Create a documentation section for Edit backup storageEVEREST-1900rasika.chivate
- [BE] Replace REST-based K8S client with controller-runtime.Client in Everest ServerEVEREST-1899Maxim Kondratenko
- Restructure and organise the "DB Status Details" page for better comprehensibilityEVEREST-1898
- [Helm] operator installer job script must use full names of the resourcesEVEREST-1897Mayank Shah
- Helm tests - add support for running tests on release candidateEVEREST-1896Resolved issue: EVEREST-1896Tomislav Plavcic
- [UI] PITR time can't be changed from the last successful backupEVEREST-1895Fábio Da Silva
- Rework monitoring usage in release testsEVEREST-1894Resolved issue: EVEREST-1894Tomislav Plavcic
- Release tests - fix PSMDB sharding test and monitoring instancesEVEREST-1893Resolved issue: EVEREST-1893Tomislav Plavcic
- Sharding QA for FB PSMDB v1.19.1EVEREST-1892Manish Chawla
- "Create Database" Button Does Not Work When Database Name is the Same During Restore, no error messageEVEREST-1891Diana Birsan
- [UI] Number of Proxies changes from 'X' to '1' while creating a mysql db clusterEVEREST-1890Fábio Da Silva
- [UI] Display Nodes per Shard in Overview pageEVEREST-1889Diana Birsan
- [UI] [Storybook] CopyToClipboardButtonEVEREST-1888Diana Birsan
- Documentation correctionEVEREST-1887Santo Leto
- Fix cluster deletion in UI sharding testEVEREST-1886Resolved issue: EVEREST-1886Tomislav Plavcic
- OpenShift certificationEVEREST-1885Tomislav Plavcic
- Add support for PSMDB operator v1.19.1EVEREST-1884Diogo Recharte
- Upgrade CI workflow runner imagesEVEREST-1883
- [Research] Session managementEVEREST-1882Oksana Grishchenko
- [UI] Allow storage scaling for PostgreSQLEVEREST-1881Diana Birsan
- [API] Allow storage scaling for PostgreSQLEVEREST-1880Mayank Shah
- [UI] Allow storage scaling for MongoDBEVEREST-1879Diana Birsan
- [API] Allow storage scaling for MongoDBEVEREST-1878Mayank Shah
50 of
We couldn't connect to that issue
Make sure that this issue actually exists in that project. If it does, try again in a few minutes. If you still can't link to the issue, contact your Jira admin.