CodeForPhilly / CodeForPhilly/stately

Feature: Scheduled actions

Open
#27 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
22
Forks
5
PR merge metrics
No merged PRs in 30d

Description

I don't think we need this for MVP, but many workflows will need something like this for practical use.
- When an indebtedness check is awaiting the submitter to "resubmit" info for more than 30 days, mark it "cancelled."
- When a FOIA request hasn't been fulfilled in 5 _business_ days, send an email requesting an extension
- When a contract has been in a step for more than 2 weeks, send a reminder to the assignee

Just leaving this issue here for when it's time.

Contributor guide

No contributing guide indexed for this repository

Research direction

The issue names no files, tests, or entry points. Start by mapping how workflows represent waiting states and scheduled notifications, then clarify the three proposed time-based behaviors, including business-day handling and cancellation rules. Done should be defined as implemented behavior for the agreed scenarios with tests covering each timing rule.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.