Investigate UX and tech limitations of deleting Jobs in the middle of workflow
Open
Nobody has claimed this yet.
- Dominant language
- Elixir
- Stars
- 296
- Forks
- 86
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 50
Description
Via Justin: https://openfn.slack.com/archives/C0394D0GBUN/p1694628971132659
Noting here for myself:
- When deleting a job in the middle, offer user the ability to choose to remove all subsequent jobs or just that single one (like Hubspot)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file, test, or entry point is named. Start with the linked Slack discussion and review the current job-deletion flow, then document the UX and technical limitations of deleting a job mid-workflow. Done means the supported deletion choices and their scope are clearly defined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- full-stack
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100