Bug reporting steps: We get a report or a problem through slack or any other channel channel The engineer will index the task in click-up, along with a description of the problem and any additional information that were provided (screenshots, urls, user story) Add an estimation of time A branch is created based on the github integration The problem is fixed, it's moved into PR/MR. This allows any shareholder that checks the task on the board to understand what is it about New Feature reporting: Feature description (detailed explanation) Include design (Figma link) Split the feature into sub-tasks for granular explanation Priority (if you know this) Estimation of time (if you know this)
0 votes
Vote to help us prioritize this feature
Sign in to join the discussion
Sign in