Creating Tasks

Tasks are labelled Issues in the team interface. This guide covers the team issue form, required values, saved issue page, and editing controls.

Verified on the development environment on 24 September 2026. Screenshots use a documentation sample. You need access to a writable workspace, a team, a project in that team, and an available Feature.

1. Open the creation form

  1. Open your team's Issues page from the sidebar.
  2. Click New Issue.
  3. Check the team name at the top of the form.

New issue form with blank title and description, unset required fields, and disabled Create issue

2. Enter title, description, and project

  1. Enter a non-empty Issue title.
  2. Fill Add description... with the requirements and acceptance criteria. Markdown is supported; the description is optional in this form, but supplying it gives the task its working context.
  3. Click the folder-icon project chip and choose the intended project. It may already show the first available project; do not assume that default is correct.

Project is required and must belong to the selected team. If the picker has no projects, have a team maintainer create one before continuing.

3. Set priority, type, and estimate

  1. Click No priority and choose Urgent, High, Medium, or Low. There is no preselected Medium priority.
  2. Click Type: Feature and choose the kind of work: Feature, Bug, or Chore.

Task type menu with Feature, Bug, and Chore

  1. Click Estimate and select the story points. Available values are 1, 2, 3, 5, 8, and 13. No estimate does not satisfy creation requirements.

Estimate menu showing No estimate and the available story-point values

4. Select the Feature and review

  1. Open the separate Feature chip, identified by the stacked-layers icon.
  2. Select the product area the issue belongs to. The picker displays your team's Feature paths; the example selects documents.
  3. Review the status and optional fields before creating.

Issue ready to create with its required fields selected

Feature association is required for Feature, Bug, and Chore tasks. The current hint says “Feature is required when Type is Feature,” but the requirement applies to all three. No feature clears the selection. If there are no entries, the picker directs you to Feature Matrix; ask a team maintainer to add the relevant Feature.

To create or organize features and review their task coverage, see Feature Matrix and Lineage.

FieldInitial value / behavior
TitleEmpty; required.
DescriptionEmpty; optional in this form. Add the complete working context before creating.
ProjectMay be preselected; required.
PriorityNo priority; choose a value.
TypeFeature; change to Bug or Chore as appropriate.
EstimateUnset; choose story points.
FeatureUnset; required for every type.
StatusBacklog. Other choices: In Progress, In Review, Done, Cancelled.
AssigneeUnset in the form; omission defaults the saved issue to the team's AI member. Choose a team member explicitly for human ownership.
ReleaseOptional selection from the releases offered for the project/team.
LabelOptional; use Add Label.
Due dateOptional; open the … menu and choose Set due date.

5. Create and verify

  1. Leave Create more off to close the form after creation, or enable it to enter another issue afterward.
  2. Click Create issue.
  3. Wait for the success confirmation, then click View issue. Alternatively, open the new issue from the team's Issues page.
  4. Check the title, description, and Properties, then reload to confirm the saved state.

Created sample issue with its title, description, identifier, and Properties

The identifier combines the team prefix and a number, for example ENG-42. Copy the URL from the open issue page; the route is /teams/<team>/issues/<issue-key>, not /tasks/<issue-key>.

Create more keeps the form open for another issue; it is not a draft mode. Required values such as priority, estimate, and Feature must be selected again. Closing an unsubmitted form does not create a saved draft.

Change issue status

  1. Open the saved issue.
  2. In Properties, click Status and choose the new value. On narrow screens, open the Properties panel first.
  3. Reload to check that the change persisted.

Status picker with the five available issue statuses

Status saves when selected. The creation/detail label Backlog corresponds to the todo state; some board views label that column To Do.

Edit a description

  1. Open the issue and click its description.
  2. Edit the text in the editor.
  3. Cancel discards the pending edits. Save attempts to submit them; it is not autosave.

Description editor with explicit Save and Cancel buttons

Current dev limitation: the Save request for the sample issue returned HTTP 404, and the original description remained after reload. Keep a copy of edited text and reload to verify any attempted save. The editor closing is not proof that the text was saved. Description persistence needs an application fix; it was not changed as part of this documentation update.

Comments and mentions

Use the message box below the issue to compose a comment. For a person, type $ and select from Team member suggestions. @ is used for agent commands on this surface; it is not the person-mention prefix.

Read Coding Agents before submitting an agent command. The member suggestion picker was checked without posting a comment or testing notification delivery.

Troubleshooting

SymptomAction
Create remains disabledCheck title, project, priority, estimate, and the separate Feature selection.
Bug or Chore still requires a FeatureSelect the product area; task type and Feature association are different fields.
The wrong project is selectedChange the preselected project chip before creating.
A new issue is assigned to AI.AgentNo explicit assignee was supplied. Select a person if required.
The new issue is missing from the current viewUse View issue in the confirmation, or check the team's view and filters.
Description edits disappearKeep a copy; the dev Save failure described above was reproduced.

For a shorter walkthrough, see Quick Start.