Tags give the ability to mark specific points in history as being important
-
2.4.0
Release: 2.4.031b14cd6 · ·Added ------------------------ - **Notifications:** - Notify members when a note is created on epic or task - Created endpoint to batch destroy notifications: `DELETE /api/v1/notifications/batch` **Projects:** feature flags Projects now have a few flags to enable/disable features. Most of the features disable the creation of new objects but don't prevent fetching/updating existing ones via the API, so they can safely be switched on and off; this is more a way to de-clutter the UIs for simple projects. - `backlog_enabled`: prevents tasks to be created with the `in_backlog` property. Existing backlog tasks still can be updated with the `PUT /api/v1/tasks/:id`, directly queried with `GET /api/v1/tasks/:id`, and are still listable via the `GET /api/v1/projects/:id/tasks` endpoint with the `in_backlog` parameter set to `null` (all tasks) or `true` (backlog tasks only, which may be weird), . Clients should update their behavior to include backlog tasks in the default tasks list. - `epics_enabled`: prevents the creation of epics. Other epics endpoints are still available to query/update existing ones via the API. Clients should update their behavior to include existing epic tasks in their tasks lists by using the `in_epic` param set to `null` (all tasks) or `true` (epic tasks only, which is weird) - `playbooks_enabled`: prevents the creation of playbooks, steps and plays, but existing data is still available/updatable - `activity_reports_enabled`: prevents the creation of new activity reports. Time frames that belongs to locked reports will still be locked. **Counter caches** - Counter caches are added for notes and links on customers and projects - Counter caches are added for notes on tasks and epics - Counter cache is added for comments on plays - Maintenance task `counter_cache:update` has been added to update them **File upload** Files can be attached to customers, projects, tasks and epics. A new data kind (`AttachmentKind`) can be created to help organize the files: - with a `Customer` subject for customer uploads - with a `Project` subject for project, task and epic uploads New notifications are sent when files are attached, and the preference regarding the distribution system is configurable via the usual endpoint. Changes to attachments are broadcasted with ActionCable on their project channel; except for changes made to customer uploads. A new instance configuration value, `uploads.max_file_size_mb` (environment variable :`ATT_UPLOADS_MAX_FILE_SIZE_MB`) can limit the acceptable files size. For clients, the value is served in the `.well-known` endpoint. Default value may be pretty high, so adapt it to your needs. Notable new API routes (check OpenAPI documentation for the details): - `POST /api/v1/attachments` - creates an attachment - `GET /api/v1/attachments/:id` - gets an attachment - `PUT|PATCH /api/v1/attachments/:id` - updates an attachment - `DELETE /api/v1/attachments/:id` - deletes an attachment - Scoped lists: - `GET /api/v1/customers/:customer_id/attachments` - Attachments for a given customer - `GET /api/v1/epics/:epic_id/attachments` - Attachments for a given epic - `GET /api/v1/projects/:project_id/attachments` - Attachments for a given project - `GET /api/v1/tasks/:task_id/attachments` - Attachments for a given task - `GET /api/v1/attachments/:attachment_id/file` - Gets the file. Note that the call MUST be authenticated to reach the content. - `GET /api/v1/attachments/:attachment_id/thumbnail` - Gets a thumbnail for the file. Note that the call MUST be authenticated to reach the content. Changed ------------------------ - **Tasks**: - `done` filter was replaced by `status`, with possible values: `null` for all statuses, `"done"` for _done_ statuses, `"todo"` for _todo_ statuses, or a project status ID - **Activity reports**: - Added model method to remove extra time frames from report (before and after report's date) - `POST /api/v1/activity_reports/:id/complete_frames` now also remove extra time frames - **Notes:** Prevent changing the subject via the API Fixed ------------------------ - **Epics**: Fixed policy preventing to create notes - **Links** and **Notes**: Fixed access to other notes and links on other projects - **Documentation:** Removed example data including user object. It was not invalid, but made no sense at all -
2.3.0
Release: 2.3.07220fa6e · ·Added ---------------------- - **Status**: New attribute, `collapsed_by_default`, to be used in UIs to collapse columns with this status. Fixed ---------------------- - **OpenAPI documentation**: - Correct attribute name and type for the payload of batch tasks - Improve description of the `type` attribute of `Status` resource - **Tasks**: - When reordering, take into account the fact that task is in the backlog - When reordering, take into account the fact that task is in an epic
-
2.2.0
Release: 2.2.09d01e620 · ·Added -------------- - **Time frames**: New API filter on `GET /api/v1/time_frames`: `reported` (_boolean_) to select time frames that are part of an activity report or not. - **Project members**: New route to re-invite members who left or where removed from the project: `PUT /api/v1/project_members/:id/reinvite` Fixed -------------- - **OpenAPI documentation**: Document some path parameters - **Tasks**: Improve position changes
-
2.1.0
Release: 2.1.0de021d6a · ·Added ------------- - Project members: created `PUT /api/v1/project_members/:id/update_time_frames` to update unlocked time frames with current rates on a Changed ------------- - Activity reports: - Nullify time frames' association when deleting an activity report - Unlock time frames before deleting an activity report