Attachments, plan approval, and clearer task progress
Give Rubic supporting files, approve the approach before coding begins, and follow revisions and progress from one task.
Attach the context Rubic needs
Upload supporting files to tasks, epics, and chat messages. Attachments stay available when the work is created, revisited, or discussed with the team.
Approve the plan before development starts
Tasks can now wait at a dedicated plan approval step. Review the proposed approach, request a revision, or approve it before Rubic changes the code.
Follow revisions and progress inside the task
- See development progress while Rubic works through the plan.
- Keep replaced plans visible without confusing them with the current approach.
- Follow status changes and important events from the task overview and activity views.
- Use generated task and epic titles to keep larger backlogs easier to scan.
Keep notifications focused on the work
Inbox updates are grouped by task or epic, and blocked development can notify the team by email so action requests do not get lost among routine updates.