# My Tasks
The **My Tasks** section in **ReleaseOwl** provides users with a centralized view of all tasks assigned to them across different release pipelines and release packages. It ensures task traceability, accountability, and seamless task execution within the SAP deployment lifecycle.
## **Accessing My Tasks**
* Navigate to the **My Tasks** section from the left-hand menu.
* The screen will display a list of tasks assigned to the logged-in user.
### **Overview of My Tasks**
The **My Tasks** screen consists of a structured table displaying task details:
* **Release Pipeline Name**: Displays the associated release pipeline name where the task is created.
* **Task Source**: Identifies the origin of the task, such as *User Story* or *Release Package*.
* **Reference ID**: The specific identifier for the associated User Story or Release Package.
* **Stage Name**: Indicates the current stage (e.g., QA, PROD) where the task is active.
* **Task Name**: Provides a descriptive name for the task (e.g., Peer Review, Production Approval, IT Check Out).
* **Task Type**: Specifies the nature of the task:
* **Approval Task**: Requires explicit approval or rejection.
* **Manual Task**: Requires manual intervention or action from the user.
* **Delivered On**: Shows the date and time when the task was delivered or assigned.
* **Action**: Displays actionable options for the user:
* ***Approve/Reject*****:** For approval tasks.
* ***Complete*****:** For manual tasks.
### **Task Types**
1. **Approval Task**
* Tasks requiring validation or approval from the user.
* **Actions**: Approve or Reject.
2. **Manual Task**
* Tasks that involve user intervention, such as document verification or reporting.
* **Actions**: Complete.
### **Performing Actions on Tasks**
1. **Approval Task**
* Click on **Approve** to approve the task.
* Click on **Reject** to reject the task.
* Provide any required comments or justification during approval/rejection.
2. **Manual Task**
* Click on **Complete** after performing the required manual actions.
* Ensure all pre-requisites for task completion are fulfilled.
* Attachments larger than **1MB** are now **restricted** in **User Stories** and **Test Evidence** tasks to ensure optimal performance and storage usage.
## **Deputy Users**
Deputy users can manage tasks when the primary user is unavailable.
### **Assigning Deputy Users**
1. Click on your **profile icon** in the **top-right corner** and select **Profile**.
2. Click on the **Deputy Users** tab next to "**Projects**."
3. Click the **Add** button, and a **pop-up screen** will appear.
4. **Select Project & User:**
* Select the project for which you want to assign a deputy.
* Search for the **User** in the system and select them.
5. Click the **Create** button to assign deputy permissions to the selected user.
6. When a user story is promoted, the assigned Deputy User will receive an approval request. The Deputy User can then navigate to the **My Tasks** section and go to the **Tasks** tab.
7. In the **Action** column, they can choose to **Approve** or **Reject** the request.
8. When you click on the **Approve/Reject** button, a detailed view will appear, displaying relevant information about the user story.
9. The Deputy User can review this information before making a decision to approve or reject the user story promotion.
10. When the task is approved, a confirmation message will appear. In the **Pipeline Activity** section, you can see the task marked as **completed**, along with the name of the **Deputy User** who approved it.
11. In the **Deputy Tasks** section, the **Deputy User** can view the **task status**, including the **task name, reference ID, stage, task type, delivery time, assigned to, and action**.
12. When you check the **History** in the **My Tasks** section, you can see a record of all actions taken, including approvals, rejections, and task completions, along with the corresponding timestamps and the user who performed each action.
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://releaseowl.gitbook.io/releaseowl-docs/releaseowl-user-guide/my-tasks.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
