This will return data containing time tracked
for the group issues by group members and within
a time frame (limited to 60 days)

To get the collection of timelogs for a certain
group we include in Group a new concern
HasTimelogsReport that will use Timelog scopes
to filter results.

We use a TimelogPresenter to display additional
fields in TimelogType

Group timelogs is a premium feature so we added
group_timelogs feature to license

TimelogType is authorized with read_group_timelogs
permission that checks for a minimun access level of
reporter and group_timelogs feature being available
Refactor changes to improve code quality

- Include subgroups in Issue and Timelog scopes
- Field timelogs in GroupType is never null
- Add error to object validation in TimelogResolver
- Use fields UserType and IssueType  in TimelogType
- Improve rule in GroupPolicy
- Remove redundant TimelogPresenter
- Add missing specs for new scopes
- Extend specs for GroupType and  TimelogType
- Add new matcher fon non null graphql fields

Update GraphQL schema
Add index for spent_at in timelogs table

Fix Timelog scope to use group descendants

Added resolvers for project and user snippets.

- Regenerate schema docs

Sean Arnold authored Dec 06, 2019 and Jan Provaznik committed Dec 06, 2019

- Squashed commit containing GraphQL changes

and changelog

Add mutation base for Issues
Update graphQL docs
Add specs for IssueSetDueDate mutation
Update GraphQL schema

Also add specs

Change names of mutations

Apply suggestion to app/graphql/mutations/todos/mark_done.rb
Apply suggestion to app/graphql/mutations/todos/mark_done.rb
Apply suggestion to app/graphql/mutations/todos/mark_done.rb

Also add specs

This enables the Vue file listing feature flag for tests
this is so that we know the Vue file listing refactor
has the same feature set as the HAML version

Brian Kabiro authored Nov 18, 2019 and Jan Provaznik committed Nov 18, 2019

- remove the ExtendedIssueType and include all fields in IssueType
- move subscribed field from ExtendedIssueType to IssueType
- add a complexity of 5 to the subscribed field

Ran `gitlab:graphql:schema:dump` as well as
`gitlab:graphql:compile_docs`

Add a mutation to change assignees for merge requests

Shows number of opened/closed sub-epics and epic issues
in GraphQL API.

Also add specs

Change names of mutations

Remove mark all done mutation

Inherit from BaseMutation

Add policy update_todo

Just support update of one todo at a time

Remove obsolete scope

Refactor spec in this location to just test result
of #resolve

Add requests spec

Add a mutation to set or remove a milestone on a Merge Request

- incldues extraction of reused code of Epic mutations

- Some use API docs copy-pasted material (a smell)
- Some are really obvious (e.g. "user's name"
- Some use labels from the UI

Felipe Artur authored Oct 30, 2019 and Jan Provaznik committed Oct 30, 2019

Add mutation to create epics on GraphQL

James Ramsay authored Oct 23, 2019 and Nick Thomas committed Oct 23, 2019

Feature branches should be deleted after being merged into a stable
branch like master. This is not universally true, and accidentally
deleting a branch cause frustration and confusion for users.

The change:
- adds a Project Setting to control if 'Delete source branch' option is
enabled or disabled for new merge requests
- the Project Setting is on for new and existing projects

The previous default behaviour can be restored by toggling the new
setting.

Historically, the behaviour was changed to delete the source branch as
part of the merge widget refactor and then reverted 3 months later.

- Widget refactor 8db76243
- Behaviour reverted fd72b4ed

In order to support realtime sidebars and continue to complete
the GraphQL API, added additional attributes to be returned
for MergeRequestType.

https://gitlab.com/gitlab-org/gitlab/issues/20829

Felipe Artur authored Oct 17, 2019 and Jan Provaznik committed Oct 17, 2019

Exposes subscribed attribute for epics in GraphQL

Jan Provaznik authored Oct 17, 2019 and Nick Thomas committed Oct 17, 2019

Allows to update epics through GraphQL API.

Remove explicit id field and changed authorization
types

Add todo to query type

Add todos field to user and add currentuser query field

Add changelog entry

Add TodoTargetEnum, using enum types in TodoType

Fix typo in description

Add missing connection_type to also support
querying for "first: n"

Fix "Do not use '_' for arguments that are used"

Add field id again

Remove unnecessary rubocop disable comments

Add values to action enum entries

Query for state and type

Use presenter for todos

Add supported fields for API

Fix action query

Marcel Amirault authored Sep 26, 2019 and Achilleas Pipinellis committed Sep 26, 2019

Update capitalization and backtick use in monitoring,
operations, raketasks and api docs.

Marcel Amirault authored Aug 28, 2019 and Achilleas Pipinellis committed Aug 28, 2019

Clean up issues that may cause the docs-lint
test to fail, such as trailing whitespace, no
EOF newline, blockquotes, etc

Alessio Caiazza authored Aug 22, 2019 and Mayra Cabrera committed Aug 22, 2019

Root namespaces have storage statistics.
This commit allows namespace owners to get those stats via GraphQL
queries like the following one

{
  namespace(fullPath: "a_namespace_path") {
    rootStorageStatistics {
      storageSize
      repositorySize
      lfsObjectsSize
      buildArtifactsSize
      packagesSize
      wikiSize
    }
  }
}

Adds more friendly docs for GraphQl implementation