Releases: topcoder-platform/tc-project-service
Add tgadmin as admin for API
Minor : bulk update member phases for milestone management
Milestone Management
This is part of Milestone management project/sprint for Topcoder conenct, an initiative to improve the UX in TC Connect for project progress/plan communication with the customers.
This Release contains :
- Add new cross ref table between Topcoder Users and TC Connect Project Phase.
- Updated Phases api endpionts to include members field which represents the copilot user ids, so when pulling a phase or project phases we get members array
- Added new endpoint to update Phase copilots by passing userIds field to store the association
- Updated Get Phases endpiont to have memberOnly param to get only phases the authorized member is part of
- Updated maxPhaseProductCount to 100, so we allow creating multiple products (challenges) per product (Milestone)
- Storing challenge id in the Phase.Product.Details json array (the string used in details is configured in tc connect and work manager app)
- Customer approval with In Review/Reviewed status (don't allow approval if phase is not In Review)
- Updated deleting product phase to sync it in ES
DB Script executed :
migrations/20210718_project_phase_member_table.sql
migrations/20210802_project_phase_approval_table.sql
Additional Billing Account Details
Patch Release - Fix missing BA name in dev env
Project Defaults - Supports Billing Accounts endpoint, add groups and terms to project
This release in support to Project Defaults shape up project
Minor release - 3.2.0
- Implemented Job creation for TaaS App (disabled for now)
- Copilot is allowed to update project status now
- Relaxed milestones/timelines validation to support new New Project-Plan operations
- Update permissions for removing Copilots
- Fixed Kafka handler for newly created projects
Minor release
TBD
Prod Release 3.0.0
Major refactoring for milestone updates (Breaking Changes)
Now api does not do automatic adjustment of the milestones when a milestone is updated (updates which affect other milestones of the timeline e.g. marking a milestone active or completed or changing its duration). This effort is inline with our overall v5 efforts where we want the API to be as RESTful as it can be, without any business logic. After this change, it is the client (caller of the api) responsibility for making sure the correct order and dates of the milestones and send all milestones, that client thinks should be updated, in single bulk patch call which is introduced in this release.
Release 2.4.0
- M2M scope support #483
- Improved local setup
- Dependency libraries security patches
- Updated to Node 12
- Bug fixes