Skip to content

Stop days_open at completed_at for completed tasks - #60

Open
porkedchop wants to merge 1 commit into
fivetran:mainfrom
porkedchop:fix/days-open-completed-tasks
Open

porkedchop wants to merge 1 commit into
fivetran:mainfrom
porkedchop:fix/days-open-completed-tasks

Conversation

@porkedchop

Copy link
Copy Markdown

Resolves #59

Please provide your name and company

Bishop Kammeraad

Describe what this PR changes and how it addresses the linked issue or feature request.

In int_asana__task_open_length, open_until is now a SQL case when task.is_completed then task.completed_at else <current timestamp> end instead of a Jinja conditional on the string 'task.is_completed', which was never true. days_open and the two days_since_*_assignment columns now stop at completed_at for completed tasks.

How did you validate the changes introduced within this PR, and what warehouse did you use for testing?

DuckDB with the integration test data. days_open for task 1138074657603006 (created 2019-09-02, completed 2019-09-18) goes from 2604 to 16. dbt build passes.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

days_open runs to the current date for completed tasks

1 participant