Allow users to define mapping logic for workflows during project merge
Open
Nobody has claimed this yet.
- Dominant language
- Elixir
- Stars
- 296
- Forks
- 86
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 50
Description
When merging 2 projects, how do you know which workflow is which? #3432 assumes that the names are unchanged, but they can change and attributes like positions changed.
- We can have a UI to map workflows by name
- Via api, it could be:
merge [fetch-patients-new] into [get-patients] - Use some other sort of identifier, maybe hashes??
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 by reading issue #3432 and tracing the existing project-merge behavior. Define the workflow-mapping requirements and decide how users or the API identify corresponding workflows; done means the selected mapping approach is specified and supports changed names and attributes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100