Add field in project type to return timeline event tags
What does this MR do and why?
With this MR, the project query can return the incidentManagementTimelineEventTags
field.
Screenshots or screen recordings
NA
How to set up and validate locally
- Make sure you have read access to a project.
- Create a few tags by following the steps mentioned in !102870 (merged).
- Add the below query to fetch project details and add the
timelineEventTags
field with the below input. - Check the return values.
Query
query GetProjectDetails($projectPath: ID!) {
project(fullPath: $projectPath) {
id
incidentManagementTimelineEventTags {
name
id
}
}
}
Sample input
{
"projectPath": "<project_path where tags were added.>"
}
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Related to #373853 (closed)
Merge request reports
Activity
changed milestone to %15.6
assigned to @rkadam3
added 2 commits
- A deleted user
added backend documentation labels
1 Warning Please add a merge request subtype to this merge request. 2 Messages CHANGELOG missing: If you want to create a changelog entry for GitLab FOSS, add the
Changelog
trailer to the commit message you want to add to the changelog.If you want to create a changelog entry for GitLab EE, also add the
EE: true
trailer to your commit message.If this merge request doesn't need a CHANGELOG entry, feel free to ignore this message.
This merge request adds or changes documentation files. A review from the Technical Writing team before you merge is recommended. Reviews can happen after you merge. Documentation review
The following files require a review from a technical writer:
-
doc/api/graphql/reference/index.md
(Link to current live version)
The review does not need to block merging this merge request. See the:
-
Metadata for the
*.md
files that you've changed. The first few lines of each*.md
file identify the stage and group most closely associated with your docs change. - The Technical Writer assigned for that stage and group.
- Documentation workflows for information on when to assign a merge request for review.
Reviewer roulette
Changes that require review have been detected!
Please refer to the table below for assigning reviewers and maintainers suggested by Danger in the specified category:
Category Reviewer Maintainer backend Jay Montal (
@jmontal
) (UTC-7, 12.5 hours behind@rkadam3
)Luke Duncalfe (
@.luke
) (UTC+13, 7.5 hours ahead of@rkadam3
)To spread load more evenly across eligible reviewers, Danger has picked a candidate for each review slot, based on their timezone. Feel free to override these selections if you think someone else would be better-suited or use the GitLab Review Workload Dashboard to find other available reviewers.
To read more on how to use the reviewer roulette, please take a look at the Engineering workflow and code review guidelines. Please consider assigning a reviewer or maintainer who is a domain expert in the area of the merge request.
Once you've decided who will review this merge request, assign them as a reviewer! Danger does not automatically notify them for you.
If needed, you can retry the
danger-review
job that generated this comment.Generated by
Danger-
added 1 commit
- 2d74ff1d - Update have_graphql_type matcher to support array of types
requested review from @jessieay
@rkadam3 approved! Thank you for providing such a concise MR, was a pleasure to review.
@proglottis can you provide a backend maintainer review please?
requested review from @proglottis and removed review request for @jessieay
@jessieay
, thanks for approving this merge request.This is the first time the merge request is approved. To ensure full test coverage, a new pipeline will be started shortly.
For more info, please refer to the following links:
mentioned in issue #373853 (closed)
enabled an automatic merge when the pipeline for 94e9ab39 succeeds
mentioned in commit 833587e5
added workflowstaging-canary label and removed workflowin dev label
added workflowcanary label and removed workflowstaging-canary label
added workflowstaging label and removed workflowcanary label
added workflowproduction label and removed workflowstaging label
added workflowpost-deploy-db-production label and removed workflowproduction label
added releasedcandidate label
added featureaddition label
added releasedpublished label and removed releasedcandidate label
mentioned in merge request !109015 (closed)