Custom input in Job Editor gets deselected after running
Nobody has claimed this yet.
- Dominant language
- Elixir
- Stars
- 296
- Forks
- 86
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 50
Description
Description:
When a user adds a custom input inside the Job Editor and runs the job, the input does not persist — it gets automatically deselected after execution.
This issue makes it difficult for users who rely on custom inputs to remain intact for subsequent runs.
Steps to Reproduce:
- User opens a workflow and navigates to the Job Editor.
- User adds a custom input field.
- User runs the job.
- Observe that the custom input is deselected or removed after the run completes.
Expected Behavior:
The custom input should remain selected and persist after running the job.
Actual Behavior:
The custom input resets or is deselected after each execution.
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 in the Job Editor entry point and reproduce the issue by adding a custom input, running the job, and checking whether it remains selected afterward. The issue names no source file or test, so trace the execution flow from the editor to identify where custom-input state is reset; done means the input remains selected after subsequent runs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100