Create an issue
Open a project or the global "Issues" list and choose to create an issue. In the global list, select a project first: it determines issue types, fields and attachment availability. Creation is available with project access, permission to create issues and an active seat.
- Select the project and issue type.
- Enter a summary and description, then complete other mandatory fields.
- Set an assignee, priority and dates when needed and available in that project.
- Add files if needed and create the issue.
- Open the created issue and check its key, field values and upload results.
Summary and description are mandatory. Text fields support Markdown; the "?" beside the description links to the full reference. Numbers, dates and choices use their own formats. For a missing custom field, first check project settings and the selected issue type.
Daily work
Open an issue by key from search, a project or a board. Edit and save the relevant field. To change status, choose an allowed transition; available actions depend on the workflow and your permissions. Reload after a concurrent-change message so you can review someone else's work and not overwrite it.
Comments keep the discussion with the issue, while a checklist tracks small steps. Changes appear in issue history. Enable watching for further updates. Estimates and worklogs are covered under Time tracking.
Types, hierarchy and links
Project configuration defines the available types and hierarchy. Choose an existing, accessible parent of a permitted type. Quevell checks compatibility and does not allow cycles. A parent describes the composition of work; an ordinary issue link records a relationship between separate pieces of work.
When linking an issue, select a link type and the other issue's key. The direction tells you which issue blocks or depends on the other. A link does not grant access to the linked issue. For instructions or decisions, use a knowledge page, which can also link to an issue.
For example, a large issue contains several child issues while a separate issue blocks release. Represent the children in the hierarchy and the blocking dependency with an appropriate link type. Available types depend on company settings.
Files and checklists
You can select files during creation after choosing a project, or attach them to an existing issue. Uploads check size limits and permissions. Review each result: the issue may be created even if one of its files does not upload.
If the issue was created but a file failed, use the offered retry for that file. Do not create another issue just to attach it. For an unknown result, first open the created issue and inspect its files. A pasted image also requires a successful upload for its description link to work.
A checklist is stored within the issue. Add items and mark completed steps. It does not create child issues or replace their statuses. Checklist and file changes depend on permission for their respective actions.
Company and project settings
A Company administrator creates shared custom fields, issue types and workflows. A person with "Edit configurations" permission selects the sets and fields used by the project. Applying a saved configuration also requires permission to manage project access. You do not need access to these settings to create or edit issues.
Open project settings and inspect issue types, assigned workflows and fields. Creating a shared field does not automatically put it on every project. Once connected, it appears in the new-issue form and in issues of the applicable types.
Before changing a shared scheme, consider other projects using it. See Workflows for statuses, publication and revisions. Project access for people and groups is covered under Rights and access.
Fields, required fields and layout
- Open fields in project settings and connect the custom field.
- Check its type, allowed values, mandatory setting and default value.
- Select applicable issue types if the field is restricted by type.
- Arrange its position on the issue screen and save.
- Open an issue of the selected type to find the field in its configured position.
Summary and description are not optional. Other fields follow project configuration. A default helps with creation; changing it does not automatically rewrite existing issues. Use an allowed option for a choice field. For a user field, select an active company member.
For example, connect "Component" to the intended type, define options and make it mandatory. Creating an issue of that type will require a component. If the field is not visible, check the project, type, connection and layout before creating a duplicate field.
Names in other languages
Custom fields, types, statuses and transitions can have names in other interface languages. Names appear in your interface language. If no name is available in that language, the base name is used. Choice options can have alternate names too. Renaming a custom field does not rename system fields or interface labels.
Enable "Names in other languages", enter the alternate name and save. Custom-field descriptions have a separate option for other languages. Switching languages changes the labels of the same field; you do not need to create another field for a different language.
To remove an alternate name, clear it or turn off its option and save. The base name remains available. Unsaved edits can be cancelled.