Skip to content

Comments

OUT-3160: add an unassigned view in IU and CRM dashboard#1129

Open
SandipBajracharya wants to merge 1 commit intoOUT-3136from
OUT-3160
Open

OUT-3160: add an unassigned view in IU and CRM dashboard#1129
SandipBajracharya wants to merge 1 commit intoOUT-3136from
OUT-3160

Conversation

@SandipBajracharya
Copy link
Collaborator

Changes

  • new separate view for unassigned tasks
  • association tasks are also shown in unassigned view. Not shared as shared tasks require IU as assignee.
  • update tabs copy
  • implement in IU and CRM view

Testing Criteria

Loom

- [x] new separate view for unassigned tasks
- [x] association tasks are also shown in unassigned view. Not shared as shared tasks require IU as assignee.
- [x] update tabs copy
- [x] implement in IU and CRM view
@linear
Copy link

linear bot commented Feb 17, 2026

@vercel
Copy link
Contributor

vercel bot commented Feb 17, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
tasks-app Ready Ready Preview, Comment Feb 17, 2026 11:15am

Request Review

Copy link
Collaborator

@rrojan rrojan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM with a few minor improvements

return filteredTasks.filter((task) => task?.assigneeType?.includes('internalUser'))

case FilterOptionsKeywords.UNASSIGNED:
return filteredTasks.filter((task) => !task.assigneeId)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Still depending on assigneeId was just something we did to prevent changing huge portions of old code.

Moving forward we can do checks like (task) => !(task.internalUserId && task.clientId && task.companyId)

Comment on lines +71 to 74
<div>
<strong>Shared with</strong> is only available
</div>
<div>for tasks assigned to internal users.</div>
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

<br/> or p might be more suitable here unless we have spacing issues

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants