![]() Learn more about setting up your Kanban board. This depends on the column configuration of your Kanban board, but this is essentially the section for the column that's mapped to the initial status of your workflow. If you split an issue in an active sprint, you can choose to send the new issue to either the backlog or a future or active sprint.Īfter splitting an issue, the new issue will be sent to the Backlog section. If you split an issue in the backlog, the new issue will be sent to the Backlog section. You'll also find the option to split an issue in the sprint or Selected for Development section of your Backlog. Right-click an issue and select Split issue. Navigate to the Backlog of your Scrum or Kanban software development project. Note that you can only split an issue from the Scrum backlog and the Kanban backlog (if enabled), and not from Active sprints or the Kanban board. ![]() Splitting an issue is useful when an issue is so big, that it's better to divide it into two or more issues and make work more manageable. If applicable to the issue you're cloning, you can also select from these options:Ĭlone attachments to add any existing attachmentsĬlone links to add any existing linked issuesĬlone sprint values to copy across the issue's current and closed sprint values Optionally edit the cloned issue's Summary The issue status also returns to the first step of the corresponding workflow, and the resolutions are cleared. The cloned issue can be linked to the original issue, but doesn't have to be. Some details aren't cloned, like time logged, comments, history, and links to Confluence pages. The cloned issue contains most of the same details stored in the original issue, like the summary, affected versions, and components. Clone an issueĬlone an issue to quickly create a duplicate of it in the same project. Then, you can add issues to epics as you create them. You can also create an issue that automatically belongs to a particular epic. If you're using epics, select Configure Fields and add the Epic Link field to the screen. To restrict issues, you can create them using the global navigation bar. These issues can be accessed by anyone who can see your project. When you use the inline issue create to create issues, your issues won’t be restricted to certain roles in the project. If your board's filter specifies more than one project, you'll still need to complete the full Create issue dialog. You can quickly create issues using the inline issue create in the Backlog (for Scrum boards, backlog, and future sprints only). You have specified a sprint when creating the issue - your issue will be created at the bottom of the sprint. You've selected an issue in the backlog - your issue will be created right below the selected issue Your newly created issue will appear at the top of your backlog, unless If you create an issue on a board that’s using a JQL filter, the issue will inherit fields such as custom values and labels. Review these before creating the new issue. Optional: To create other issues with the same Project and Issue Type, select the Create another checkbox. Depending on your configuration and issue creation history, some fields may be pre-populated. When you next create an issue, the selected fields will be displayed. Optional: To change which fields appear when you create another issue, select Configure Fields and select and deselect the fields you want. Create an issueĬomplete all required fields and any other fields that you want. You need the Create Issue project permission for the issue's relevant project. Learn how to import multiple issues from a CSV file.įor those just getting started, head over to our admin docs to learn how to configure issue types. You can also import multiple issues and subtasks via the CSV import. On this page, you'll learn more about creating and converting issues and subtasks, and setting issue-level security. You can also control issue-level security to restrict an issue to select members of your team. ![]() Issues act as the packets of work that travel through their respective workflows within their projects until the work is completed.Īn issue can have subtasks that can be assigned and tracked individually. The building blocks of any project are issues. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |