TheDude
/
openproject
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
OpenProject is the leading open source project management software.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
53365 Commits
139 Branches
203 Tags
1.2 GiB
Tag: Branch: Tree: d01d33c631
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'd01d33c631'
${ noResults }
openproject/app/models/queries/time_entries.rb

43 lines
1.8 KiB
Raw Normal View History Unescape

read operations for time_entries via api v3 (#5776) * read operations for time_entries via api v3 Introduces the endpoints: * GET /api/v3/time_entries * GET /api/v3/time_entries/:id * GET /api/v3/time_entries/activities/:id The index action for time entries can be queried by the following filters: * project_id * user_id * work_package_id The implementation is exposing the database structure mostly one to one with the exception of some renaming and the hiding of the activities' complexity, where only the activity used systemwide is referenced regardless of whether a project specific override exists or not. * allow custom values for time entries [ci skip]
7 years ago
#-- encoding: UTF-8
#-- copyright
# OpenProject is a project management system.
Bump copyright to 2018 (#6171) [ci skip]
7 years ago
# Copyright (C) 2012-2018 the OpenProject Foundation (OPF)
read operations for time_entries via api v3 (#5776) * read operations for time_entries via api v3 Introduces the endpoints: * GET /api/v3/time_entries * GET /api/v3/time_entries/:id * GET /api/v3/time_entries/activities/:id The index action for time entries can be queried by the following filters: * project_id * user_id * work_package_id The implementation is exposing the database structure mostly one to one with the exception of some renaming and the hiding of the activities' complexity, where only the activity used systemwide is referenced regardless of whether a project specific override exists or not. * allow custom values for time entries [ci skip]
7 years ago
#
# This program is free software; you can redistribute it and/or
# modify it under the terms of the GNU General Public License version 3.
#
# OpenProject is a fork of ChiliProject, which is a fork of Redmine. The copyright follows:
# Copyright (C) 2006-2017 Jean-Philippe Lang
# Copyright (C) 2010-2013 the ChiliProject Team
#
# This program is free software; you can redistribute it and/or
# modify it under the terms of the GNU General Public License
# as published by the Free Software Foundation; either version 2
# of the License, or (at your option) any later version.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with this program; if not, write to the Free Software
# Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
#
Bump copyright to 2018 (#6171) [ci skip]
7 years ago
# See docs/COPYRIGHT.rdoc for more details.
read operations for time_entries via api v3 (#5776) * read operations for time_entries via api v3 Introduces the endpoints: * GET /api/v3/time_entries * GET /api/v3/time_entries/:id * GET /api/v3/time_entries/activities/:id The index action for time entries can be queried by the following filters: * project_id * user_id * work_package_id The implementation is exposing the database structure mostly one to one with the exception of some renaming and the hiding of the activities' complexity, where only the activity used systemwide is referenced regardless of whether a project specific override exists or not. * allow custom values for time entries [ci skip]
7 years ago
#++
module Queries::TimeEntries
query = Queries::TimeEntries::TimeEntryQuery
Queries::Register.filter query, Queries::TimeEntries::Filters::UserFilter
Queries::Register.filter query, Queries::TimeEntries::Filters::WorkPackageFilter
Queries::Register.filter query, Queries::TimeEntries::Filters::ProjectFilter
TimeEntries: activity, created_at and spent_on filter/sortby Implements the following filters and sortBy for TimeEntries: - created_at - spent_on - activity(_id)
6 years ago
Queries::Register.filter query, Queries::TimeEntries::Filters::SpentOnFilter
Queries::Register.filter query, Queries::TimeEntries::Filters::CreatedOnFilter
Queries::Register.filter query, Queries::TimeEntries::Filters::ActivityFilter
fix flickering spec by introducing order for time_entries api
7 years ago
Queries::Register.order query, Queries::TimeEntries::Orders::DefaultOrder
read operations for time_entries via api v3 (#5776) * read operations for time_entries via api v3 Introduces the endpoints: * GET /api/v3/time_entries * GET /api/v3/time_entries/:id * GET /api/v3/time_entries/activities/:id The index action for time entries can be queried by the following filters: * project_id * user_id * work_package_id The implementation is exposing the database structure mostly one to one with the exception of some renaming and the hiding of the activities' complexity, where only the activity used systemwide is referenced regardless of whether a project specific override exists or not. * allow custom values for time entries [ci skip]
7 years ago
end