You must be the issue author or have at least the Reporter role for the project, be the author of the issue, or be assigned to the issue.Learn how to change the default issue closing pattern. You must have administrator access to your GitLab instance.Merge requests and commits in this project can still close another project’s issues. Alreadyĭisabling automatic issue closing only applies to issues in the project where the setting was disabled. Referenced issues are still displayed, but are not closed automatically.Ĭhanging this setting applies only to new merge requests or commits. Clear the Auto-close referenced issues on default branch checkbox.On the left sidebar, select Settings > Repository.On the top bar, select Main menu > Projects and find your project.You must have at least the Maintainer role for the project.You can disable the automatic issue closing feature on a per-project basis Changed in GitLab 15.4: The referenced issue’s project setting is checked instead of the project of the commit or merge request.A cross-project issue ( group/project#123).Implement, Implements, Implemented, Implementing, implement, implements, implemented, implementing.Resolve, Resolves, Resolved, Resolving, resolve, resolves, resolved, resolving.Fix, Fixes, Fixed, Fixing, fix, fixes, fixed, fixing.Close, Closes, Closed, Closing, close, closes, closed, closing.To automatically close an issue, use the following keywords followed by the issue reference. It inherits the issue’s milestone and labels.įor performance reasons, automatic issue closing is disabled for the very first Issue #5 is marked as a related issue, but it’s not closed automatically.Īlternatively, when you create a merge request from an issue,.Issues #4 and #6 are closed automatically when the MR is merged.The commit or merge request is merged into the default branch.įor example, if you include Closes #4, #6, Related to #5 in a merge request.The commit is pushed to a project’s default branch.If a commit message or merge request description contains text matching the closing pattern,Īll issues referenced in the matched text are closed when either: Administrators of self-managed GitLab instances In a commit message or merge request description. You can close issues automatically by using certain words, called a closing pattern, To reopen a closed issue, at the top of the issue, select Reopen issue.Ī reopened issue is no different from any other open issue. In an issue board, drag an issue card from its list into the Closed list.At the top of the issue, select Close issue.To close an issue, you can do the following: The issue is marked as closed but is not deleted. When you decide that an issue is resolved or no longer needed, you can close it. Drag the row to the new position in the list.Hover over the list item row to make the grip icon ( ) visible.To reorder list items, when viewing an issue: The issue’s description must have an ordered, unordered, or.You must have at least the Reporter role for the project, be the author of the issue, or be.When you view an issue that has a list in the description, you can also reorder the list items. Search for a project to move the issue to.On the right sidebar, select Move issue.You must have at least the Reporter role for the project.Before moving the issue, make sure it does not contain sensitive data. Where it came from and went to, is added to both issues.īe careful when moving an issue to a project with different access rules. When you move an issue, it’s closed and copied to the target project. When bulk editing issues in a group, you can edit the following attributes: From the sidebar, edit the available fields.Select the checkboxes next to each issue you want to edit.A sidebar on the right of your screen appears. On the top bar, select Main menu > Groups and find your group.To edit multiple issues at the same time: You must have at least the Reporter role for a group.You can edit multiple issues across multiple projects when you’re in a group. Editing iteration introduced in GitLab 13.9.Editing health status introduced in GitLab 13.2.Assigning epic introduced in GitLab 13.2.To the right of the title, select Edit title and description ( ).You must have at least the Reporter role for the project, be the author of the issue, or be assigned to the issue.You can edit an issue’s title and description. Issue-related quick actions Manage issuesĪfter you create an issue, you can start working with it.Reorder list items in the issue description.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |