Separate interface for 'Pending' applications

Registered by Brianna Laugher on 2009-05-17

A membership workflow may look like this:

- member makes application [no status]
- application is acknowledged [status Applied]
- application is approved [status Pending]
- dues are received [status Member] - at this point the application leaves the approve_members page and can be found on memberlist.

This might be a misuse of Pending. If so - then a separate status is needed that conveys "approved by the committee, but something else needs to happen before membership is completely confirmed".
And applications with this status should be viewable probably via a separate page, rather than mixed in with the "not yet approved" applications.

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
None
Direction:
Needs approval
Assignee:
None
Definition:
New
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.