# Instruction
- You are an expert in cleaning process data descriptions. Given a task, you are provided with a set of annotation description
data for a certain visual LLM related to human user operation videos. Plus, You are provided with full trace of playwright action,
whic includes action and url before and after the action.
- You need to analyze all the descriptive data and ultimately summarize a complete and reasonable user operation description that can accomplish the given task.
- For each strategy, give a clear list of the low level action sequence.

# Task
Open a new issue to discuss the implementation of dark mode

# Annotation description
## Part 1
### Step-by-Step Actions:

1. **Action:** I click on the "Issues" link in the left sidebar menu.
   - **Page Changes:** The page transitions to the "Issues" section of the GitLab project. The main content area now displays a message: "Use issues to collaborate on ideas, solve problems, and plan work," along with options for creating a new issue and importing issues.
   - **Possible Purpose:** The likely intent is to navigate to the section where issues related to the project can be viewed, managed, or created. This could be for the purpose of tracking bugs, feature requests, or other tasks associated with the project.

2. **Action:** I click on the "New issue" button located in the center of the page.
   - **Page Changes:** A new form titled "New Issue" appears, allowing me to input details for a new issue. The form includes fields for "Title (required)," "Description," "Type," "Assignee," and "Due date." There are also options for adding labels and milestones.
   - **Possible Purpose:** The intention here is to initiate the process of creating a new issue within the project. This action suggests a need to document a specific problem, idea, or task that requires attention and collaboration from team members. 

### Summary:
In this video segment, I first navigate to the "Issues" section of a GitLab project by clicking the corresponding link in the sidebar. This action brings up a page dedicated to issue management. Subsequently, I click the "New issue" button, which opens a form for creating a new issue. These steps indicate a focused effort to either report a problem, propose a new feature, or outline a task that needs to be addressed within the project framework.

---

## Part 2
### Step-by-Step Actions:

1. **Action:** I click on the "Title (required)" text box.
   - **Page Changes:** The text box becomes active, and a placeholder text appears suggesting to "Add description templates."
   - **Possible Purpose:** The likely intent is to enter a title for the new issue being created.

2. **Action:** I type "Implementation of Dark Mode" into the title text box.
   - **Page Changes:** The text "Implementation of Dark Mode" appears in the title field.
   - **Possible Purpose:** The purpose is to clearly define the subject of the new issue.

3. **Action:** I click on the "Description" text box under the "Write" tab.
   - **Page Changes:** The text box becomes active, and the placeholder text "Write a description or drag your files here.." is highlighted.
   - **Possible Purpose:** The intent is to provide more detailed information about the issue.

4. **Action:** I type "Should we implement dark mode?" into the description text box.
   - **Page Changes:** The typed text appears in the description field, and a preview of the text is shown under the "Preview" tab.
   - **Possible Purpose:** The purpose is to elaborate on the issue by posing a question for discussion.

5. **Action:** I scroll down slightly on the page.
   - **Page Changes:** Additional options such as "Assignee," "Milestone," "Labels," and "Due date" become more visible.
   - **Possible Purpose:** The intent is to review or set additional parameters for the issue before submitting it.

6. **Action:** I click the "Submit new issue" button at the bottom of the form.
   - **Page Changes:** The page transitions to a new view showing the details of the newly created issue. The title "Implementation of Dark Mode" and the description "Should we implement dark mode?" are displayed prominently. Additional sections like "Activity," "Tasks," and "Linked items" are now visible.
   - **Possible Purpose:** The purpose is to finalize and submit the new issue for tracking and collaboration.

### Summary:
In this segment, I completed the process of creating a new issue titled "Implementation of Dark Mode" with a descriptive question in the GitLab interface. Each step was methodical, focusing on filling out the necessary fields and ultimately submitting the issue for further action.

# Playwright action
[
  {
    "action_uid": "action_0",
    "idx": 0,
    "action_repr": "frame.clicklocator(\"a\").filter(has_text=\"Issues 0\")",
    "before": {
      "url": "http://ec2-3-135-39-80.us-east-2.compute.amazonaws.com:8023/byteblaze/solarized-prism-theme"
    },
    "after": {
      "url": "http://ec2-3-135-39-80.us-east-2.compute.amazonaws.com:8023/byteblaze/solarized-prism-theme"
    }
  },
  {
    "action_uid": "action_1",
    "idx": 1,
    "action_repr": "frame.clicklocator(\"a\").filter(has_text=\"Issues 0\")",
    "before": {
      "url": "http://ec2-3-135-39-80.us-east-2.compute.amazonaws.com:8023/byteblaze/solarized-prism-theme/-/issues"
    },
    "after": {
      "url": "http://ec2-3-135-39-80.us-east-2.compute.amazonaws.com:8023/byteblaze/solarized-prism-theme/-/issues"
    }
  },
  {
    "action_uid": "link_New issue",
    "idx": 2,
    "action_repr": "frame.clickget_by_role(\"link\", name=\"New issue\")",
    "before": {
      "url": "http://ec2-3-135-39-80.us-east-2.compute.amazonaws.com:8023/byteblaze/solarized-prism-theme/-/issues"
    },
    "after": {
      "url": "http://ec2-3-135-39-80.us-east-2.compute.amazonaws.com:8023/byteblaze/solarized-prism-theme/-/issues"
    }
  },
  {
    "action_uid": "button_Issue",
    "idx": 3,
    "action_repr": "frame.clickget_by_role(\"button\", name=\"Issue\", exact=True)",
    "before": {
      "url": "http://ec2-3-135-39-80.us-east-2.compute.amazonaws.com:8023/byteblaze/solarized-prism-theme/-/issues/new"
    },
    "after": {
      "url": "http://ec2-3-135-39-80.us-east-2.compute.amazonaws.com:8023/byteblaze/solarized-prism-theme/-/issues/new"
    }
  },
  {
    "action_uid": "text_Type Issue Select type Issue Incident",
    "idx": 4,
    "action_repr": "frame.clickget_by_text(\"Type Issue Select type Issue Incident\")",
    "before": {
      "url": "http://ec2-3-135-39-80.us-east-2.compute.amazonaws.com:8023/byteblaze/solarized-prism-theme/-/issues/new"
    },
    "after": {
      "url": "http://ec2-3-135-39-80.us-east-2.compute.amazonaws.com:8023/byteblaze/solarized-prism-theme/-/issues/new"
    }
  },
  {
    "action_uid": "action_5",
    "idx": 5,
    "action_repr": "frame.clickget_by_placeholder(\"Write a description or drag your files here\u2026\")",
    "before": {
      "url": "http://ec2-3-135-39-80.us-east-2.compute.amazonaws.com:8023/byteblaze/solarized-prism-theme/-/issues/new"
    },
    "after": {
      "url": "http://ec2-3-135-39-80.us-east-2.compute.amazonaws.com:8023/byteblaze/solarized-prism-theme/-/issues/new"
    }
  },
  {
    "action_uid": "button_Create issue",
    "idx": 6,
    "action_repr": "frame.clickget_by_role(\"button\", name=\"Create issue\")",
    "before": {
      "url": "http://ec2-3-135-39-80.us-east-2.compute.amazonaws.com:8023/byteblaze/solarized-prism-theme/-/issues/new"
    },
    "after": {
      "url": "http://ec2-3-135-39-80.us-east-2.compute.amazonaws.com:8023/byteblaze/solarized-prism-theme/-/issues/new"
    }
  }
]

# Output format
- 先总结整个任务的Objective，然后按照Strategy-SubStrategy-action三级层次来给出整个过程，
- 接着给出整个操作流程后的观察和有趣的发现，最后严格按照json格式输出三级层次的过程描述。
- 最后的输出json应该是包在```{json}```之间，最底层动作需要包含描述、对应的playwright动作指令顺序编号，以及具体指令内容。

# Example
### Complete User Operation Description to Display Labeled Issues in kkroening/ffmpeg-python

**Objective:** Filter and display all issues labeled as "question" in the kkroening/ffmpeg-python repository.

---

#### **Strategy 1: Navigate to the Repository**
**Low-Level Action Sequence:**
1. **Search for the user "kkroening"**
   - Click the global search bar (placeholder: "Search GitLab").
   - Type "kkroening" and press `Enter`.
2. **Select the user from results**
   - Click the "Users" tab in search results.
   - Click on "Karl Kroening @kkroening" in the user list.
3. **Access the repository**
   - Navigate to the "Personal projects" section.
   - Click on the "ffmpeg-python" project.

---

#### **Strategy 2: Filter Issues by Label**
**Low-Level Action Sequence:**
1. **Open the Issues tab**
   - Scroll to the left sidebar menu.
   - Click the "Issues" tab (displaying the count, e.g., "Issues 402").
2. **Apply label filtering**
   - Click the search/filter bar in the issues list.
   - Select the "Label" dropdown from the filter options.
   - Type or select "question" from the label dropdown.
   - Click the search/apply button to confirm the filter.

---

#### **Final Oberservation**
The issues list will refresh to show only issues with the "question" label. The URL will reflect the filter:
`.../ffmpeg-python/-/issues/?label_name[]=question`.

---

### Key Observations from Playwright Trace
- The final URL after filtering:
  `http://ec2-3-135-39-80.../ffmpeg-python/-/issues/?label_name%5B%5D=question`
  confirms the "question" label filter is applied.
- Critical interactions include selecting the "Label" dropdown and explicitly choosing "question" to refine results.

### Final output
```json
[{
  "strategy" : "Navigate to the Repository",
  "substrategies": [
    {
      "substrategy": "Search for the user \"kkroening\"",
      "actions" : [
        {
          "description": "Click the global search bar (placeholder: \"Search GitLab\"). ",
          "playwright_idx" : 18,
          "playwright_instruction" : "frame.pressget_by_placeholder(\"Search GitLab\")Enter"
        }
      ]
    },
    {
      "substrategy": "Select the user from results",
      "actions" : [
      ]
    }
  ]
},
{
  "strategy" : "Filter Issues by Label",
  "substrategies" : [
  ]
}]
```