Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
10bae3d0
Commit
10bae3d0
authored
Nov 18, 2021
by
Marcin Sedlak-Jakubowski
Committed by
Fiona Neill
Nov 18, 2021
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Fix and clarify tasks doc
parent
f9f80ec6
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
6 additions
and
3 deletions
+6
-3
doc/user/tasks.md
doc/user/tasks.md
+6
-3
No files found.
doc/user/tasks.md
View file @
10bae3d0
...
@@ -15,15 +15,18 @@ For the latest updates, check the [Tasks Roadmap](https://gitlab.com/groups/gitl
...
@@ -15,15 +15,18 @@ For the latest updates, check the [Tasks Roadmap](https://gitlab.com/groups/gitl
FLAG:
FLAG:
On self-managed GitLab, by default this feature is not available. To make it available,
On self-managed GitLab, by default this feature is not available. To make it available,
ask an administrator to
[
enable the feature flag
](
../administration/feature_flags.md
)
named
`work_items`
.
ask an administrator to
[
enable the feature flag
](
../administration/feature_flags.md
)
named
`work_items`
.
On GitLab.com, this feature is not available.
The feature is not ready for production use.
The feature is not ready for production use.
Use tasks to track steps needed for the
[
issue
](
project/issues/index.md
)
to be closed.
Use tasks to track steps needed for the
[
issue
](
project/issues/index.md
)
to be closed.
When planning an issue, you need a way to capture and break down technical
When planning an issue, you need a way to capture and break down technical
requirements or steps necessary to complete it. An issue with tasks is better defined,
requirements or steps necessary to complete it. An issue with
related
tasks is better defined,
and so you can provide a more accurate issue weight and completion criteria.
and so you can provide a more accurate issue weight and completion criteria.
To see the roadmap for migrating issues and
[
epics
](
group/epics/index.md
)
Tasks are a type of work item, a step towards
[
default issue types
](
https://gitlab.com/gitlab-org/gitlab/-/issues/323404
)
in GitLab.
For the roadmap of migrating issues and
[
epics
](
group/epics/index.md
)
to work items and adding custom work item types, visit
to work items and adding custom work item types, visit
[
epic 6033
](
https://gitlab.com/groups/gitlab-org/-/epics/6033
)
or
[
epic 6033
](
https://gitlab.com/groups/gitlab-org/-/epics/6033
)
or
[
Plan direction page
](
https://about.gitlab.com/direction/plan/
)
.
[
Plan direction page
](
https://about.gitlab.com/direction/plan/
)
.
...
@@ -31,4 +34,4 @@ to work items and adding custom work item types, visit
...
@@ -31,4 +34,4 @@ to work items and adding custom work item types, visit
## View a task
## View a task
The only way to view a task is to open it with a deep link,
The only way to view a task is to open it with a deep link,
for example:
`/<group_name>/<project_name>/-/work_item/1`
for example:
`/<group_name>/<project_name>/-/work_item/1`
.
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment