List view
- No due date•1/1 issues closed
- No due date•4/4 issues closed
https://github.com/status-im/status-desktop/issues/18029
No due date•328/328 issues closedhttps://github.com/status-im/status-desktop/issues/17966
No due date•155/155 issues closed- No due date•3/3 issues closed
https://github.com/status-im/status-desktop/issues/17170
No due date•125/125 issues closedhttps://github.com/status-im/status-desktop/issues/17165
Due by February 28, 2025•247/247 issues closed- Due by May 17, 2024•1/1 issues closed
- Due by April 11, 2024•59/59 issues closed
- No due date•130/130 issues closed
- Due by February 14, 2024•27/27 issues closed
- Due by November 1, 2024•210/210 issues closed
- Due by November 23, 2023•25/25 issues closed
A point milestone where we focus the Messaging and Communities team 100% on bug fixing, stabilisation, reliability and finishing any unfinished items from 0.15 **1. Fix bug and stabilise Communities and Messaging functionality** **2. Reduce size of community description metadata** - better compressions, less duplication **3. Use data sync layer (or other mechanism) to improve community description reliability** - Every time a new user joins the community, the Control Node updates and signs the description. - Random back off to stop it being too chatty **4. Continue work on profile showcase ** --- Wallet --- - Improved handling of community minted tokens: Community Asset and NFT designs for Asset screens - Token visibility management - Minor updates to Asset screens - Continue work on WalletConnect integration - Database re-encryption flows
Due by December 7, 2023- Due by September 1, 2023•20/20 issues closed
- Due by July 31, 2024•559/559 issues closed
- Due by May 30, 2024•218/218 issues closed
- Due by August 4, 2023•2/2 issues closed
- Due by July 28, 2023•3/3 issues closed
- Due by June 30, 2023•27/27 issues closed
## Messaging & Communities team **1. Continue to fix bugs and stabilise chat and communities functionality as top priority** - includes any issues found during dogfooding **2. Status Communities / Discord bridge** - Ensure bridge works with token gated communities (e.g. permission is set at the community level that requires a token to be held to be a member of that community) - Ensure bridge works with token gated channels - On the Status Desktop side, individual messages from Discord are displayed as individual messages with Discord usernames **3. Continue work on profile showcase** **4. Ability to mark a token gated channel as 'hidden'** - A token gated channel that's marked as 'hidden' is only visible to community members that have the requisite tokens to access this channel - Design for this is completed **5. Fix outstanding bugs related to Discord import and community history archive service** - Complete Boris's unfinished items **6. Community encryption change to support KeycardPro/Status Web** - Patryk on point, to work with Michelle and Cammellos **7. Ability to select any Collectable that exists when setting up a Community permission** - So communities aren't limited to just using collectables the community itself has minted - Designs already done for this I think, this functionality was discussed with MichaelC last year **8. Fix user flow bugs, better handle edgecases and other improvements** Note: many of the issues below are now scheduled for future releases *High priority* - https://github.com/status-im/status-desktop/issues/13034 - https://github.com/status-im/status-desktop/issues/8257 - https://github.com/status-im/status-desktop/issues/11649 - https://github.com/status-im/status-desktop/issues/11538 *Medium priority* - https://github.com/status-im/status-desktop/issues/13378 - https://github.com/status-im/status-desktop/issues/13393 - https://github.com/status-im/status-desktop/issues/13397 - https://github.com/status-im/status-desktop/issues/12809 - https://github.com/status-im/status-desktop/issues/11948 - https://github.com/status-im/status-desktop/issues/9807 - https://github.com/status-im/status-desktop/issues/8565 - https://github.com/status-im/status-desktop/issues/8349 - https://github.com/status-im/status-desktop/issues/11550 *Low priority* - https://github.com/status-im/status-desktop/issues/10160 - https://github.com/status-im/status-desktop/issues/8481 - https://github.com/status-im/status-desktop/issues/13379 - https://github.com/status-im/status-desktop/issues/11992 - ~~https://github.com/status-im/status-desktop/issues/9700~~ moved to 2.31 (part of the milestone goals for chat input) - https://github.com/status-im/status-desktop/issues/9698 - https://github.com/status-im/status-desktop/issues/8975 - https://github.com/status-im/status-desktop/issues/8349 ~~- https://github.com/status-im/status-desktop/issues/11519~~ moved to 2.31 (part of the milestone goals for chat input) *Epic tags and burnup charts for all issues above* - [E:Communities UX fix - High](https://status.app/insights/epics/E:Communities%20UX%20fix%20-%20High) - [E:Communities UX fix - Medium](https://status.app/insights/epics/E:Communities%20UX%20fix%20-%20Medium) - [E:Communities UX fix - Low](https://status.app/insights/epics/E:Communities%20UX%20fix%20-%20Low) - [E:Messaging UX fix - High](https://status.app/insights/epics/E:Communities%20UX%20fix%20-%20High) - [E:Messaging UX fix - Medium](https://status.app/insights/epics/E:Messaging%20UX%20fix%20-%20Medium) - [E:Messaging UX fix - Low](https://status.app/insights/epics/E:Communities%20UX%20fix%20-%20Low) [Spreadsheet of all of these issues with Figma links](https://docs.google.com/spreadsheets/d/12QKBFvNwjoI8l8w-Ry5zbch3HH643-EpbFcyDrFP59E/edit#gid=0) ## Wallet Team **1. Fixing bugs, stabilisation of existing functionality** - 0.17 will be our 1st or 2nd public beta release, so squashing bugs is the top priority - Includes fully testing Keycard on Windows and fixing any outstanding Windows Keycard issues **2. Collectables - support graceful support of edgecases and improvements** - Ben to provide designs and links to all associated issues **3. Other wallet improvements and improved edgecase support** *High priority* - https://github.com/status-im/status-desktop/issues/13377 - https://github.com/status-im/status-desktop/issues/13404 - https://github.com/status-im/status-desktop/issues/13399 - https://github.com/status-im/status-desktop/issues/13382 - https://github.com/status-im/status-desktop/issues/13380 - https://github.com/status-im/status-desktop/issues/13389 - https://github.com/status-im/status-desktop/issues/13391 *Medium priority* - https://github.com/status-im/status-desktop/issues/13405 - https://github.com/status-im/status-desktop/issues/13381 - https://github.com/status-im/status-desktop/issues/13384 - https://github.com/status-im/status-desktop/issues/10956 - https://github.com/status-im/status-desktop/issues/10927 *Low priority* - https://github.com/status-im/status-desktop/issues/13386 - https://github.com/status-im/status-desktop/issues/12618 *Epic tags and burnup charts for all issues above* - [E:Wallet UX fix - High](https://status.app/insights/epics/E:Wallet%20UX%20fix%20-%20High) - [E:Wallet UX fix - Medium](https://status.app/insights/epics/E:Wallet%20UX%20fix%20-%20Medium) - [E:Wallet UX fix - Low](https://status.app/insights/epics/E:Wallet%20UX%20fix%20-%20Low) [Spreadsheet of all of these issues with Figma links](https://docs.google.com/spreadsheets/d/12QKBFvNwjoI8l8w-Ry5zbch3HH643-EpbFcyDrFP59E/edit#gid=1965038978) **4. Finish improved 'saved accounts' functionality and 'share address' dialogue**
Due by April 3, 2024•322/323 issues closed- Due by May 19, 2023•7/7 issues closed
- minting fee calculation fix - community nav fix - fix waku sync/fetch - intel build fix
Due by April 21, 2023•3/3 issues closed- Due by April 7, 2023•49/49 issues closed
## Messaging & Communities team **1. Finish anything that wasn't completed in the previous 0.14 cycle** - And fix bugs as usual. We need to keep tech. debt at a roughly fixed level as we grow out functionality, can't let it accumulate! ;-) **2. Tokenisation of community ownership** - Work needed already evaluated in spike. Community and 'Channel in a Community' URLs don't need to be signed if this will present problems. Patryk to work on this as a continuation of the spike already done. - See priority 4 below, as this also has some implications for the tokenisation of community work. **3. Community tokens visible in wallet when received by user who is not a member of that community** - Solution obvs. needs to be fully decenteralised and permissionless - Perhaps whenever a community token is A) sent from a Status Wallet to another user or B) airdropped by a community or C) retailed by a community, a M2M (invisible to the user) Waku message should be sent to the recipient's *ethereum address*? - This message could either: A) contain the metadata for the token B) tell the user that they have received token, and to check the metadata in either another Waku channel where Control Nodes periodically post Metadata OR check the metadata embedded in the token contract (embedding metadata in the token contract might be a better idea?). - The token metadata stored in the token contract is signed by the Community's private key to ensure authenticity. When the community's private key changes due to ownership of a community being transferred or due to the control node being moved, a transaction must be made to update this metadata so it is signed by the community's new private key. - See here for how a Waku message can be sent to and Ethereum address https://rfc.vac.dev/spec/20/ **4. Discord history import into a single channel in an existing community** - Pay off any Discord history import service tech. debt first - Then build the import into a single channel functionality, designs for this are already complete **5. UI for community owner to enable manual Waku static shading for their community** - This will be off by default in 0.15 - This UI is only for the Owner of a community (not TokenMasters or Admins) - Figma designs are here https://www.figma.com/file/qHfFm7C9LwtXpfdbxssCK3/Kuba%E2%8E%9CDesktop---Communities?type=design&node-id=37242%3A222352&mode=design&t=rw6q6NQYmiz3rSn2-1 ## Wallet Team **1. Finish anything that wasn't completed in the previous 0.14 cycle** - And fix bugs as usual. We need to keep tech. debt at a roughly fixed level as we grow out functionality, can't let it accumulate! ;-) **. Sending Community created tokens to Status users who are not members of that community** - See priority 4) in the messaging priorities list above. **3. Send NFT functionality** **4. Updated wallet settings with keypair syncing**
Due by November 9, 2023•288/288 issues closedPriorities **in priority order** for the 0.13 milestone: **1. Finish items started in 0.12** - Complete any outstanding issues related to pairing (for syncing) - Igor - Implement the 'Admin' role (issue #10114) - Mykhailo - Any remaining work to pay off tech. debt related to mutual contacts - Mishka - When creating/editing token based permission, ability to search for and selecting Collectables from OpenSea - MichaelC **2. Channel token permissions** - Create, edit and delete channel token permissions in the permissions admin screens - This includes the "no tokens required to view this channel" permission - All user facing channel token permissions functionality e.g. what happens when a user tries to access a token gated channel they don't have the required tokens to access, what happens when a user only has permissions to view a channel, etc... - If a community is an open (not token gated at the community level) community, if a channel is token gated AND if **no** "no tokens required to view this channel" permission for that channel exists, then the channel should be automatically encrypted. If token gating is removed from a channel, the channel should become unencrypted. **3. DB perf improvements** - https://www.notion.so/Database-related-performance-1dbaa7ea894c461d885e55676683be07 - Alex and Patryk to work on this, with help from Lukáš **4. Update app to use new 'Share URL' formats** - add functionality to status-go to generate the new 'Share URL' formats for sharing links to: User Profiles, Communities, Channel inside a Community (issue https://github.com/status-im/status-desktop/issues/10851) - Update everywhere a user can share a URL from to use the new URL format (issue https://github.com/status-im/status-desktop/issues/10852) - New/updated URL unroll designs for inside chat, including specific unrolls for the new User Profile, Community and Channel inside a Community URLs (issue https://github.com/status-im/status-desktop/issues/10585) - Ability to share a URL that points to a specific channel in a community (issue #10160) - Update all address inputs to accept a user pasting a 'share URL' into the input (in addition to being able to input the raw address). This includes: Start new chat input, send contact request input in Settings, the import community key input, etc... - Update Status Desktops URL handler so that if Status is installed on a computer, when a user clicks on a Status 'Share URL' the app is launched (if not already running) and after signing in the user is automatically taken to the entity the Share URL represented inside the app. e.g. if a user clicks on a URL for a Status Community, the user should be taken to the home screen for that community inside the Status App **5. Mint Assets functionality** - Also includes some small improvements to the mint Collectables functionality - Noelia, GravityBlast **6. Profile showcase backend** **--- For the Wallet team ---** tldr; continue building out Ben's wallet designs 1. Complete any outstanding development related to the activity screens 2. All accounts overview screens 3. New settings screens 4. Implement 'imported key and account' syncing and transfer between devices
Due by June 16, 2023•245/245 issues closed- Due by February 10, 2023•10/10 issues closed
- Due by January 13, 2023•48/48 issues closed
## Messaging & Communities team **1. Fix bug and stabilise Communities and Messaging functionality** **2. Reduce size of community description metadata** - better compressions, less duplication **3. Use data sync layer (or other mechanism) to improve community description reliability** - Every time a new user joins the community, the Control Node updates and signs the description. - Random back off to stop it being too chatty **4. Continue work on profile showcase** ## Wallet Team **1. Complete support for Community minted assets** **2. Complete token visibility management screens** **3. Continue working on WalletConnect support** **4. Minor updates to Asset screens** **5. Continue fixing bugs, making optimisations and keeping tech debt low**
Due by January 31, 2024•301/301 issues closedmilestone to adress some important issues found in 0.8.0
No due date•10/10 issues closed- Due by November 18, 2022•15/15 issues closed
- Due by October 7, 2022•34/34 issues closed
Milestone cycles: [Cycle 1](https://github.com/status-im/status-desktop/issues?q=is%3Aopen+is%3Aissue+milestone%3A0.14+label%3AC1): 7 July [Cycle 2](https://github.com/status-im/status-desktop/issues?q=is%3Aopen+is%3Aissue+milestone%3A0.14+label%3AC2): 28 July [Cycle 3](https://github.com/status-im/status-desktop/issues?q=is%3Aopen+is%3Aissue+milestone%3A0.14+label%3AC3): 18 August **--- Main focus ---** **1. Token permissions to enable control of community smart contracts** - Before a community founder can use any of the community token admin functionality, they first have to deploy Owner and Token Master contracts. - This work involves: new empty state screen for Mint and Airdrop tokens (before current empty state screen is revealed), new flow for deploying the community's Owner and Token Master contracts in a single step, a fixed uneditable permission giving anybody who holds the Token Master token admin rights for the community should be automatically created. - Only the holder of the single Owner token can access the Token Master airdrop, remote destruct, and view holders functions. Anybody who holds the Token Master token can access all token admin options, excluding those related to the Token Master token itself, as well as being and Admin of the community. - This will all be explained in more detail in the designs. Backend Epic: https://github.com/status-im/status-desktop/issues/11249 **2. Update Community Admin home screen inc control node transfer and associated dialogues** - Remove ability for a Owner to leave a community on the computer that's running as that community's control node - Community Admin home screen cleanup (inc. adding at least one of the three graphs, whichever is easiest to implement). - Graph issue: https://github.com/status-im/status-desktop/issues/11152 - Community overview: https://github.com/status-im/status-desktop/issues/11278 **3. Ability for user to select & manage accounts shared with each community control node** - This item is quite a bit of work - Touches Community settings, as well as all of the community join flows - Backend issues: - Join API: https://github.com/status-im/status-desktop/issues/11154 - Edit API: https://github.com/status-im/status-desktop/issues/11153 **4. Encryption for token gated channels that are inside Open (not token gated) communities** [#10998](https://github.com/status-im/status-desktop/issues/10998) **5. Final screens and bits and bobs needed prior to public beta** - Modal that's shown every time after login, reminding user's that Status Desktop is in Beta [#11044](https://github.com/status-im/status-desktop/issues/11044) - The bug with 'requests to join' a community not constantly arriving, or sometimes arriving after a delay, must be fixed. [#8264](https://github.com/status-im/status-desktop/issues/8264) - Anything that didn't get completed in 0.13 related to new share URL format - All the outstanding bugs and small items that got pushed into the 0.14 milestone. **--- Things that we SHOULD NOT work on during the 0.14 cycle ---** - Messaging and UI teams shouldn't work on perf. in 0.14 (but Wallet team should!) - Anything big mutual contacts related, other than fixing small bugs we find like #10497 #10498 #11120 #11121 (hopefully this functionality working good enough now!) **--- Wallet Team ---** 1. Finish any outstanding work related to Activity screens (top priority - aim to have complete by July 14th) 2. Updated Wallet Settings screens UI inc. account syncing functionality *Synced information should immediately be reflected in the UI after it is received (sometimes synced info is currently only displayed after the next app restart, this needs to be fixed)* 3. Wallet performance and memory consumption optimisations 4. Fix bugs, clean up loose ends (to get things in a good state before the work on the Mobile wallet starts)
Due by August 18, 2023•332/332 issues closedPriorities **in priority order** for the 0.12 milestone: **1. Improve performance** - Focus on eliminating any UI freezes when the user clicks on something and the app does not display an immediate response. Target: the app should ideally respond to all user input within 50ms, but let's start with identifying the longest UI freezes and trying to fix the worst UI freezes first. - Speed and responsiveness of switching between community channels, and 1on1 and ad-hoc group chats is particularly important, especially for channels and chats that contains a lot of history. We should aim for about 250ms delay in the *worst* case if possible. Having a lot of history in a channel should not slow channel switching down. - DB perf optimisations. - Move things to async and off main thread - See Alex's great profiling work for possible tasks (Alex to continue focusing on perf. for this release cycle) - "user facing performance in everyday app usage" is the top priority, but any task that improves performance is worthwhile **2. Finish development of token based functionality from 0.11** - Optimise No. queries made by owner node when checking member tokens (Pascal) - Community encryption should automatically switch on/off depending on community permissions (issue #9942) - Implement the 'Admin' role (issue #10114) - Airdrop to community members (in addition to addresses) - Optimise gas required by collectable minting smart contracts (issue #9943, GravityBlast) --- After collectable minting gas optimisation is complete, start work on Asset minting contracts (GravityBlast) - Complete token remote destruct UI - Remove 'Community Permissions Settings', 'Community Tokens' and 'Discord Import Tool' feature flags (issue #10115) - Thoroughly test, and fix all bugs found. - Anything else related to Community level token permissions, collectable minting, airdropping, and remote destructing that didn't make it into 0.11 **3. Finish implementing the ability for Community Owners and Admins to drag and drop channels and categories into different orders** **4. Finish anything related to the initial pairing process for syncing that wasn't completed in 0.11** (Igor) **5. Improve Mutual Contacts functionality to improve reliability and pay off tech debt** (Mishka) **6. Complete Community Directory Curation dApp integration inc. Featured functionality** (Patryk) **7. Backend for the Profile Showcase** **8. Identity Verification** (required for 'Profile Showcase') **9. Fix bugs, bugs and more bugs!** - Esp. find the cause of and fix the longstanding bug of some 'requests to join' not arriving for hours/days after they were sent! - Many 'fit and finish' bugs for the UI team **--- For the Wallet team ---** 1. Continue feature development inc. kicking off development of the activity screens 2. 'All accounts' section. The ability to return all tokens owned by the user in all accounts (excluding watch only accounts) is also required for the Showcase functionality 3. Widen scope of 'backup to waku' and 'syncing' so that all relevant Wallet user state is backed up and synced between devices 4. Continue to ensure Wallet functionality is performant. 5. Fix wallet bugs
Due by May 5, 2023•176/176 issues closedCommunities: - Token Based Functionality General: - User Profile showcase
Due by March 24, 2023•193/193 issues closedGeneral: - Memory Usage Improvements (part 3) General: - Account Syncing
Due by January 27, 2023•95/95 issues closedGeneral: - Memory Usage Improvements (part 2) Chat: - Fixes & Improvements to ENS support - Fixes & Improvements to chat input Communities: - Communities MVP admin functionality Wallet: - Second bridge integragrated - Bridge UI - Multi Transaction view + notification - Latency improvement for fetching data in the wallet - keycard Import or restore a Keycard via a seed phrase Migrate an exsiting account from Keycard to Status Desktop UI for the keycard settings in case user has set up a keycard
Due by December 19, 2022•175/175 issues closedFeatures: General: - Memory Usage Improvements (part 1) Chat: - Activity Center - New Profile Modal - Contacts & Profiles - Identity Verification Communities: - Community Portal - New Join Workflow - Encrypted Communities - Import Tool Wallet: - Send - Initial Bridge integration, allow to send eth/token to best route and advanced view - Test: - Wallet test fully automated and working - Asset - Token view graph - Keycard - onboarding flow and login revision - Rename Keycard - Change PIN - Create a 12-digit personal unblocking key (PUK) - Create a new Pairing Code - UI for the keycard settings in case user has set up a keycard Automation: - docker setup to test message reliability & message fetching - Use local mailserver in the CI - Automation: Edit group chat name and cleanup group chat creation scenario - Automation: Can invite members to a community - Automation: Can create a contact request - Automation: Can create a 1 on 1 chat with a mutual contact - Automation: Can create a 1 on 1 chat with a mutual contactCan delete a message from another member if admin - Automation: Can create a 1 on 1 chat with a mutual contactCan reply to a message in a community channel - Wallet scenario: User adds a watch only account - Wallet scenario: User generates a new account from wallet - Wallet scenario: User imports a private key - Wallet scenario: User imports a seed phrase - Wallet scenario: User deletes a generated account - Wallet scenario: Can see collectibles for an account - Wallet scenario: User can edit the default wallet account - Wallet scenario: User can toggle network and see balances UI Storybook: - Initial Storybook app - Component Events Tracking/logging - Component properties/models Editing - Community Portal Section - Community Portal Card Component - ProfilePopup Component C++: - status-go wrapper: Login - status-go wrapper: Account Creation - status-go wrapper: get Chats
Due by November 7, 2022•233/233 issues closed- Due by September 29, 2022•13/13 issues closed
- Due by May 17, 2022•29/29 issues closed
- Due by September 12, 2021•6/6 issues closed
- Due by September 12, 2021•7/7 issues closed
- Due by September 12, 2021
- Due by September 5, 2021•8/8 issues closed
- Due by September 5, 2021•10/10 issues closed
- Due by September 5, 2021•1/1 issues closed
- Due by August 15, 2021
- Due by August 15, 2021
- Due by August 15, 2021
- Due by August 8, 2021