Recognize 'time' for time tracking quick actions
What does this MR do and why?
Describe in detail what your merge request does and why.
This adds aliases containing time
to the time tracking quick actions, so they are easier to find
Screenshots or screen recordings
How to set up and validate locally
Write /time
in the comment field of an issue and observe the suggestions
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 #16501 (closed)
Merge request reports
Activity
added typefeature label
added Leading Organization label
Hey @Taucher2003!
Thank you for your contribution to GitLab. Please refer to the contribution flow documentation for a quick overview of the process, and the merge request (MR) guidelines for the detailed process.
When you're ready for a first review, post
@gitlab-bot ready
. If you know a relevant reviewer(s) (for example, someone that was involved in a related issue), you can also assign them directly with@gitlab-bot ready @user1 @user2
.At any time, if you need help moving the MR forward, feel free to post
@gitlab-bot help
. Read more on how to get help.To enable automated checks on your MR, please configure Danger for your fork.
You can comment
@gitlab-bot label <label1> <label2>
to add labels to your MR. Please see the list of allowed labels in thelabel
command documentation.This message was generated automatically. You're welcome to improve it.
added Community contribution workflowin dev labels
assigned to @Taucher2003
added featureenhancement groupproject management labels
- Resolved by Max Woolf
@Taucher2003-Bot rwps msedlakjakubowski nicolasdular
Edited by Niklas van Schrick
mentioned in issue #16501 (closed)
1 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/user/project/quick_actions.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 Niko Belokolodov (
@nbelokolodov
) (UTC+13)Max Woolf (
@mwoolf
) (UTC+0)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
DangerEdited by Taucher2003 Bot-
added 1 commit
- 891944f4 - Recognize 'time' for time tracking quick actions
added devopsplan sectiondev labels
added workflowready for review label and removed workflowin dev label
requested review from @msedlakjakubowski and @nicolasdular
Hi
@dianalogan
! Please review this documentation merge request. This message was generated automatically. You're welcome to improve it.added documentation twtriaged labels
requested review from @dianalogan
@nicolasdular
@msedlakjakubowski
@dianalogan
, this Community contribution is ready for review.- Do you have capacity and domain expertise to review this? We are mindful of your time, so if you are not able to take this on, please re-assign to one or more other reviewers.
- Add the workflowin dev label if the merge request needs action from the author. This message was generated automatically. You're welcome to improve it.
- Resolved by Marcin Sedlak-Jakubowski
- Resolved by Marcin Sedlak-Jakubowski
Thanks @Taucher2003 for your contribution
Looks all good from my side, I just have a question regarding the grammar but will leave it up to our TWs :)
Hey @mwoolf, Do you mind performing a backend review for this merge request, please? :) Thanks!
requested review from @mwoolf
added backend label
changed milestone to %15.6
- Resolved by Marcin Sedlak-Jakubowski
- Resolved by Marcin Sedlak-Jakubowski
added Technical Writing UI text docsfeature twdoing workflowin review labels and removed twtriaged workflowready for review labels
removed review request for @dianalogan
removed review request for @msedlakjakubowski
- Resolved by Marco Zille
removed review request for @nicolasdular
requested review from @msedlakjakubowski
- Resolved by Max Woolf
added twfinished label and removed twdoing label
removed review request for @msedlakjakubowski
- Resolved by Max Woolf
@msedlakjakubowski
, thanks for approving this merge request.This is the first time the merge request is approved. To ensure full test coverage, please start a new pipeline before merging.
For more info, please refer to the following links:
1 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/user/project/quick_actions.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 Harsimar Sandhu (
@harsimarsandhu
) (UTC+5.5)Drew Blessing (
@dblessing
) (UTC-6)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-
enabled an automatic merge when the pipeline for a8352727 succeeds
@Taucher2003, how was your code review experience with this merge request? Please tell us how we can continue to iterate and improve:
- React with a
or a on this comment to describe your experience. - Create a new comment starting with
@gitlab-bot feedback
below, and leave any additional feedback you have for us in the comment.
Have five minutes? Take our survey to give us even more feedback on how GitLab can improve the contributor experience.
Thanks for your help!
This message was generated automatically. You're welcome to improve it.
- React with a
mentioned in commit babfadf4
mentioned in issue #382727
added workflowstaging-canary label and removed workflowin review 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-staging label and removed workflowproduction label
added workflowpost-deploy-db-production label and removed workflowpost-deploy-db-staging label
added releasedcandidate label
mentioned in merge request kubitus-project/kubitus-installer!1646 (merged)
added releasedpublished label and removed releasedcandidate label