Issue

Assigning Issues

Assigning tasks in Oktuple is simple and flexible, helping you streamline collaboration and boost team productivity. You can assign tasks from various parts of the platform to fit your workflow. 💡 Why Assigning Issue Matters - Clarifies responsibilities for each team member - Helps divide work effectively across the project - Ensures the right people are involved - Matches tasks to each person’s expertise How to Create Issues To Create a Task - Go to the relevant Project or Workspace You can go to projects from left side bar and open the project: - Click Add Issue from right side of opened page - After completing the items click on “Create issue” 🛠️ Ways to Assign Issues You can assign tasks from different areas in Oktuple, depending on how you work: 1. In the task creation form, find the Assignee field - Select one or more team members from the dropdown list 2. From the Backlog List in the sprint page - Open the Backlog by clicking on the special sprint name - Click on a task to open its details - Find the Assignee section - Select the team member(s) and save changes 3. From the Kanban Board - Open the Kanban Board by clicking on the project name - Click on the task you want to assign - In the modal, find the Assignee field - Choose your team member(s) and save 4. From Subtasks Inside a Task Modal - Open the main task modal - Scroll to the Subtasks section - Add or edit a subtask - Use the Assignee dropdown to assign a team member 6. 🔄 (Coming Soon) Bulk Assign Multiple Tasks Quickly assign several tasks at once to one or more team members (feature under development). 🔁 Reassign Tasks Anytime Need to make a change? - Open the task - Click the current assignee’s name - Select a new team member from the dropdown list 📌 Task Assignment Tips 1. Assign to multiple members if teamwork is required 2. Use tags or priorities to clarify urgency and ownership 3. Make sure assignees have access to the workspace 🔎 Use the Assignees Filter From the filter bar, quickly view tasks assigned to any team member. It’s perfect for tracking contributions and managing workload across your team.

Moving Issues

You can easily create tasks anywhere in your Workspace and move them seamlessly between lists, sprints, and Kanban columns. Whether you're adjusting priorities or reorganizing your workflow, moving issues keeps your tasks in the right place at the right time. 🛠️ What You Can Do - Move Issues Between Kanban Workflow Columns - Transfer Issues in the List View (Backlog List) - Reallocate Issues Between Sprints - Shift Issues Within a Single Sprint 🧩 Move Issues in the Kanban Workflow at the Collection Level If your Kanban board is set at the collection level (not at the folder level or in a space without a collection), you can drag and drop issues between columns to update their status. However, if your board is not tied to a collection, drag-and-drop won't be available — you'll need to manually change the issue's status to move it between columns. 1. Add your issue to the Kanban board inside a collection 2. Simply drag and drop the issue from one workflow column to another (e.g., from "To Do” to "In Progress"). This helps reflect the current stage of work and keeps your board updated. 📋 Transfer Issues in the List View Go to your Project or switch to List View. At first click on the projects part and then choose the specific project Go to your Project Click on the Projects section from the sidebar 1. Select the specific project you want to manage 2. Then this page will appear: Navigate to the Desired Collection 3. Within your project, go to the collection that contains the tasks you want to move Switch to List View 1. In the top navigation of the collection, click on List View 2. View Issue Statuses 1. You'll see tasks grouped by their current status 2. Click on the small arrow/flash icon next to a status to expand the list of issues 3. Select and Move the Issue 1. Locate the task you want to move 2. On the left side of the issue, you'll see a drag icon (a six-dot “::” icon) 4. Click and drag the task to another status group within the same collection This feature makes it easy to reorganize, reprioritize, and keep your tasks flowing smoothly based on their progress. 🌀 Move Issues Between or Within Sprints 1. Navigate to the Sprint backlog list. 2. Select the issue you'd like to move. 3. Drag it: - From one Sprint to another, or - To a different position within the same Sprint. This drag-and-drop feature ensures tasks stay aligned with your current priorities, helping you rebalance your team’s workload as needed.

Delete an Issue

If an issue or task is no longer needed—or was created by mistake—you can easily remove it to keep your workspace organized. You can delete an issue from any list or board where it appears. Once deleted, the issue will be permanently removed from all associated views. 🔍 How to Delete an Issue 1. Locate the issue on the list or board. 2. Click the options menu (three dots) on the right side of the issue name. 3. Select “Delete” from the dropdown menu. 4. A confirmation prompt will appear—review the details. 5. Click “Delete” to permanently remove the issue. ⚠️ Note: Deleting an issue is permanent and cannot be undone. This helps keep your projects tidy by removing outdated or irrelevant items.

Create Issue Keys

Every task deserves a unique identity. Issue Keys ensure clarity, consistency, and accurate tracking. Issue Keys are unique alphanumeric codes that are automatically assigned to every issue (task) in your project. These keys serve as fixed identifiers, simplifying communication, tracking, and integration across your entire workspace. Oktuple generates them by default, and they cannot be changed — ensuring that every task remains clearly identifiable throughout its lifecycle. Or in the subtasks: 🆔 Why Issue Keys Matter | Purpose | Description | | 🔍 Easy Task Tracking | Quickly locate, reference, and search for tasks using their Issue Key. | | 🔗 Clear Communication | Refer to tasks unambiguously in discussions, comments, and reports. | | 🚫 Avoid Duplication or Errors | Ensure every task is uniquely identified, preventing overlap or confusion. | | 🧩 Integration-Ready | Issue Keys can be used in integrations, reports, and automation workflows without breaking references. | 🛠️ Structure of Issue Keys Oktuple automatically creates Issue Keys in the following format: ABC-123 - ABC: A short project prefix (usually 2–4 uppercase letters) - 123: A sequential number unique to that project This structure is: - ✅ Simple - ✅ Human-readable - ✅ System-friendly ⚙️ How Issue Keys Work in Oktuple - Automatically Generated: A new Issue Key is assigned to each task as soon as it’s created. - Non-Customizable: You cannot change, rename, or restructure an Issue Key. - Globally Unique per Project: Each Issue Key is unique within its project and remains fixed. - Permanent Reference: Even if task details change, the Issue Key remains the same. 🔒 Why Issue Keys Cannot Be Modified Modifying an Issue Key could have serious consequences in terms of data accuracy and team coordination. That’s why Oktuple prevents any alteration to these identifiers. 🚫 Risks of Changing Issue Keys: - ❌ Tracking Confusion: Team members may lose track of updated or renamed tasks. - ❌ Broken Links: Internal or external references to tasks might stop working. - ❌ Inconsistent Reports: Analytics and progress reports could show errors. - ❌ Reduced Transparency: Collaboration between teams becomes more error-prone. 🔐 The Stability You Can Trust Fixed Issue Keys are a pillar of reliable task management. By keeping these identifiers constant: - You ensure historical accuracy across the project's timeline - You maintain clear traceability from creation to completion - You eliminate ambiguity in team conversations, audits, or support ✅ Key Takeaways - Issue Keys are automatically assigned to all issues. - They follow a standard format and are non-editable. - They ensure clarity, consistency, and reliability across your workspace. - Oktuple’s fixed key system is designed for team alignment, reporting accuracy, and seamless integration.