Allow users to export History
Open
Nobody has claimed this yet.
- Dominant language
- Elixir
- Stars
- 296
- Forks
- 86
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 50
Description
- A button on the history page that makes an export request when clicked
- If the storage is not configured by providing the right API keys, the feature should be disabled and the export button should show a message that “Storage credentials missing or not properly configured”
- On Success, there is a toast that confirms that says Export in progress
- If there is an error, the toast should communicate the error
- Apply filters to the export functionality based in workflow, status, received date, last activity, and search string
Because this runs as a background process, we need to make sure we can associate this with the project
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
Start from the history page and trace how it makes requests and applies workflow, status, date, activity, and search filters. Implement the background export flow with project association, storage-credential handling, and success or error toasts; done means each checklist behavior works and unavailable storage disables the export action.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- full-stack
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100