asana

• Team parameter removed from duplicate project endpoint
• Add create_record_type_in_domain to RBAC API

• Added time tracking categories endpoints

• New endpoints: portfolio duplication, rates, budgets

• Added reactions endpoint

• Added Initiate a resource export endpoint

Added new export endpoints: https://developers.asana.com/reference/creategraphexport

• Add auto retry on failed requests: https://github.com/Asana/python-asana/tree/v5.1.0?tab=readme-ov-file#retries

• Add get events in workspace endpoint
• Update opt_fields description

• Updated GitHub Action publishing workflow

• Add archived property to portfolios

• Added privacy_setting property to portfolios
• Update portfolios description
• Added default_access_level property to portfolios
• Created PortfolioMembershipCompactResponse
• Added delivery_retry_count property to webhook response
• Update security scheme in yaml
• Added team_content_management_access_level to teams opt_field description
• Update security scheme in yaml

• team_content_management_access_level
• is_custom_weight property on goal metric
• x-hook-secret returned in create a webhook endpoint

• New is_custom_weight property on goals

• chore: fixes repsonse type to response #197
• fix: GCP not recognizing access token #196
• Added new allocations endpoints: create_allocation, delete_allocation, get_allocation, get_allocations, update_allocation
• Added update a membership endpoint

• Remove beta warning from README
• Fixed GitHub Action workflow to publish new versions of python
• Delete task template endpoint added
• Fixed: urlib3 deprecation warning: HTTPResponse.getheaders() is deprecated and will be removed in urllib3 v2.1.0. Instead access HTTPResponse.headers directly. #192

• Add a custom field to a project endpoint now takes in opts argument

BEFORE:

    api_response = projects_api_instance.add_custom_field_setting_for_project(body, project_gid)

AFTER:

    api_response = projects_api_instance.add_custom_field_setting_for_project(body, project_gid, opts)

• Fix call_api not working when no query_params are provided (Adding a custom field to a project raises exception #188)
• Fix page iterator link in README.md going to wrong link

• Changes from v4:
• • Query params are now passed in through opts dictionary instead of method params
• Added pagination
• Updated sample code
• Document how to use new client library features
• Fix response decode issue of special characters from previous versions

• task_templates endpoints
  • GET /task_templates
  • GET /task_templates/{task_template_gid}
  • POST /task_templates/{task_template_gid}/instantiateTask
• Added complete color option to current_status.color value -> for endpoints that return current_status.color EX: Projects
• Update description for custom_fields updates -> gives example of date and date-time values

• Fix search_tasks_for_workspace custom fields query not working for is_set, value, starts_with, ends_with, less_than, greater_than

• Fix not being able to search using custom fields query for searchTasksForWorkspace method

• Added minimum_access_level_for_customization and minimum_access_level_for_sharing to the project schema
• Added completed_since as a query param to GET /sections/{section_gid}/tasks

• Handle multiprocessing.pool init
• Sync with API/Developer Docs: Removed required text and color from ProjectStatusBase which caused problems in developer docs -> Update a Project endpoint

• Fix IndentationError: Updated api.mustache template file to generate api classes with out indentation errors. (issue)

README.md + Sample code changes

• Update tab spacing in sample code and README.md from 2 to 4 spaces
• Separate call_api examples in README.md
• Add instructions on how to paginate with next_page response data in README.md
• Add instructions on how to access response data in README.md
• Add instructions on how to get events in README.md
• Add instructions on how to set asana-enable header to README.md
• Add instructions on how to access status and headers from response to README.md
• Update GitHub Action to include version in update commit message

• Sync with API/Developer Docs: Added created_by property to task response

• Fix indentation on code samples template

• Update Github Action: add tags to update pushes and update gh-action-pypi-publish release version

v4.0.0

• Completely new python client library. Code generated through Swagger Codegen.
• Improves internal release process -> allows Asana to keep python client library in sync with the API more frequently
• Introduces classes for resources. Responses return resource objects and data can be accessed via dot notation
• Sample code documentation is more rich
• Synced with latest API changes since Apr 18, 2023

v4.0.1

• Add missing quotes to version in custom Asana header

• Update v3 to v3.2.3
• Add important message to README.md

• Rollback from v4 to v3 -> update README.md to mention v4 = BETA

• removed delete_status_message method

• Drop support for python 3.6 and below
• Added Message and Memberships resources

• Added goal relationships
• Removed goals methods: add_subgoal, add_supporting_work_for_goal, get_subgoals_for_goal, remove_subgoal, remove_supporting_work_for_goal, supporting_work

• Adds support for /attachment endpoints. Note: Attachments are no longer tied to a task
  • POST /tasks/:task/attachments -> POST /attachments?parent=
  • GET /tasks/:task/attachments -> GET /attachments?parent=
• Adds goal_id request parameter for Goals-related endpoints
• Adds support for GET /workspaces/{workspace_gid}/teams. Note: Removes support for getting teams in an organization

• Removed Travis CI and added GitHub Actions

Added create_attachment_for_task to the attachments resource.

Fixes BatchAPI being ignored on the client.

Added team_memberships to resources

This version converts our client libraries to use the OpenAPI spec. We also switched to a more consistent naming convention. This version keeps the old methods and adds the new method names.

Fixes an incorrectly strict requirement.

This release contains one change, to fix some string templating when uploading attachments that was broken with string IDs.

This adds api functionality the the client libraries have been missing:

• Portfolios
• PortfolioMemberships
• Jobs
• UserTaskLists

This update also includes Asana-Change warnings. These warnings pop up every time a request is made and the response contains a deprecation header. You can find out how to work with these here.

In Python 3.7, it's bad form to raise StopIteration at the end of a loop - and it yells at you for it by turning the exception into a Runtime Exception.

This simply removes throwing this, since it should be safe to just return.

Tested with pipenv on 2.7 and 3.7. We don't officially support 3.7 yet due to https://bugs.python.org/issue34226, but we should be close - support for everything except attachments.

This fixes a bug with setting custom headers and fixes #80.

This release contains many of the API updates that have accumulated since the last release, including:

• The search API
• Dependencies
• Custom field creation
• Project memberships
• Project statuses
• Editing and deleting comments

Our API can accept a client_name option for apps who wish to identify themselves, but we weren't properly pulling this out into the payload and query params.

• Add support for Sections and Organization Exports (#58)
• Handle 402's in the API (#62 )
• Drop Python 2.6 & 3.3 support

• Add Timeout To Request Options (#54) - Add simple timeouts via requests that throw an exception on any timeout specified, including the middle of a paginated call.
• Make Package Requirements Less Stringent (#61):
  • Upgrade most packages to recent versions (tested).
  • Set compatibility for > 1.0 releases at minor releases (second digit).
  • Set compatibility for < 1.0 releases at micro releases (third digit).

Using the deploy.py script as a source of versioning in setup.py, which was introduced in 0.6.0, caused problems, as deploy.py is not included in the python egg. Removing that dependency in setup.py

Asana has added Custom Fields to its tasks and projects!

To read more information about Custom Fields, please head to https://asana.com/developers/documentation/getting-started/custom-fields