Asana import skip completed
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 59.6k
- Forks
- 5.8k
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 49
Description
Asana import is perfect way to track issues from Asana which is used by our team and I hate it :D
Problem is that there is no filter for items. Main reason is that asana Completed status is not typical status so it is imported even if there are completed issues.
Problem is mainly for first import and historic data. Asana import will fetch too many records, import them all and even keep them as open since completed is no status.
Contributor guide
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 locating the Asana import entry point and the mapping for Asana completion. Reproduce an import containing completed historical items; done means completed items are skipped rather than imported as open, especially during the first import.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100