Project

General

Profile

Actions

roos-fs tasks #316

open

Statuses and Status change for Leads

Added by Vadim Golub 9 months ago. Updated 5 days ago.

Status:
Closed
Priority:
Low
Start date:
08/21/2025
Due date:
% Done:

0%

Estimated time:
16:00 h

Description

We need the ability to assign and manage Lead status to improve tracking and pipeline visibility.
Status must be visible and usable in the Leads table, editable in the Lead Details screen, and every change must be tracked in Activity Log.
All new Leads start with status New.

Developer Context:
To view Lead, head into the Leads Menu and pick the Lead:

Required Implementation:

Leads table

  • Add a new Status column.
  • Enable sorting and filtering by Status (works with existing pagination/search).

Lead Details

  • Add a Status dropdown to assign/change a lead’s status.

  • Placement: inside the Lead Information block, below the existing fields and left-aligned with them.

  • Available statuses: New, Engaged, Follow up & close, Closed lost, Follow-up due; default = New.
    - New Leads are created with status New.

Activity Log

  • On every status change, append an entry:
    “Status changed from {Old} to {New} by {User} at {Timestamp}”.

Expected Behavior / Acceptance Criteria

  • Status is shown in the Leads table and can be sorted/filtered.
  • In Lead Information, users can change Status via the dropdown.
  • Every status change is recorded in Activity Log with old/new values, actor, and timestamp.
  • New Leads are created with status New.
  • Other Lead features continue to work as before.

Files

Actions #1

Updated by Vadim Golub 9 months ago

  • Description updated (diff)
Actions #2

Updated by Anton Obolientsev 8 months ago

  • Status changed from Open to In progress
Actions #3

Updated by Anton Obolientsev 8 months ago

  • Estimated time set to 8:00 h
Actions #4

Updated by Anton Obolientsev 8 months ago

  • Status changed from In progress to In review
Actions #5

Updated by Anton Obolientsev 8 months ago

  • Status changed from In review to Deployed (QA)
Actions #6

Updated by Vadim Golub 8 months ago

  • Status changed from Deployed (QA) to Open
Actions #7

Updated by Anton Obolientsev 8 months ago

  • Status changed from Open to In progress
Actions #8

Updated by Anton Obolientsev 8 months ago

  • Estimated time changed from 8:00 h to 16:00 h
Actions #9

Updated by Anton Obolientsev 8 months ago

  • Status changed from In progress to In review
Actions #10

Updated by Anton Obolientsev 8 months ago

  • Status changed from In review to Deployed (QA)
Actions #11

Updated by Vadim Pariev 8 months ago

test result not OK

Every status change is recorded in Activity Log with old/new values, actor, and timestamp. - NOT IMPLIMENTED

Actions #12

Updated by Vadim Pariev 8 months ago

  • Status changed from Deployed (QA) to QA Failed
Actions #13

Updated by Anton Obolientsev 8 months ago

  • Status changed from QA Failed to Deployed (QA)
Actions #14

Updated by Vadim Pariev 8 months ago · Edited

test result not ok
the statues are rendered with the _ sign
Expected that the status would be rendered without it as it is in the selected field

Actions #15

Updated by Vadim Pariev 8 months ago

  • Status changed from Deployed (QA) to QA Failed
Actions #16

Updated by Anton Obolientsev 8 months ago

  • Status changed from QA Failed to Deployed (QA)
Actions #17

Updated by Vadim Pariev 8 months ago

  • Status changed from Deployed (QA) to Ready for Deployment (prod)
Actions #19

Updated by Vadim Pariev 8 months ago

  • Status changed from Ready for Deployment (prod) to Closed
Actions #20

Updated by Albert Katasonov 5 days ago

  • Project changed from 8 to Roos-fs-ZIP
  • Category deleted (Task)
Actions

Also available in: Atom PDF