Upload 15 files

README.md

@@ -0,0 +1,53 @@
+# AI Evaluation Data
+
+## Getting started
+
+This repo contains datasets used to evaluate the quality of AI features we are developing at GitLab.
+We follow a similar approach to HuggingFace and store the datasets as LFS objects under the `data` folder.
+
+## Datasets
+
+### AI Feature: Duo Chat
+
+#### Context dataset
+
+| Field name     | Type             | Additional notes                                             |
+|----------------|------------------|--------------------------------------------------------------|
+| `context_id`   | STRING           | Valid UUIDs, generated as `uuid4().hex` in Python            |  
+| `context`      | STRING           | JSON string describing one of the GitLab resources           |
+| `context_type` | STRING           | GitLab resource type, either `issue` or `epic`               |
+| `referer_url`  | STRING, NULLABLE | Not used in this iteration, added for Chat API compatibility |
+
+#### Queries dataset
+
+| Field name      | Type             | Additional notes                                             |
+|-----------------|------------------|--------------------------------------------------------------|
+| `query_id`      | STRING           | Valid UUIDs, generated as `uuid4().hex` in Python            |
+| `query`         | STRING           | User query submitted to Duo Chat                             |
+| `context`       | STRING           | JSON string describing one of the GitLab resources           |
+| `resource_id`   | INT, NULLABLE    | GitLab global resource identifier                            |
+| `resource_type` | STRING           | GitLab resource type, either `issue` or `epic`               |
+| `referer_url`   | STRING, NULLABLE | Not used in this iteration, added for Chat API compatibility |
+
+#### Code generations
+
+| Field name      | Type             | Additional notes                                             |
+|-----------------|------------------|--------------------------------------------------------------|
+| `query_id`      | STRING           | Valid UUIDs, generated as `uuid4().hex` in Python            |
+| `query`         | STRING           | User query submitted to Duo Chat                             |
+
+## Usage
+
+Refer to a specific commit SHA1 if you need to get a concrete revision of the dataset.
+
+```shell
+GIT_LFS_SKIP_SMUDGE=1 git clone $URL
+git reset --hard $SHA1
+git lfs pull
+```
+
+## Authors
+
+- Alexander Chueshev - [email protected]
+- Bruno Cardoso - [email protected]
+- David O'Regan - [email protected]

data/duo_chat/v1/jsonl/code_generations/data.jsonl

@@ -0,0 +1,9 @@
+{"query_id":"9fac71b7575041cca8519da583e6aee7","query":"Can you write Python code that sums up two numbers?"}
+{"query_id":"7ed54c92d0b5490eb547bcb957c548df","query":"write me python code to query the rest api server at example.com/api"}
+{"query_id":"18d84a973bf54d0f8b3695748c4a2ced","query":"Write a PHP script that finds 4 hours in a run of sunny weather"}
+{"query_id":"dc992a57ecef4902bee4daf61baea4cb","query":"can you write the regex that will match any value with \"pg\" in it, \"postgres\" or \"patroni\""}
+{"query_id":"794e34170ecf4dadae439433ef7883c3","query":"can you make a mermaid diagram where there is a central box or square with a specific title, two arrows pointing at the box as an input and one arrow getting out the box as an output"}
+{"query_id":"19ab19f137b64cc689599376692285f9","query":"How do I create a new Next JS application named nextjs-support-portal with tailwindcss?"}
+{"query_id":"9f01fb5f9c7c4c4ba4455209cbdb07f9","query":"Create a login page using Next.js, typescript, and tailwindcss"}
+{"query_id":"3e627b091d9c49f69685313007b71fad","query":"Share a gitlab-ci.yml file to cache node files"}
+{"query_id":"da9a496741c243e0812be5b018be3bbf","query":"Write a .gitlab-ci.yml file to test, build and and deploy a javascript application to AWS EC2"}

data/duo_chat/v1/jsonl/context/resources/212dcc2f768b4b9d982d3b2a98d03b42.jsonl

@@ -0,0 +1,2 @@
+{"id": 278964, "name": "GitLab", "path": "gitlab", "namespace_id": 9970}
+{"id": 7764, "name": "www-gitlab-com", "path": "www-gitlab-com", "namespace_id": 6543}

data/duo_chat/v1/jsonl/context/resources/32e65c969f6d46e58f989697de75044a.jsonl

@@ -0,0 +1,6 @@
+{"id": 128440335, "title": "Guest users are not able to subscribe to work items", "author_id": 3860200, "project_id": 278964, "created_at": "2023-05-24 09:55:52 UTC", "updated_at": "2023-10-24 13:56:16 UTC", "description": "A user with guest access should be able to subscribe/unsubscribe from work item notifications despite not having permissions to update the work item.\n\nWe are observing this bug because the GraphQL mutation that updates all widgets [checks `update_work_item` permission](https://gitlab.com/gitlab-org/gitlab/-/blob/master/app/graphql/mutations/work_items/update.rb#L13) when this particular widget requires the more lenient `update_subscription` permission.\n\n### Steps to replicate\n\n- Log in as a `Guest` user and visit an issue in the project, for example `https://gdk.test:3000/gitlab-org/gitlab-test/-/issues/1`\n- The user should be able to reveal the notifications toggle in the top menu\n- Visit the same issue using the work item view for example `https://gdk.test:3000/gitlab-org/gitlab-test/-/work_items/1`\n- The option to toggle notifications is not displayed\n\n![Screen_Recording_2023-05-24_at_11.32.13](/uploads/b28defc97c9690f78748f45df4b4a387/Screen_Recording_2023-05-24_at_11.32.13.mov)", "iid": 412831, "updated_by_id": 3860200, "confidential": false, "lock_version": 0, "time_estimate": 0, "relative_position": -194466693, "closed_at": "2023-07-31 08:59:23 UTC", "closed_by_id": 3860200, "state_id": 2, "blocking_issues_count": 0, "upvotes_count": 0, "work_item_type_id": 1, "namespace_id": 15846663, "due_date": null, "start_date": null, "last_edited_at": null, "last_edited_by_id": null, "discussion_locked": null, "health_status": "on_track", "milestone_id": 2969682, "weight": 2, "epic_id": 835460, "labels": [992791, 10413872, 2492649, 26460213, 3103451, 3412464, 10690700, 3857523, 14918378, 3713902, 2278648, 25541419, 28669354]}
+{"id": 24652824, "title": "Report number of lines per language in repository charts", "author_id": 920678, "project_id": 278964, "created_at": "2017-04-15 17:20:45 UTC", "updated_at": "2023-10-24 13:56:16 UTC", "description": "### Description\n\nAs of now, repository charts report percentage of language in the repo.\nFirst, it is not obvious how this percentage is computed (number of files? number of lines? bytes? what about comments? libraries?). Second, I would love to see some *absolute* data (number of files, lines, bytes).\n\n### Proposal\n\nAs a user I would like to see the number of lines of code per language.\nIdeally, excluding blank lines and comments, but that is optional.\n\n### Documentation blurb\n\nAs for use cases:\n* better understand the repo structure\n* if this is your repo, being able to report the number of lines of your main language\n    * this is one of the metric employers would like to know (I personally was surprised by this question on interview and could not clearly respond)\n* all those use cases for general repo graphs (like pie chart of languages)\n\n### Details\n\n[A useful comment from ZJ](https://gitlab.com/gitlab-org/gitlab/issues/17800#note_214979038):\n\n> Just so its stated explicitly, the language bar on the projects overview page is based on bytes. Iteration over each blob to count the number of lines will be quite expensive and to make it performant on gitlab.com scale will be quite the challenge :smile: Bytes are chosen as Git stores the size of each blob with its name. So if a blob has the path `path/to/file.rb` it can take the extension and detect it's Ruby. It already has the number of bytes, so it can move on.\n\n> Lines however is harder, as now you'd have to either iterate each blob each time, or be clever with caching combined with diffing, which in turn might lead to race conditions.\n\n> That all being said, this would require a new RPC to Gitaly, and gitaly-proto changes. Happy to review MRs there! :cat:\n\n### Potential Workarounds\n\n- Run `scc` in a GitLab CI pipeline: https://github.com/boyter/scc to generate SLOC/etc. reports\n- If API use is acceptable (instead of UI), parts of its output stats can be stored as custom attributes on the project: https://docs.gitlab.com/ee/api/custom_attributes.html#set-custom-attribute", "iid": 17800, "updated_by_id": 5749302, "confidential": false, "lock_version": 3, "time_estimate": 0, "relative_position": -14979600, "closed_at": "2023-01-19 09:38:40 UTC", "closed_by_id": 10822493, "state_id": 2, "blocking_issues_count": 0, "upvotes_count": 579, "work_item_type_id": 1, "namespace_id": 15846663, "due_date": null, "start_date": null, "last_edited_at": "2021-07-17 16:10:21 UTC", "last_edited_by_id": 7536567, "discussion_locked": false, "health_status": null, "milestone_id": 490705, "weight": 8, "epic_id": null, "labels": [11039421, 11469047, 7161201, 1890178, 2677574, 2492649, 1672341, 3103452, 4107658, 10309854, 15237307, 2936416, 2714266, 14918378, 10230929]}
+{"id": 130193114, "title": "Trainee FE Maintainer (Gitlab) - Deepika Guliani", "author_id": 11701495, "project_id": 7764, "created_at": "2023-07-03 05:03:24 UTC", "updated_at": "2023-10-25 04:46:41 UTC", "description": "## Basic setup\n\n1. [x] Read the [code review page in the handbook](https://about.gitlab.com/handbook/engineering/workflow/code-review/) and the [code review guidelines](https://docs.gitlab.com/ee/development/code_review.html).\n1. [x] Understand [how to become a maintainer](https://about.gitlab.com/handbook/engineering/workflow/code-review/#how-to-become-a-project-maintainer) and add yourself as a [trainee maintainer](https://about.gitlab.com/handbook/engineering/workflow/code-review/#trainee-maintainer) in the [team database](https://gitlab.com/gitlab-com/www-gitlab-com/blob/master/doc/team_database.md). (MR: https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/105456+)\n\n## Working towards becoming a maintainer\n\nThese are only guidelines. Remember that there is no specific timeline on this.\n\nAs part of your journey towards becoming a maintainer, you may find it useful to:\n\n1. [ ] Act as a coach in a big deliverable that requires [following the planning step](https://docs.gitlab.com/ee/development/fe_guide/development_process.html#planning-development) as part of the trainee program.\n1. [x] [Shadow a maintainer](#code-review-pairing) while they review an MR. This will allow you to get insight into the thought processes involved.\n1. [x] [Have a maintainer shadow *you*](#code-review-pairing) while you review an MR *as if you were a maintainer* . Ideally, this would be with a different maintainer to the above, so you can get different insights.\n1. [x] *Optional:* [Consider finding a mentor](https://about.gitlab.com/handbook/engineering/workflow/code-review/#trainee-maintainer-mentorship-pilot-program) to help you become a maintainer.\n\nIt is up to you to ensure that you are getting enough MRs to review, and of varied types. All engineers are reviewers, so you should already be receiving regular reviews from Reviewer Roulette. You could also seek out more reviews from your team, or #frontend Slack channels.\n\nYour reviews should aim to cover maintainer responsibilities as well as reviewer responsibilities. Your approval means you think it is ready to merge.\n\nAfter each MR is merged or closed, add a discussion to this issue using this template:\n\n```markdown\n### (Merge request title): (Merge request URL)\n\nDuring review:\n\n- (List anything of note, or a quick summary. \"I suggested/identified/noted...\")\n\nPost-review (opportunities to learn):\n\n- (List anything of note, or a quick summary. \"I missed...\" or \"Merged as-is\")\n\n(Maintainer who reviewed this merge request) Please add feedback, and compare\nthis review to the average maintainer review.\n```\n\nThe purpose of comparing your review to the maintainer's review is to engage in active learning and expand your list of items to consider. Remember, different maintainers are going to identify different issues in the same code. As long as you are not missing large errors or bugs, don't feel like you are doing a bad job if you and a maintainer make different suggestions.\n\n**Note:** Do not include reviews of security MRs because review feedback might reveal security issue details.\n\n**Tip:** There are [tools](https://about.gitlab.com/handbook/tools-and-tips/#trainee-maintainer-issue-upkeep) available to assist with this task.\n\n### Code Review Pairing\n\nMuch like pair programming, pairing on code review is a great way to knowledge share and collaborate on merge request. This is a great activity for trainee maintainers to participate with maintainers for learning their process of code review.\n\nA **private code review session** (unrecorded) involves one primary reviewer, and a shadow. If more than one shadow wishes to observe a private session, please consider obtaining consent from the merge request author.\n\nA **public code review session** involves a primary reviewer and one or more shadows in a recorded session that is released publicly, for example to GitLab Unfiltered.\n\n* If the merge request author is a GitLab team member, please consider obtaining consent from them.\n* If the merge request author is a community contributor, you **must** obtain consent from them.\n* Do **not** release reviews of security merge requests publicly.\n\n## When you're ready to make it official\n\nWhen reviews have accumulated, and recent reviews consistently fulfill maintainer responsibilities, any maintainer can take the next step. The trainee should also feel free to discuss their progress with their manager or any maintainer at any time.\n\n1. [ ] Create a merge request updating [your team member entry](https://gitlab.com/gitlab-com/www-gitlab-com/blob/master/doc/team_database.md) proposing yourself as a maintainer.\n1. [ ] Keep reviewing, start merging :metal:", "iid": 34345, "updated_by_id": 11701495, "confidential": false, "lock_version": 3, "time_estimate": 0, "relative_position": 244675350, "closed_at": "2023-10-25 04:46:41 UTC", "closed_by_id": 11701495, "state_id": 2, "blocking_issues_count": 0, "upvotes_count": 0, "work_item_type_id": 1, "namespace_id": 17069039, "due_date": null, "start_date": null, "last_edited_at": "2023-08-23 08:19:15 UTC", "last_edited_by_id": 11701495, "discussion_locked": null, "health_status": null, "milestone_id": null, "weight": null, "epic_id": null, "labels": [130812, 8595532]}
+{"id": 129393876, "title": "BE: Add support for setting Work Item as parent to an Issue", "author_id": 411701, "project_id": 278964, "created_at": "2023-06-16 08:14:55 UTC", "updated_at": "2023-10-24 13:56:16 UTC", "description": "# Summary\n\n**Note:** This is part of https://gitlab.com/groups/gitlab-org/-/epics/9290, where we are planning to migrate Epics to Work Items.\n\nSince Epics to Work Items migration is scheduled to happen _before_ we're able to migrate legacy Issues to Work Items, we need a way to associate a legacy issue as a child to an Epic Work Item, this is only needed until Issues too are Work Items as then, we get parent-child relationships between Work Items for free via Hierarchy Widget that we built for OKRs via https://gitlab.com/groups/gitlab-org/-/epics/7864.", "iid": 415547, "updated_by_id": 3860200, "confidential": false, "lock_version": 4, "time_estimate": 0, "relative_position": -194466963, "closed_at": "2023-09-11 14:58:26 UTC", "closed_by_id": 3860200, "state_id": 2, "blocking_issues_count": 1, "upvotes_count": 0, "work_item_type_id": 1, "namespace_id": 15846663, "due_date": null, "start_date": null, "last_edited_at": "2023-06-16 08:22:38 UTC", "last_edited_by_id": 411701, "discussion_locked": null, "health_status": "on_track", "milestone_id": 2969687, "weight": 2, "epic_id": 864661, "labels": [992791, 2492649, 3103451, 10690700, 14918378, 10230929, 25541419, 28669354]}
+{"id": 113414743, "title": "Problem Validation: Report Source Lines of Code (SLoC) per Developer or per Repo/Group", "author_id": 10822493, "project_id": 278964, "created_at": "2022-08-17 16:09:48 UTC", "updated_at": "2023-10-24 13:56:16 UTC", "description": "# Recommendation as a result of the research\n- Do NOT implement Lines of Code Contributed _per Developer_. There has a potential negative impact.\n  - For details refer to the opportunity canvas or details section below.  \n- Analytics for Lines of Code _per directory, repo, or group_. \n  - While there are strong hints in this research that suggest this could be of value to users. It seems mostly a nice-to-have feature.\n     - For details refer to the opportunity canvas or details section below.  \n  - The [tentative effort estimation to implement SLoC count on the repo level](https://gitlab.com/groups/gitlab-org/-/epics/9692#tentative-effort-estimation-base-on-first-technical-approach-above) suggests the amount of work is roughly 1.5 dev months. To then offer this on the group level is probably also not expensive. The effort to implement this on the directory level needs to be investigated. \n\n\n\n### Links\nThe full [Opportunity Canvas \"Contribution Metrics based on Lines of Code (SLoC) Contributed per Developer\"](https://docs.google.com/document/d/1lV4GB1tE9e52sotyHj61CAjTXwowCq1IyXBUS5P8xS8/edit?usp=sharing). Internal only. \n\nThe full [Opportunity Canvas \"Expose Lines of Code (SLoC) per Language in Repository Analytics to improve understanding of repo\"](https://docs.google.com/document/d/1wQ8-WbcE5HmYiwWhZFwASWCqAOp-CcUEeeSIJO1ox3M/edit#). Internal only. \n\nThe full [research on Source Lines of Code Q3F23](https://docs.google.com/presentation/d/1xm1eVhwHIMEHA851jIqfhQEHRgAA7PFJ4i2LNdkolp0/edit?usp=sharing). Internal only. \n\n\n# Details: What we learned researching this space\n\n<div>\n\n<table>\n<tr>\n<td>\n\n<span dir=\"\">Assumption</span>\n</td>\n<td>\n\n<span dir=\"\">What we thought</span>\n</td>\n<td>\n\n<span dir=\"\">What we learned</span>\n</td>\n<td>\n\n<span dir=\"\">What we think now</span>\n</td>\n</tr>\n<tr>\n<td>\n\n<span dir=\"\">{What we assumed}</span>\n</td>\n<td>\n\n<span dir=\"\">{What we thought this meant for the solution to this problem}</span>\n</td>\n<td>\n\n<span dir=\"\">{What we learned when we tested this assumption}</span>\n</td>\n<td>\n\n<span dir=\"\">{How these learnings relate to our approach/solution}</span>\n</td>\n</tr>\n<tr>\n<td>\n\n<span dir=\"\">We assumed that following three issues are about related/partly identical needs and are highly important due to their popularity:</span>\n\n[<span dir=\"\">Report number of lines per language in repository charts</span>](https://gitlab.com/gitlab-org/gitlab/-/issues/17800)<span dir=\"\"> 568 upvotes; 18 individual commenters + 15 customer asks; also third highest </span>[<span dir=\"\">priority score</span>](https://app.periscopedata.com/app/gitlab:safe-intermediate-dashboard/970771/User-Request-Issue-Prioritization---Product)<span dir=\"\"> for user requested issues in SCM.</span>\n\n<span dir=\"\">\u00a0</span>\n\n[<span dir=\"\">New contributors graph (lines of code)</span>](https://gitlab.com/gitlab-org/gitlab/-/issues/14875)<span dir=\"\"> 161 upvotes; 25 individual commenters; no customer asks</span>\n\n[<span dir=\"\">Visualize Language Trends over Time</span>](https://gitlab.com/gitlab-org/gitlab/-/issues/12104)<span dir=\"\"> 11 upvotes; 5 customer asks\u00a0</span>\n</td>\n<td>\n\n<span dir=\"\">Due to the high popularity, we thought the community agrees that GitLab should implement \u2018LoC\u2019 and that it would be clear what to implement.\u00a0</span>\n\n<span dir=\"\">The popularity (both among users and among paying customers) was the reason to pick this topic up.\u00a0</span>\n</td>\n<td>\n\n[<span dir=\"\">Reviewing all comments and customer asks on all issues I learned</span>](https://docs.google.com/presentation/d/1xm1eVhwHIMEHA851jIqfhQEHRgAA7PFJ4i2LNdkolp0/edit#slide=id.g191e02223c5_0_2)<span dir=\"\">:</span>\n\n<span dir=\"\">There are **many dimensions** for which SLoC are requested: per **instance**, per **group**, per **project**, per **user**</span>\n\n**<span dir=\"\">Paying customers</span>**<span dir=\"\"> care more about the **group level**, i.e. counting SLoC across all their repos</span>\n\n<span dir=\"\">In some cases, it seems unclear if there is a need for reporting SLoC **per language** or **just SLoC**</span>\n\n<span dir=\"\">There is **little** **detail** to **why** this is helpful nor **how** **often** such metrics would be consulted</span>\n\n[<span dir=\"\">Additional insights from other sources</span>](https://docs.google.com/presentation/d/1xm1eVhwHIMEHA851jIqfhQEHRgAA7PFJ4i2LNdkolp0/edit#slide=id.g17f2129743e_1_0)<span dir=\"\">:</span>\n\n**<span dir=\"\">Some customers do NOT want to see data about individuals</span>**<span dir=\"\"> as their workscouncil would object that and would turn off such a feature.\u00a0\u00a0</span>\n</td>\n<td>\n\n<span dir=\"\">It seems that there are two fundamental use cases:\u00a0</span>\n\n<span dir=\"\">a) report LoC per user (i.e per each contributor to a project)</span>\n\n<span dir=\"\">b) report LoC per \u2018location\u2019 (i.e. per repo, per group or per instance)</span>\n\n<span dir=\"\">It is not very clear how important the topic is to the users/customers.\u00a0</span>\n\n<span dir=\"\">- Conclusion: we should run a survey to assess importance.</span>\n\n<span dir=\"\">It is not clear what they are trying to achieve.\u00a0</span>\n\n<span dir=\"\">- Conclusion: run interviews to understand the why.</span>\n</td>\n</tr>\n<tr>\n<td>\n\n<span dir=\"\">The ask is highly popular AND GitHub has offered this for a long time. It should therefore be a good thing to implement \u2018LoC\u2019.</span>\n</td>\n<td>\n\n<span dir=\"\">I thought GH addresses all asks vocalized in our issues.</span>\n</td>\n<td>\n\n<span dir=\"\">Assessing </span>[**<span dir=\"\">GitHub</span>**<span dir=\"\">\u2019s offering</span>](https://gitlab.com/gitlab-org/gitlab/-/issues/371465#competition)<span dir=\"\"> I found:</span>\n\n<span dir=\"\">GH does **NOT** show **LoC per repo**. (GL also doesn\u2019t.)</span>\n\n<span dir=\"\">GH shows **languages per repo**</span>\n\n<span dir=\"\">- in **percent** in the UI (just like GL)</span>\n\n<span dir=\"\">- in **bytes** in the API (unlike GL which also provides percent)</span>\n\n<span dir=\"\">GH also offers the above for the **org-level**, i.e. is across all repos. (GL doesn\u2019t.)</span>\n\n<span dir=\"\">GH shows </span>[**<span dir=\"\">LoC</span>**<span dir=\"\"> (added/removed) </span>**<span dir=\"\">per contributor</span>**](https://github.com/mrdoob/three.js/graphs/contributors?from=2010-03-21&to=2022-11-22&type=a)<span dir=\"\"> (but **NOT language**).</span>\n\n<span dir=\"\">A </span>[<span dir=\"\">popular tool lets users post their </span>**<span dir=\"\">personal stats</span>**](https://github.com/anuraghazra/github-readme-stats)<span dir=\"\"> on their </span>[<span dir=\"\">profile page</span>](https://github.com/mrdoob)<span dir=\"\">.</span>\n</td>\n<td>\n\n<span dir=\"\">GitHub also does not offer everything that users seem to be asking on our issues.</span>\n\n<span dir=\"\">A reason may be that when they implemented this there was no handy library to report SLoC per language per repo/org.</span>\n\n<span dir=\"\">GH seems to be considering </span>[<span dir=\"\">extensive visualizations of source code</span>](https://githubnext.com/projects/repo-visualization)<span dir=\"\">. The feedback on twitter is positive.\u00a0</span>\n\n<span dir=\"\">If we were to offer _LoC per user_, this would be a me-too feature. The </span>[<span dir=\"\">comments</span>](https://gitlab.com/gitlab-org/gitlab/-/issues/17800#note_293348432)<span dir=\"\"> on the issue suggest that the need is largely driven by the fact that GitHub has had this for a long time and developers consider it as something a source code management platform would normally have.</span>\n</td>\n</tr>\n<tr>\n<td>\n\n<span dir=\"\">We should survey a broad spectrum of users as the issues suggested that commenters also came from different backgrounds but still all seemed to care about the topic \u2018LoC\u2019.\u00a0</span>\n\n<span dir=\"\">We asked a total of </span>[<span dir=\"\">118 users: 64 sw dev; 15 dev team leads; 10 DevOps; etc.</span>](https://docs.google.com/presentation/d/1xm1eVhwHIMEHA851jIqfhQEHRgAA7PFJ4i2LNdkolp0/edit#slide=id.g139bca1b89a_0_1059)\n</td>\n<td>\n\n<span dir=\"\">We thought \u2018LoC\u2019 would be highly popular, given that the issues are so popular.</span>\n</td>\n<td>\n\n[<span dir=\"\">The </span>**<span dir=\"\">survey</span>**<span dir=\"\"> showed</span>](https://docs.google.com/presentation/d/1xm1eVhwHIMEHA851jIqfhQEHRgAA7PFJ4i2LNdkolp0/edit#slide=id.g18dae5a6a9c_0_0)<span dir=\"\">:</span>\n\n<span dir=\"\">Compared to users of other tools, users of GitLab seem to care less about seeing the number of lines contributed\u00a0</span>\n\n<span dir=\"\">GitLab users also care less about the breakdown of languages within a project compared to their peers</span>\n\n<span dir=\"\">In most cases, those newer to their role thought the features were more important</span>\n\n<span dir=\"\">\u00a0</span>\n</td>\n<td>\n\n<span dir=\"\">The survey suggests, \u2018LoC\u2019 seems to be of medium importance (or medium un-importance) for Source Code management.\u00a0</span>\n\n<span dir=\"\">We will need to run interviews to understand more.\u00a0</span>\n</td>\n</tr>\n<tr>\n<td>\n\n<span dir=\"\">The survey suggested that there do not seem to be significant differences in the views of managers vs. individual contributors.\u00a0</span>\n\n<span dir=\"\">Therefore, we interviewed software developers and also asked them about their manager's perspective.\u00a0</span>\n\n<span dir=\"\">8 interviews (7 sw devs, 1 of which is also DevOps engineer / evangelist; 1 prj. mngr (former sw dev))\u00a0</span>\n</td>\n<td>\n\n<span dir=\"\">We would learn in the interviews what the value of \u2018LoC\u2019 would be.\u00a0</span>\n</td>\n<td>\n\n<span dir=\"\">In the </span>[**<span dir=\"\">interviews</span>**<span dir=\"\"> we learned</span>](https://docs.google.com/presentation/d/1xm1eVhwHIMEHA851jIqfhQEHRgAA7PFJ4i2LNdkolp0/edit#slide=id.g17117578ef8_2_21)<span dir=\"\">:</span>\n\n**<span dir=\"\">SLoC</span>**<span dir=\"\"> **_per user_** is **NOT** seen as a **good measure for contribution**.</span>\n\n<span dir=\"\">Some have had **negative experiences** with **metrics to assess performance** (incl. SLoC)</span>\n\n**<span dir=\"\">SLoC _per directory_</span>**<span dir=\"\"> would be **valuable**. Interviewees see this mostly as **nice to have** though.</span>\n\n**<span dir=\"\">Comparing</span>**<span dir=\"\"> growth of SLoC in **_different directories_** that serve different purposes (application vs. test) is **more interesting than** **comparing growth** in SLoC **_per languages_**.</span>\n\n<span dir=\"\">Potentially interesting sub-feature: Using SLoC to **filter by language**: commit lists or repo lists.\u00a0</span>\n</td>\n<td>\n\n<span dir=\"\">One use case seems to be around SLoC _per user:_</span>\n\n<span dir=\"\">_I want an easy way to know who has contributed how many LoC to a project_</span>\u00a0\n\n<span dir=\"\">_so that I can compare their contributions_</span>\u00a0\n\n<span dir=\"\">_a) to feel proud of my own work or_</span>\n\n<span dir=\"\">_b) to track my team members work_</span>\n\n**<span dir=\"\">We should NOT implement this use case: SLoC _per user_</span>**<span dir=\"\"> as it is NOT a good metric.\u00a0</span>\n\n<span dir=\"\">It might be a nice graph to look at for some, but it will have **negative consequences for a few** as their performance would be evaluated based on their contributed SLoC.\u00a0</span>\n\n<span dir=\"\">Do literature research to find further evidence of this outcome.\u00a0</span>\n\n<span dir=\"\">Consider a blog post that reflects our decision. A good timing would be at the same time when we potentially release something else related to SLoC (see below).</span>\n\n<span dir=\"\">-> Take this result and create an **opportunity canvas on SLoC _per user _**as a contribution metric **with the recommendation NOT to do it**.</span>\n\n<span dir=\"\">\u2014--</span>\n\n**<span dir=\"\">SLoC _per directory_ or _per language per repo_</span>**<span dir=\"\"> seems to be valuable to help users get a quick understanding of a repo or the health of different modules. The use case seems to be:</span>\n\n<span dir=\"\">_For a given repo or a module (i.e. directory) , that I see for the first time, I want to know lines of code per language,_</span>\u00a0\n\n<span dir=\"\">_a) so that I can get a quick sense if it will be easy for me to contribute to it given my skill set_</span>\n\n<span dir=\"\">_b) so that I can understand if the module is bloated_</span>\n\n<span dir=\"\">This addresses the needs of individual contributors so it would be part of the **free tier**.</span>\n\n<span dir=\"\">-> Understand the effort to implement this.</span>\n\n<span dir=\"\">\u2014---</span>\n\n**<span dir=\"\">SLoC _per group_</span>**<span dir=\"\"> was not assessed in this series of interviews with developers as this is likely more relevant for administrators, CIO\u2019s, directors, etc.\u00a0</span>\n\n<span dir=\"\">-> reach out to 2 or 3 customers that requested this in one of the original issues to understand what they are trying to achieve and to understand how this could be tiered.\u00a0</span>\n</td>\n</tr>\n<tr>\n<td>\n\n</td>\n<td>\n\n</td>\n<td>\n\n<span dir=\"\">The </span>[**<span dir=\"\">literature research</span>**](https://gitlab.com/gitlab-org/gitlab/-/issues/371465#literature)<span dir=\"\"> showed:</span>\n\n<span dir=\"\">Literature supports the interviewee\u2019s perspective that SLoC is NOT a good metric for measuring contribution.\u00a0</span>\n</td>\n<td>\n\n</td>\n</tr>\n</table>\n\n</div>\n\n\n\n## Definition of Done\n\n- [x] The problem is well understood by the PM to have an understanding summarized in a RICE score (see [Opportunity Canvas \"Contribution Metrics based on Lines of Code (SLoC) Contributed per Developer\"](https://docs.google.com/document/d/1lV4GB1tE9e52sotyHj61CAjTXwowCq1IyXBUS5P8xS8/edit?usp=sharing)). \n- [x] The problem is well understood by the PM to decide if they want to move forward with this idea or drop it. \n  - Recommendation is not to go ahead with Lines of Code _per developer_\n  - Recommendation is to do follow-up research on Lines of Code _per directory, per repo, and per group_\n- [x] N/A: The problem is well described and detailed with necessary requirements for product design to understand the problem\n- [x] N/A: The problem is well described and detailed with necessary requirements for engineering to understand the problem\n\n## Research Issue\n\n_This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc._\n<!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION -->\n*This page may contain information related to upcoming products, features and functionality.\nIt is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes.\nJust like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.*\n<!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION -->", "iid": 371038, "updated_by_id": 10822493, "confidential": false, "lock_version": 24, "time_estimate": 0, "relative_position": -166060152, "closed_at": "2023-07-17 13:55:28 UTC", "closed_by_id": 10822493, "state_id": 2, "blocking_issues_count": 0, "upvotes_count": 0, "work_item_type_id": 1, "namespace_id": 15846663, "due_date": null, "start_date": null, "last_edited_at": "2023-01-19 14:12:21 UTC", "last_edited_by_id": 10822493, "discussion_locked": null, "health_status": null, "milestone_id": 490705, "weight": null, "epic_id": 584663, "labels": [11469047, 2677574, 3103452, 2771176, 10309854, 14918378, 26375975, 11111311]}
+{"id": 130125924, "title": "Update work item metadata with item type and icon", "author_id": 4377833, "project_id": 278964, "created_at": "2023-06-30 20:48:58 UTC", "updated_at": "2023-10-24 13:56:16 UTC", "description": "## Problem\n\nThe current work item detail view includes the work item type in the parent widget, which will be moving elsewhere on the page as part of the updates to the work item detail view. To prepare for this, we are adding the work item type and icon into the header to provide consistency and group similar information together.\n\n## Proposal\n\n- Add the work item type and icon into the header\n- Update text styling to match design\n\n## Acceptance\n\n- UX matches the attached designs. \n\n## Design\n- See design section\n- [Link to Figma](https://www.figma.com/file/1rrKIfHIvBdY8XrQRJbJdF/%5BSpecs%5D-Planning-objects-%26-work-items-detail-view?type=design&node-id=2%3A139685&mode=design&t=Oz6mkfIUgx8RrBbF-1)\n\n## Context\n\n- https://gitlab.com/gitlab-org/plan/-/issues/933#note_1422464575", "iid": 416800, "updated_by_id": 11701495, "confidential": false, "lock_version": 3, "time_estimate": 0, "relative_position": 231484068, "closed_at": "2023-08-08 04:21:45 UTC", "closed_by_id": 11701495, "state_id": 2, "blocking_issues_count": 0, "upvotes_count": 0, "work_item_type_id": 1, "namespace_id": 15846663, "due_date": null, "start_date": null, "last_edited_at": "2023-07-12 18:53:32 UTC", "last_edited_by_id": 4377833, "discussion_locked": null, "health_status": null, "milestone_id": 2969682, "weight": 2, "epic_id": 909555, "labels": [22241940, 2024184, 15714199, 3103451, 2975007, 10690691, 14918378, 10230929, 11111313]}

data/duo_chat/v1/jsonl/context/resources/3a7fdb3d018f4d1a88634a69dec3c01d.jsonl

@@ -0,0 +1,2 @@
+{"id": 9970, "name": "GitLab.org", "path": "gitlab-org", "parent_id": null}
+{"id": 6543, "name": "GitLab.com", "path": "gitlab-com", "parent_id": null}

data/duo_chat/v1/jsonl/context/resources/5abd531b18bb4230b6554d9ed3562ed4.jsonl

@@ -0,0 +1,150 @@
+{"id": 411701, "username": "kushalpandya", "name": "Kushal Pandya"}
+{"id": 13375904, "username": "ramistry", "name": "Rajan Mistry"}
+{"id": 3860200, "username": "egrieff", "name": "Eugenia Grieff"}
+{"id": 419655, "username": "markglenfletcher", "name": "Mark Fletcher"}
+{"id": 346483, "username": "yachmenov_c_", "name": "Yaroslav Yachmenov"}
+{"id": 920678, "username": "dbogatov", "name": "Dmytro Bogatov"}
+{"id": 695248, "username": "lbot", "name": "Lee Matos"}
+{"id": 239547, "username": "wil.rodriguez", "name": "William Rodriguez"}
+{"id": 87854, "username": "DouweM", "name": "Douwe Maan"}
+{"id": 1187333, "username": "jramsay-gitlab", "name": "James Ramsay (ex-GitLab)"}
+{"id": 1512428, "username": "pds-admins", "name": "Dennis Biringer"}
+{"id": 2182793, "username": "craph1", "name": "craph"}
+{"id": 102482, "username": "faithfulman", "name": "Kevin Isley"}
+{"id": 1861874, "username": "shellyniz", "name": "Shelly Nizri"}
+{"id": 709639, "username": "omidontop", "name": "Omid Manikhi"}
+{"id": 1086520, "username": "jeremy-gl", "name": "Jeremy Watson (ex-GitLab)"}
+{"id": 37100, "username": "sampad.abbas1370", "name": "Abbas Aliakbari"}
+{"id": 2346644, "username": "ariaieboy", "name": "AriaieBOY"}
+{"id": 101578, "username": "zj-gitlab", "name": "Zeger-Jan van de Weg"}
+{"id": 2223731, "username": "bobbymcgill", "name": "Bobby McGill"}
+{"id": 2814876, "username": "jim.robbins", "name": "Jim Robbins"}
+{"id": 491329, "username": "Valentin_Seehausen", "name": "Valentin Seehausen"}
+{"id": 3511154, "username": "valexieva", "name": "Virjinia Alexieva"}
+{"id": 1283330, "username": "max-wittig", "name": "Max Wittig"}
+{"id": 4158075, "username": "aakriti.gupta", "name": "Aakriti Gupta"}
+{"id": 5476246, "username": "unitysipu", "name": "Simo Punnonen"}
+{"id": 1612315, "username": "dico.karssiens", "name": "Dico Karssiens"}
+{"id": 4911777, "username": "i.hayden", "name": "Immanuel Hayden"}
+{"id": 635873, "username": "pisarik", "name": "Vlad Blazhko"}
+{"id": 7536567, "username": "hchouraria", "name": "Harsh Chouraria"}
+{"id": 164827, "username": "DarwinJS", "name": "DarwinJS"}
+{"id": 4512390, "username": "djensen", "name": "Dan Jensen"}
+{"id": 3796140, "username": "sarahwaldner", "name": "Sarah Waldner"}
+{"id": 2973161, "username": "robf_at_conversica.com", "name": "Rob Fulwell"}
+{"id": 5791080, "username": "mlockhart", "name": "Mike Lockhart | GitLab"}
+{"id": 786106, "username": "lyle", "name": "Lyle Kozloff"}
+{"id": 424775, "username": "markpundsack", "name": "Mark Pundsack"}
+{"id": 7978344, "username": "robinshine", "name": "Robin Shen"}
+{"id": 4156460, "username": "ogolowinski", "name": "Orit Golowinski"}
+{"id": 5213201, "username": "bmiller1", "name": "Bryan Miller"}
+{"id": 4447217, "username": "ljlane", "name": "Larissa Lane"}
+{"id": 4376883, "username": "stkerr", "name": "Sam Kerr"}
+{"id": 3288671, "username": "cupini", "name": "Brian Cupini"}
+{"id": 7272738, "username": "kategrechishkina", "name": "Kate Grechishkina"}
+{"id": 5250128, "username": "ricardoamarilla", "name": "Ricardo Amarilla"}
+{"id": 5291964, "username": "crispindev", "name": "crispin velez"}
+{"id": 5537005, "username": "cleveland", "name": "Cleveland Bledsoe Jr"}
+{"id": 4748523, "username": "sheininger", "name": "Steffen Heininger"}
+{"id": 10051186, "username": "kballon", "name": "Kent Japhet Ballon"}
+{"id": 4788291, "username": "bgadberry", "name": "Brett Gadberry"}
+{"id": 882141, "username": "1u", "name": "1u"}
+{"id": 154953, "username": "Zandor300", "name": "Zandor Smith"}
+{"id": 2414870, "username": "mason1920", "name": "mason1920"}
+{"id": 2438931, "username": "JasonHuZS", "name": "Jason Hu"}
+{"id": 5329074, "username": "tmccaslin", "name": "Taylor McCaslin"}
+{"id": 196721, "username": "billclark", "name": "Bill Clark"}
+{"id": 3219145, "username": "spprint", "name": "Sven Vet"}
+{"id": 4587928, "username": "cbazan1", "name": "Carlos Bazan"}
+{"id": 688008, "username": "friuns", "name": "friuns"}
+{"id": 4708748, "username": "matt_wilson", "name": "Matt Wilson"}
+{"id": 4122216, "username": "saunved", "name": "Saunved Mutalik"}
+{"id": 261290, "username": "TRPmwiesen", "name": "Matthew Wiesen"}
+{"id": 1276118, "username": "wagnerpinheiro", "name": "Wagner Pinheiro"}
+{"id": 11701495, "username": "deepika.guliani", "name": "Deepika Guliani"}
+{"id": 181229, "username": "leipert", "name": "Lukas 'Eipi' Eipert"}
+{"id": 3540517, "username": "ealcantara", "name": "Enrique Alc\u00e1ntara"}
+{"id": 4477803, "username": "pburdette", "name": "Payton Burdette"}
+{"id": 4545397, "username": "cngo", "name": "Coung Ngo"}
+{"id": 272636, "username": "ddavison", "name": "Dan Davison"}
+{"id": 1607849, "username": "mrincon", "name": "Miguel Rincon"}
+{"id": 3146670, "username": "tristan.read", "name": "Tristan Read"}
+{"id": 11004366, "username": "eduardosanz", "name": "Eduardo Sanz Garc\u00eda"}
+{"id": 2233420, "username": "pslaughter", "name": "Paul Slaughter"}
+{"id": 4846639, "username": "fguibert", "name": "Florie Guibert"}
+{"id": 3732265, "username": "pgascouvaillancourt", "name": "Paul Gascou-Vaillancourt"}
+{"id": 7293390, "username": "jannik_lehmann", "name": "Jannik Lehmann"}
+{"id": 5327378, "username": "f_caplette", "name": "Fr\u00e9d\u00e9ric Caplette"}
+{"id": 10762712, "username": "arfedoro", "name": "Artur Fedorov"}
+{"id": 2890431, "username": "amandarueda", "name": "Amanda Rueda"}
+{"id": 10822493, "username": "tlinz", "name": "Torsten Linz"}
+{"id": 10060155, "username": "leducmills", "name": "Ben Leduc-Mills"}
+{"id": 3507264, "username": "donaldcook", "name": "Donald Cook"}
+{"id": 4377833, "username": "esybrant", "name": "Emily Sybrant"}
+{"id": 4810535, "username": "shoyle1", "name": "Sean John Hoyle"}
+{"id": 100770, "username": "tnir", "name": "Takuya Noguchi"}
+{"id": 8047255, "username": "jhenkel1", "name": "Jayson Henkel"}
+{"id": 12577608, "username": "jesswang_gitlab", "name": "Jess Wang"}
+{"id": 10339034, "username": "manuelgrabowski", "name": "Manuel Grabowski"}
+{"id": 5749302, "username": "mray2020", "name": "Mon Ray"}
+{"id": 9608331, "username": "katiemacoy", "name": "Katie Macoy"}
+{"id": 5291762, "username": "jmandell", "name": "Justin Mandell"}
+{"id": 4554599, "username": "m_gill", "name": "Michelle Gill"}
+{"id": 7351507, "username": "alasch", "name": "Anne Lasch"}
+{"id": 5709669, "username": "mushakov", "name": "Melissa Ushakov"}
+{"id": 8110537, "username": "mcelicalderonG", "name": "Mario Celi"}
+{"id": 4089849, "username": "jackib", "name": "Jacki Bauer"}
+{"id": 4303289, "username": "gweaver", "name": "Gabe Weaver"}
+{"id": 426128, "username": "felipe_artur", "name": "Felipe Artur"}
+{"id": 1642716, "username": "jprovaznik", "name": "Jan Provaznik"}
+{"id": 626804, "username": "pedroms", "name": "Pedro Moreira da Silva"}
+{"id": 853414, "username": "andr3", "name": "Andr\u00e9 Lu\u00eds"}
+{"id": 3199302, "username": "dmishunov", "name": "Denys Mishunov"}
+{"id": 12455340, "username": "andrei.zubov", "name": "Andrei Zubov"}
+{"id": 1149402, "username": "timzallmann", "name": "Tim Zallmann"}
+{"id": 2338505, "username": "mle", "name": "Michael Le"}
+{"id": 4708570, "username": "wayne", "name": "Wayne Haber"}
+{"id": 10554979, "username": "jkunzmann", "name": "Jan Kunzmann"}
+{"id": 3617348, "username": "uhlexsis", "name": "Alexis Ginsberg"}
+{"id": 10219953, "username": "nmarsh2", "name": "Nicholas Marsh"}
+{"id": 4669960, "username": "cdybenko", "name": "Christen Dybenko"}
+{"id": 13640713, "username": "cu00oe", "name": "Cuoooe"}
+{"id": 4418630, "username": "johnhope", "name": "John Hope"}
+{"id": 3483274, "username": "acroitor", "name": "Alexandru Croitor"}
+{"id": 5965371, "username": "jlear", "name": "Jake Lear"}
+{"id": 5961404, "username": "euko", "name": "Eulyeon Ko"}
+{"id": 907418, "username": "abitrolly", "name": "Anatoli Babenia"}
+{"id": 4261879, "username": "dzalbo", "name": "Vladimir Dzalbo"}
+{"id": 11166071, "username": "akashsaini21", "name": "Akash Saini"}
+{"id": 10188931, "username": "Rwarcards762", "name": "Christopher Rice"}
+{"id": 7690791, "username": "rachel_fuerst", "name": "Rachel Fuerst"}
+{"id": 3659089, "username": "ccasella", "name": "Cristiano Casella"}
+{"id": 12249784, "username": "jess_perry", "name": "Jess Perry"}
+{"id": 5534214, "username": "dnsmichi", "name": "Michael Friedrich"}
+{"id": 10735508, "username": "rajkga", "name": "Rajesh Kumar G"}
+{"id": 12672053, "username": "somarandos", "name": "soma randos"}
+{"id": 4587943, "username": "jrreid", "name": "Jamie Reid"}
+{"id": 1873771, "username": "pherlihy", "name": "Patrick Herlihy"}
+{"id": 107951, "username": "vermeeren", "name": "Melvin Vermeeren"}
+{"id": 4867274, "username": "msedlakjakubowski", "name": "Marcin Sedlak-Jakubowski"}
+{"id": 10166363, "username": "marius_ruter", "name": "Marius Aarsnes"}
+{"id": 9676400, "username": "badnewsblair", "name": "Blair Christopher"}
+{"id": 12045345, "username": "EHickson", "name": "Ellie Hickson"}
+{"id": 655908, "username": "mlapierre", "name": "Mark Lapierre"}
+{"id": 4234774, "username": "pcalder", "name": "Phil Calder"}
+{"id": 2535118, "username": "tkuah", "name": "Thong Kuah"}
+{"id": 4391348, "username": "sean_carroll", "name": "Sean Carroll"}
+{"id": 10539876, "username": "dbolkensteyn", "name": "Dinesh Bolkensteyn"}
+{"id": 4888751, "username": "changzhengliu", "name": "Changzheng Liu"}
+{"id": 926632, "username": "joshlambert", "name": "Joshua Lambert"}
+{"id": 4124757, "username": "dsatcher", "name": "Darva Satcher"}
+{"id": 4303163, "username": "rnalen", "name": "Robert Nalen"}
+{"id": 4409816, "username": "a_akgun", "name": "Alper Akgun"}
+{"id": 3714742, "username": "ck3g", "name": "Vitali Tatarintev"}
+{"id": 5041243, "username": "nickbrandt", "name": "Nick Brandt"}
+{"id": 4554611, "username": "hollyreynolds", "name": "Holly Reynolds"}
+{"id": 10593761, "username": "danmh", "name": "Dan Mizzi-Harris"}
+{"id": 4159863, "username": "mmacfarlane", "name": "Matthew Macfarlane"}
+{"id": 13143755, "username": "francoisrose", "name": "Fran\u00e7ois Ros\u00e9"}
+{"id": 5213298, "username": "kbychu", "name": "Kevin Chu"}
+{"id": 832471, "username": "psimyn", "name": "Simon Knox"}

data/duo_chat/v1/jsonl/context/resources/69186119714148bcb143e604a6cc3e2e.jsonl

@@ -0,0 +1 @@
+{"id": 181602, "iid": 344, "created_at": "2023-07-11 21:37:58 UTC", "updated_at": "2023-08-11 00:05:02 UTC", "start_date": "2023-07-28", "due_date": "2023-08-10", "state_enum": 3, "sequence": 3, "group_id": 9970, "iterations_cadence_id": 39982, "description": null, "title": null}

data/duo_chat/v1/jsonl/context/resources/af3b5bd629d0474e87cbb71c95d570ad.jsonl

@@ -0,0 +1,3 @@
+{"id": 2969682, "iid": 90, "title": "16.3", "description": "", "created_at": "2023-02-01 16:03:42 UTC", "updated_at": "2023-02-01 16:03:42 UTC", "state": "active", "lock_version": 0, "start_date": "2023-07-18", "due_date": "2023-08-17", "group_id": 9970, "project_id": null}
+{"id": 490705, "iid": 14, "title": "Backlog", "description": "Issues that we want to do but are not planned right now. Open for contribution from the community.", "created_at": "2018-03-22 13:09:23 UTC", "updated_at": "2018-10-30 14:56:54 UTC", "state": "active", "lock_version": 0, "start_date": null, "due_date": null, "group_id": 9970, "project_id": null}
+{"id": 2969687, "iid": 91, "title": "16.4", "description": "", "created_at": "2023-02-01 16:04:08 UTC", "updated_at": "2023-02-01 16:04:08 UTC", "state": "active", "lock_version": 0, "start_date": "2023-08-18", "due_date": "2023-09-17", "group_id": 9970, "project_id": null}

data/duo_chat/v1/jsonl/context/resources/c49522bba29749a793f14492e2f2ccfd.jsonl

@@ -0,0 +1,12 @@
+{"id": 584663, "iid": 8589, "title": "Report number of lines per language in repository charts", "description": "### Description\n\nAs of now, repository charts report percentage of language in the repo.\nFirst, it is not obvious how this percentage is computed (number of files? number of lines? bytes? what about comments? libraries?). Second, I would love to see some *absolute* data (number of files, lines, bytes).\n\n### Proposal\n\nAs a user I would like to see the number of lines of code per language.\nIdeally, excluding blank lines and comments, but that is optional.\n\n### Documentation blurb\n\nAs for use cases:\n* better understand the repo structure\n* if this is your repo, being able to report the number of lines of your main language\n    * this is one of the metric employers would like to know (I personally was surprised by this question on interview and could not clearly respond)\n* all those use cases for general repo graphs (like pie chart of languages)\n\n### Details\n\n[A useful comment from ZJ](https://gitlab.com/gitlab-org/gitlab/issues/17800#note_214979038):\n\n> Just so its stated explicitly, the language bar on the projects overview page is based on bytes. Iteration over each blob to count the number of lines will be quite expensive and to make it performant on gitlab.com scale will be quite the challenge :smile: Bytes are chosen as Git stores the size of each blob with its name. So if a blob has the path `path/to/file.rb` it can take the extension and detect it's Ruby. It already has the number of bytes, so it can move on.\n\n> Lines however is harder, as now you'd have to either iterate each blob each time, or be clever with caching combined with diffing, which in turn might lead to race conditions.\n\n> That all being said, this would require a new RPC to Gitaly, and gitaly-proto changes. Happy to review MRs there! :cat:\n\n### Potential Workarounds\n- **There is a pipeline template that you can use to count lines of code per language: https://gitlab.com/guided-explorations/code-metrics/ci-cd-extension-scc** \n- Run `scc` in a GitLab CI pipeline: https://github.com/boyter/scc to generate SLOC/etc. reports\n- If API use is acceptable (instead of UI), parts of its output stats can be stored as custom attributes on the project: https://docs.gitlab.com/ee/api/custom_attributes.html#set-custom-attribute", "author_id": 10822493, "group_id": 9970, "updated_by_id": 10822493, "lock_version": 3, "start_date": "2022-09-18", "end_date": "2022-10-17", "created_at": "2022-08-17 11:03:36 UTC", "updated_at": "2023-10-20 19:46:40 UTC", "state_id": "opened", "confidential": false, "color": "#1068bf", "total_opened_issue_weight": 7, "total_closed_issue_weight": 2, "total_opened_issue_count": 4, "total_closed_issue_count": 3, "closed_by_id": null, "closed_at": null, "start_date_sourcing_milestone_id": 2453027, "due_date_sourcing_milestone_id": 2453027, "start_date_fixed": null, "due_date_fixed": null, "start_date_is_fixed": null, "due_date_is_fixed": null, "parent_id": null, "relative_position": null, "start_date_sourcing_epic_id": null, "due_date_sourcing_epic_id": null, "last_edited_by_id": 10822493, "last_edited_at": "2023-01-23 10:05:09 UTC", "labels": [11039421, 11469047, 1890178, 2677574, 2492649, 1672341, 3103452, 4107658, 10309854, 15237307, 2936416, 2714266, 14918378, 10230929, 11111311]}
+{"id": 864661, "iid": 10851, "title": "Work Items - Allow relating of issuables", "description": "# Summary\n\nUntil all issuables records are migrated to work items, we will be in a state where we will have relationships (parent/child & linked) between issuables and work items.\n\nTo that end, we need a way to associate existing Issuables to a Work Item. This effort will act as a \"compatibility-layer\" to make Work Items and Issuables work together while the migration is fully completed.\n\n## Use Cases\n\n1. Parent epic (work item) with child issue (issuable)\n2. Epic (work item) blocked by Issue (issuable) - _new relationship use case being introduced in work items_\n3. ~~Epic (issuable) blocking Objective (work item)~~ - _based on the [high level estimate](https://gitlab.com/groups/gitlab-org/-/epics/10851#note_1488766787) provided by engineering, we will not pursue this use case._", "author_id": 2890431, "group_id": 9970, "updated_by_id": 2890431, "lock_version": 6, "start_date": "2023-08-18", "end_date": "2023-11-10", "created_at": "2023-06-15 18:06:35 UTC", "updated_at": "2023-10-06 18:21:04 UTC", "state_id": "opened", "confidential": false, "color": "#1068bf", "total_opened_issue_weight": 3, "total_closed_issue_weight": 7, "total_opened_issue_count": 2, "total_closed_issue_count": 4, "closed_by_id": null, "closed_at": null, "start_date_sourcing_milestone_id": 2969687, "due_date_sourcing_milestone_id": 3094094, "start_date_fixed": null, "due_date_fixed": null, "start_date_is_fixed": null, "due_date_is_fixed": null, "parent_id": 302007, "relative_position": -32831, "start_date_sourcing_epic_id": null, "due_date_sourcing_epic_id": null, "last_edited_by_id": 2890431, "last_edited_at": "2023-07-26 19:44:01 UTC", "labels": [3103451, 10690700, 14918378, 25541419]}
+{"id": 822061, "iid": 10550, "title": "GitLab Duo Chat [Beta]", "description": "This epic tracks the work to bring the [GitLab Duo Chat](https://docs.gitlab.com/ee/user/ai_features.html#gitlab-duo-chat) system to Beta. This includes the backend where the heavy lifting is done and the WebUI frontend.\n\n**While this epic does NOT include the **[**Chat in VS Code and Web IDE**](https://gitlab.com/groups/gitlab-org/-/epics/10522 \"Bringing GitLab Chat to WebIDE & VSCode via Gitlab Workflow Extension\")** work, it needs to build the backend in such a way that it can support clients other than the WebUI - specifically IDEs**. It must consider that the IDEs may not have the same context as the WebUI. For instance, an IDE may not know the URL of the code file the user is looking at, as the user might have just created it locally. Also the file may have changed on the client. The maturation of the Chat in VS Code and Web IDE is independent of the chat system maturation.\n\n:movie_camera: [Video Walk-through of this epic](https://youtu.be/T645Ppm8oQ0)\n\n## Overall Scope\n\n### Functional scope\n\n* [x] Chat can be opened anywhere on the GitLab Web page. (Excluding [Web IDE](https://gitlab.com/groups/gitlab-org/-/epics/10522 \"Bringing GitLab Chat to WebIDE & VSCode via Gitlab Workflow Extension\"))\n* [ ] Chat answers questions relating to\n  * [x] code the user sees (explain \"this\")\n  * [x] code referenced (with URL)\n  * [x] issue the user sees\n  * [x] issue referenced\n  * [x] epic the user sees\n  * [x] epic referenced\n  * [ ] ~~MR the user sees~~ (removed from beta scope)\n  * [ ] ~~MR referenced~~ (removed from beta scope)\n  * [x] how to use GitLab\n  * [x] recent context from chat history (i.e. Conversational Chat enabled)\n  * [ ] ~~selections (if something is selected e.g. code in the code file, this is added to the context so the chat can answer questions about the selection)~~ (removed from beta scope)\n  * [ ] dummy tools exist that proof the agent can support many more use cases (pipeline context, global issues/epics/code contexts)\n* [ ] If context is not available, [chat responds with its supported contexts](https://gitlab.com/gitlab-org/gitlab/-/issues/415801 \"Self-discoverable capabilities of the chat via responses of the chat itself - e.g. I can't answer this questions but I can answer questions that are about the code you are looking at...\").\n* [x] User can give feedback on their satisfaction with the answers and these answers are analyzed to inform potential prompt engineering tweaks.\n\n### Non-functional scope\n\n* [x] **By design: The tools and the agent(s) must never share context that the user does not have access to.**\n* [ ] The quality bar for what success means ([see below](https://gitlab.com/groups/gitlab-org/-/epics/10550#what-does-success-mean \"GitLab Duo Chat [Beta]\")) is defined, tested and passed\n* [ ] [Perceived speed of answers is at least o.k](https://gitlab.com/groups/gitlab-org/-/epics/10683). from user perspective and there are ideas how to improve it to good.\n  * [x] https://gitlab.com/gitlab-org/gitlab/-/issues/419531+s\n  * [ ] https://gitlab.com/gitlab-org/gitlab/-/issues/419531+s\n* [ ] Errors are tracked.\n\nOne of these two options. Still TBD:\n\n* [ ] Works in the main product for Ultimate users that have toggled the right switches in the settings.\n* [ ] **Access to the Chat is granted if the user has paid the add-on.** The project or the tier of the project's namespace does not matter. [This still needs to be confirmed](https://gitlab.com/gitlab-org/gitlab/-/issues/421295#note_1515265994 \"Discuss: Allow the user to use the chat while not being in a GitLab repo\").\n  * [ ] During the pre-GA phase or pre-addon phase, all SaaS users that are at least in one Ultimate tier, do have access to the chat. [This still needs to be confirmed](https://gitlab.com/gitlab-org/gitlab/-/issues/421295#note_1515265994 \"Discuss: Allow the user to use the chat while not being in a GitLab repo\").\n\n## What does success mean?\n\nGenerally\n\n* AI answers should be _mostly_ correct, helpful and friendly.\n* If the AI does not know it should _mostly_ say that is does not know.\n\n#### How to measure it?\n\n~~We shall consider the experience Beta-ready once we have achieved the following:~~\n\nWe shall consider the experience satisfactory once we have achieved the following:\n\n* Users consider \\>80% of responses `good` or `excellent`\n* Users consider \\<5% of responses `terrible`\n\n(on a 5 point scale: `terrible`, `poor`, `average`, `good`, `excellent`)\n\nSee [details why we opted for this quality bar](https://gitlab.com/gitlab-com/gitlab-OKRs/-/work_items/3555#note_1541945461 \"KR2: GitLab Duo Chat becomes available in beta, including six \u201cspecialized tools\u201d that are also in beta, with a path to general availability in FY24Q4.\").\n\n[This user satisfaction will be assessed by UXR roughly every two to three weeks](https://gitlab.com/gitlab-org/ux-research/-/issues/2513 \"Repeated analysis of user experience with Duo chat as we continuously improve the chat (also considering the outcome of each round of these user tests.)\"). Check the [bottom of our AI Features Dashboard](https://app.periscopedata.com/app/gitlab/1137231/Ai-Features) for these metrics and how they progress toward the goal.\n\n## Work items (remaining as of mid August)\n\n#### Understand in more detail the problem space and how well we address user needs (mostly UXR and Product analytics)\n\n**Outcomes**: More clear understanding of users expectations and which problems they want to solve interactively with the chat.\n\n* https://gitlab.com/groups/gitlab-org/-/epics/11120+\n* https://gitlab.com/gitlab-data/product-analytics/-/issues/1325+\n* https://gitlab.com/gitlab-org/ux-research/-/issues/2513+\n* https://gitlab.com/gitlab-org/gitlab/-/issues/415591+\n\n#### Addressing functional gaps & UX issues\n\n**Outcomes**: better user experience measurable in better scores in user testing\n\n- ~~MR context: https://gitlab.com/gitlab-org/gitlab/-/issues/412430+s~~ (removed from beta scope; see [reason](https://gitlab.com/gitlab-org/gitlab/-/issues/412430#note_1545114583))\n- Epic context: https://gitlab.com/gitlab-org/gitlab/-/issues/422091+s\n- Support selected text: https://gitlab.com/gitlab-org/gitlab/-/issues/422176+s\n- Streaming: https://gitlab.com/groups/gitlab-org/-/epics/10683+s\n- Dummy contexts: https://gitlab.com/gitlab-org/gitlab/-/issues/422187+s\n- Self-discoverable capabilities: https://gitlab.com/gitlab-org/gitlab/-/issues/415801+s\n- [Collection of UX issues to be addressed](https://gitlab.com/groups/gitlab-org/-/epics/10673 \"Chat Integration iteration 1 FE & BE\"). Such as:\n  - new conversation\n  - sync chat across clients\n  - onboarding\n  - expiration time for response\n  - Error messages\n  - feedback mechanism\n  - ~~Global entry point for chat should be enabled for beta release but should not be enabled before we reach our quality target.~~ [Global entry point for chat will only be turned on when we reach the quality target defined above independent of the beta release](https://gitlab.com/gitlab-org/ux-research/-/issues/2465#note_1577201457). \n- **Continuously test user satisfaction with UXR and respond to their feedback**\n\n#### Developing a testing framework\n\n**Outcomes**: enabling efficient development and efficient contribution\n\n- https://gitlab.com/gitlab-org/gitlab/-/issues/422212+s\n- https://gitlab.com/gitlab-org/gitlab/-/issues/422245+s\n\n#### Monitoring quality / stability / speed / cost\n\n**Outcomes**: more trust production readiness of the chat\n\n- https://gitlab.com/groups/gitlab-org/-/epics/11234+\n  - Cost: https://gitlab.com/gitlab-org/gitlab/-/issues/415944+s / https://gitlab.com/gitlab-data/product-analytics/-/issues/1358+s\n  - Error rate: https://gitlab.com/gitlab-org/gitlab/-/issues/421546+s tracks the error rate on individual 3rd party AI requests as well as error rate from the user perspective as responding to their request might require combining multiple 3rd party AI requests. @jprovaznik's assumes there are no errors beyond the 3rd party LLM service that would need to be considered (for instance between the backend and the client). The user level error rate calculation will interpret slow responses \\>20 sec to be errors. The error rates will be tracked in Grafana.\n  - Response time: <span dir=\"\">\\~\\~</span> https://gitlab.com/gitlab-data/product-analytics/-/issues/1366+\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\~\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\~ Will be tracked in Prometheus on the worker level as part of https://gitlab.com/gitlab-org/gitlab/-/issues/421546+s by @jprovaznik. These measurements will include the time for all AI requests necessary to answer the user question but not the time to receive the user input from the frontend and sending the result back to the frontend. The difference should be marginal.\n  - \"Can't answer\" rate: https://gitlab.com/gitlab-org/gitlab/-/issues/422202+s\n\n#### Other work items\n\n- [ ] https://gitlab.com/gitlab-org/gitlab/-/issues/420939+s (switch embeddings provider)\n- [ ] Mature the chat documentation and bring it to its own page.\n- [ ] Label the Chat as beta in the product and in the documentation. \n\n#### Integrate existing stand-alone AI features ???\n\n- Should we integrate existing standalone AI features like _explain this code_ into the chat prior to the Beta release?\n- We should only do so if they reach the quality bar defined above.\n- What interdependencies are there with company announcements?\n\n# What the user can ask\n\n### Questions related to current code\n\nQuestion | Tool test | Quality test \n---|---|---\nCan you explain the code? (Whole file or selected) Explain the selected code | [:white_check_mark:](https://gitlab.com/gitlab-org/gitlab/-/blob/b220eb42587282203362b59eafc3560b5578c9d6/ee/spec/lib/gitlab/llm/chain/agents/zero_shot/executor_real_requests_spec.rb#L222-246) | \nCan you explain function X? | [:white_check_mark:](https://gitlab.com/gitlab-org/gitlab/-/blob/b220eb42587282203362b59eafc3560b5578c9d6/ee/spec/lib/gitlab/llm/chain/agents/zero_shot/executor_real_requests_spec.rb#L222-246) | \nWrite me tests for function X | [:white_check_mark:](https://gitlab.com/gitlab-org/gitlab/-/blob/b220eb42587282203362b59eafc3560b5578c9d6/ee/spec/lib/gitlab/llm/chain/agents/zero_shot/executor_real_requests_spec.rb#L222-246) | \nWhat is the complexity of the code | [:white_check_mark:](https://gitlab.com/gitlab-org/gitlab/-/blob/b220eb42587282203362b59eafc3560b5578c9d6/ee/spec/lib/gitlab/llm/chain/agents/zero_shot/executor_real_requests_spec.rb#L222-246) | \nHow would the code look like in Python? | [:white_check_mark:](https://gitlab.com/gitlab-org/gitlab/-/blob/b220eb42587282203362b59eafc3560b5578c9d6/ee/spec/lib/gitlab/llm/chain/agents/zero_shot/executor_real_requests_spec.rb#L222-246) | \nHow would you refactor the code? | [:white_check_mark:](https://gitlab.com/gitlab-org/gitlab/-/blob/b220eb42587282203362b59eafc3560b5578c9d6/ee/spec/lib/gitlab/llm/chain/agents/zero_shot/executor_real_requests_spec.rb#L222-246) | \nCan you fix the bug in my code | [:white_check_mark:](https://gitlab.com/gitlab-org/gitlab/-/blob/b220eb42587282203362b59eafc3560b5578c9d6/ee/spec/lib/gitlab/llm/chain/agents/zero_shot/executor_real_requests_spec.rb#L222-246) | \nCreate an example of how to use function X | [:white_check_mark:](https://gitlab.com/gitlab-org/gitlab/-/blob/b220eb42587282203362b59eafc3560b5578c9d6/ee/spec/lib/gitlab/llm/chain/agents/zero_shot/executor_real_requests_spec.rb#L222-246) | \nWrite documentation for the selected code | [:x:](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/133770#note_1597887855) | \nCreate a function to validate an e-mail address | [:white_check_mark:](https://gitlab.com/gitlab-org/gitlab/-/blob/b220eb42587282203362b59eafc3560b5578c9d6/ee/spec/lib/gitlab/llm/chain/agents/zero_shot/executor_real_requests_spec.rb#L222-246) | \nCreate a tic tac toe game in Javascript | [:white_check_mark:](https://gitlab.com/gitlab-org/gitlab/-/blob/b220eb42587282203362b59eafc3560b5578c9d6/ee/spec/lib/gitlab/llm/chain/agents/zero_shot/executor_real_requests_spec.rb#L222-246) | \nCreate a function in Python to call the spotify API to get my playlists | [:white_check_mark:](https://gitlab.com/gitlab-org/gitlab/-/blob/b220eb42587282203362b59eafc3560b5578c9d6/ee/spec/lib/gitlab/llm/chain/agents/zero_shot/executor_real_requests_spec.rb#L222-246) | \n\n### Questions related to the current issue or current epic\n\nQuestion | Tool test | Quality test \n---|---|---\nPlease summarize the issue | [:white_check_mark:](https://gitlab.com/gitlab-org/gitlab/-/blob/b220eb42587282203362b59eafc3560b5578c9d6/ee/spec/lib/gitlab/llm/chain/agents/zero_shot/executor_real_requests_spec.rb#L126-144) | \nSummarize with bullet points | [:white_check_mark:](https://gitlab.com/gitlab-org/gitlab/-/blob/b220eb42587282203362b59eafc3560b5578c9d6/ee/spec/lib/gitlab/llm/chain/agents/zero_shot/executor_real_requests_spec.rb#L126-144) | \nCan you list all the labels? | [:white_check_mark:](https://gitlab.com/gitlab-org/gitlab/-/blob/b220eb42587282203362b59eafc3560b5578c9d6/ee/spec/lib/gitlab/llm/chain/agents/zero_shot/executor_real_requests_spec.rb#L126-144) | \nHow old is the epic? | [:x:](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/133770/diffs#note_1597974580) | \nFor which milestone is the issue? And how long until then? | [:white_check_mark:](https://gitlab.com/gitlab-org/gitlab/-/blob/b220eb42587282203362b59eafc3560b5578c9d6/ee/spec/lib/gitlab/llm/chain/agents/zero_shot/executor_real_requests_spec.rb#L126-144) | \nSummarize the comments into bullet points? | [:white_check_mark:](https://gitlab.com/gitlab-org/gitlab/-/blob/31d608f706ac72533502736939cdfe9c077c9975/ee/spec/lib/gitlab/llm/chain/agents/zero_shot/executor_real_requests_spec.rb#L142) | \nQuestions on the actual content: \"What should be the final solution for this issue?\" | [:x:](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/133770/diffs#note_1613052031) | \n\n### Questions relating to the current MR\n\nQuestion | Tool test | Quality test \n---|---|---\nWhat is this MR about? | | \nCan you review this MR? | | \nCan you create a test for the new function in this MR? | | \nCan you simplify this code? | | \n\n### Questions relating how to use GitLab\n\nQuestion | Tool test | Quality test \n---|---|---\nHow do I change my password in GitLab? | [:white_check_mark:](https://gitlab.com/gitlab-org/gitlab/-/blob/b220eb42587282203362b59eafc3560b5578c9d6/ee/spec/lib/gitlab/llm/chain/agents/zero_shot/executor_real_requests_spec.rb#L248-261) | \nHow do I fork a project? | [:white_check_mark:](https://gitlab.com/gitlab-org/gitlab/-/blob/b220eb42587282203362b59eafc3560b5578c9d6/ee/spec/lib/gitlab/llm/chain/agents/zero_shot/executor_real_requests_spec.rb#L248-261) | \nHow do I clone a repository? | [:white_check_mark:](https://gitlab.com/gitlab-org/gitlab/-/blob/b220eb42587282203362b59eafc3560b5578c9d6/ee/spec/lib/gitlab/llm/chain/agents/zero_shot/executor_real_requests_spec.rb#L248-261) | \nHow do I create a template? | [:white_check_mark:](https://gitlab.com/gitlab-org/gitlab/-/blob/b220eb42587282203362b59eafc3560b5578c9d6/ee/spec/lib/gitlab/llm/chain/agents/zero_shot/executor_real_requests_spec.rb#L248-261) | \nWhat is DevOps? What is DevSecOps? | [:x:](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/133770/diffs#note_1597971516) | \n\n### Follow-up questions\n\n#### Basic follow-up question that only require the last answer as context\n\n- Can you simplify your answer?\n  - Context: there is at least one bot-answer in history.\n  - Result: the last answer is simplified\n  - Tool test: [:white_check_mark:](https://gitlab.com/gitlab-org/gitlab/-/blob/b220eb42587282203362b59eafc3560b5578c9d6/ee/spec/lib/gitlab/llm/chain/agents/zero_shot/executor_real_requests_spec.rb#L167-218)\n  - Quality test:\n- Can you translate your answer to German?\n  - Context: there is at least one bot-answer in history.\n  - Result: the last answer is translated\n  - Tool test:\n  - Quality test:\n- Can you explain your third point in different words?\n  - Context: there is at least one bot-answer in history and the last answer contains a bulleted or numbered list (because that was the assignment of the previous question).\n  - Result: the third point of the last answer is explained with different words.\n  - Tool test:\n  - Quality test:\n\n#### Advanced follow-up questions that require the last answer + the context that was pulled for creating the last answer\n\n- Iterative in depth analysis of an issue\n  - Context: there is at least one bot-answer in history and the last answer required the usage of a Tool to generate it.\n  - Result: The answer contains information that was available in the result of the previously used Tool but not contained in any of the answers.\n  - Example:\n    - User is on: https://gitlab.com/gitlab-org/gitlab/-/issues/17800\n    - User asks: Can you identify the unique use cases the commenters have raised on this issue?\n    - Bot:\n      - uses `<issue tool to collet the issue context>`\n      - answers `<with bulleted or numbered list of use cases>`\n      - Tool test:\n      - Quality test:\n    - User asks: Can you sort this list by the number of users that have requested the use case and include the number for each use case? Can you include a verbatim for the two most requested use cases that reflect the general opinion of commenters for these two use cases?\n    - Bot:\n      - uses `<history that includes the result of previously used tool but does not call the tool again>`\n      - answers `<with sorted list that contains the number of users that asked for each use case and two verbatim>`\n      - Tool test:\n      - Quality test:\n- Can you expand on the last paragraph?\n  - Context: there is at least one bot-answer in history and the last answer required the usage of a Tool to generate it.\n  - Result: The answer contains information that was available in the result of the previously used Tool but not contained in any of the answers.\n  - Tool test:\n  - Quality test:\n\n- Can you detail the purpose of the code-owner class?\n  - Context: there is at least one bot-answer in history and the last answer required the usage of a Tool to generate it.\n  - Result: The answer contains information that was available in the result of the previously used Tool but not contained in any of the answers.\n  - Tool test:\n  - Quality test:\n\n#### Advanced follow-up questions that require multiple recent answers + multiple contexts that were pulled for creating the last answer (NOT PART OF BETA)\n\n- Comparison of two issues\n  - Example\n    - History: continued from above big example \"Iterative in depth analysis of an issue \"\n    - User switched to: https://gitlab.com/gitlab-org/gitlab/-/issues/12104\n    - User asks: How are the use cases raised in this issue different or the same?\n    - Bot:\n      - uses `<issue tool to collet the issue context for 12104>`\n      - uses `<history that includes the result of previously used tool to get context for 17800 but does not call the tool again>`\n      - answers `<with two list: one with similarities and one with differences>`\n  - Tool test:\n  - Quality test:\n\n#### Questions that the user did not formulate clear enough should result in a question from the AI to clarify the question\n\n- User: `How do I create a template?`\n  - Although this question seems to be reasonable, it's not clear what kind of template is meant. I think the only solution for such questions is to have a means for the AI to ask a clarifying question, for example the following\n- Bot: `The term template is used widely in the context. Could you be more specific which kind of template you would like to create?`\n- Tool test:\n- Quality test: \n\n## What will not be supported\n\n* We will not support other languages than English. That does not mean it won't work, but it will not have been tested at all. We made this decision to prevent a significant increase in complexity.\n* We will not support comparing and relating different contexts to another. E.g. what is the difference between this issue and issue xyz. This is GA scope.\n* We will not support global contexts for repos / issues / epics / etc. This may be covered before GA though.\n\n## Marketing\n\n* https://gitlab.com/gitlab-com/marketing/brand-product-marketing/product-marketing/-/issues/7274+s\n\n## Related\n\n* [Research work prioritization for the GitLab Chat in Q2 FY24](https://gitlab.com/gitlab-org/ux-research/-/issues/2501#note_1421246798 \"Research Prioritization for Fulfillment, ModelOps, and Analytics - Q2FY24\")\n* https://gitlab.com/gitlab-org/ux-research/-/issues/2604#note_1515310932\n* https://gitlab.com/gitlab-org/gitlab/-/issues/423325+s\n\n## Literature\n\n(some random links)\n\n* Research result: [Questions users want to ask](https://gitlab.dovetailapp.com/projects/6wL9UBVQCbOpaC6WLu22su/v/ukXfzRL2lbYwiKe5Bbdyu/present/1WktHKngt2oO4NpHzBEf9I)\n* [What parts of development workflow make sense for AI tools](https://stackoverflow.co/labs/developer-sentiment-ai-ml/#h2-what-parts-of-development-workflow-make-sense-for-ai-tools)\n* https://www.honeycomb.io/blog/hard-stuff-nobody-talks-about-llm\n* https://newrelic.com/platform/new-relic-grok\n* https://twitter.com/amanrsanger/status/1660729100137553920\n* Test framework for code suggestions: https://gitlab.com/gitlab-org/gitlab/-/issues/415381+", "author_id": 3796140, "group_id": 9970, "updated_by_id": 367626, "lock_version": 64, "start_date": "2023-05-18", "end_date": "2023-07-31", "created_at": "2023-05-11 21:27:09 UTC", "updated_at": "2023-10-24 13:56:17 UTC", "state_id": "opened", "confidential": false, "color": "#1068bf", "total_opened_issue_weight": 17, "total_closed_issue_weight": 11, "total_opened_issue_count": 57, "total_closed_issue_count": 80, "closed_by_id": null, "closed_at": null, "start_date_sourcing_milestone_id": null, "due_date_sourcing_milestone_id": null, "start_date_fixed": null, "due_date_fixed": "2023-07-31", "start_date_is_fixed": null, "due_date_is_fixed": true, "parent_id": 785400, "relative_position": -12825, "start_date_sourcing_epic_id": 853405, "due_date_sourcing_epic_id": 834262, "last_edited_by_id": 367626, "last_edited_at": "2023-10-20 22:05:32 UTC", "labels": [30251403, 31167182, 30402137, 3207279, 31287867, 31287876, 23545476]}
+{"id": 657742, "iid": 9290, "title": "\u2708\ufe0f Work Items - Migrate Epics to Work Items", "description": "## Summary\n\nEpics are a flexible tool to support the portfolio planning process. Regardless of your planning methodology, we think epics can be a critical part of your planning toolkit. However, our legacy epics architecture was built as a standalone object separate from other features like issues and requirements. Given this, we're inefficient with our development efforts of common widgets and limited in building scalable relational models.\n\nAs part of our move to [work items](https://gitlab.com/groups/gitlab-org/-/epics/6033 \"[INITIATIVE] Work Items\") we will migrate the legacy epic features, related boards, views and data to the new architecture.\n\nFor most features, we are conscious to not change the user\u2019s mental model so the transition to the work items framework is not abrasive. For some features however, we must implement the feature in a new way due to the functional differences between the work items layout and the issuables layout. Additionally, there are some features which need UX improvement, like designs uploads. In this case, we will look for opportunities to improve known usability challenges as we build the feature on work items.\n\nMigrating epics to work items will unlock dozens of feature improvements and bug issues just by being on the shared work items framework. Notable improvements on day 1 will be assignees, milestones, and nesting that carries through to tasks which will allow for rolled up features like total weight of an epic.\n\nThis epic will be used to track the work needed for epic migration.\n\n## General Work Item Context\n\nDifferent object types require different fields and different context, depending on what job they are being used to accomplish. Instead of each object type diverging into a separate model, we can standardize on an underlying common model that we can customize with the widgets (one or more attributes) it contains. Epics, issues, requirements, and others all have similar but just subtle enough differences in common interactions that the user needs to hold a complicated mental model of how they each behave. Transitioning all three will provide a more efficient user experience.", "author_id": 2890431, "group_id": 9970, "updated_by_id": 2890431, "lock_version": 28, "start_date": "2023-08-01", "end_date": "2023-10-31", "created_at": "2022-11-17 21:14:25 UTC", "updated_at": "2023-10-23 20:06:12 UTC", "state_id": "opened", "confidential": false, "color": "#217645", "total_opened_issue_weight": 48, "total_closed_issue_weight": 188, "total_opened_issue_count": 56, "total_closed_issue_count": 128, "closed_by_id": null, "closed_at": null, "start_date_sourcing_milestone_id": null, "due_date_sourcing_milestone_id": null, "start_date_fixed": "2023-08-01", "due_date_fixed": "2023-10-31", "start_date_is_fixed": true, "due_date_is_fixed": true, "parent_id": 273703, "relative_position": -43989, "start_date_sourcing_epic_id": null, "due_date_sourcing_epic_id": null, "last_edited_by_id": 2890431, "last_edited_at": "2023-06-15 16:32:16 UTC", "labels": [29655839, 27355480, 28630294, 29821275, 1672342, 3103451, 10690700, 14918378, 10230929, 25541419]}
+{"id": 785400, "iid": 10219, "title": "GitLab Duo Chat", "description": "## Vision: enable users to solve all DevSecOps tasks via an AI chat, so they can work faster, more efficiently and with less context switching\n\nOur vision is to enable users to work on all their DevSecOps tasks via an AI chat called GitLab Duo Chat. Duo chat would have access to everything the user has access to, so it can get the context when answering to user questions. Duo is backed by a large language model and tools that allow it to process large amounts of data quickly and thereby accelerate how users can solve tasks. \n\nIt will help developers understand unknown code and code bases more quickly; suggest tests; or refactor code. Security professionals will be supported in understanding and fixing vulnerabilities faster. Product managers can weed though comments automatically to summarize them or extract unmet needs and generate feature definitions based on these findings. ...\n\nDuo will consider the chat history in its answers. History is even preserved across different touch points so users can ask follow-up questions even if they switch for example from the GitLab UI to their IDE. The history will contain the data previously collected via tools, so follow-up questions can drill deeper into the subject matter. \n\nThe chat will be available in the GitLab Web UI, in its WebIDE, and via Extensions in popular desktop IDEs. \n\n### Evidence\n[Today developers already use AI heavily for writing code (83% of developers) and Debugging and getting help (49%)](https://survey.stackoverflow.co/2023/#developer-tools-ai-tool). [54% use copilot for development](https://survey.stackoverflow.co/2023/#most-popular-technologies-ai-dev). [70+% of Copilot users want to use it again next year](https://survey.stackoverflow.co/2023/#section-worked-with-vs-want-to-work-with-ai-developer-tools). However, beyond coding, there is a [huge interest to use AI for Documenting code (50%), Learning about a codebase (49%), Testing code (55%), Project planning (39%), Committing and reviewing code (50%), Deployment and monitoring (45%)](https://survey.stackoverflow.co/2023/#developer-tools-ai-tool-interested)\n\n## Architecture and technical implementations\n\n### Connections\n\nAs we want to offer the chat experience both in our Web Application as in our IDE plugins we need to target especially that the main work is happening in the Rails Chat implimentation and have couple of thin clients.\n\n![image](/uploads/729ed32700c8bf86e07b789067957af7/image.png)\n\n### Technical Parts\n\n![image](/uploads/66ca445581cdf29720432b94be06043c/image.png)\n\n#### 1. Switch Agent\n\nWe need to understand in the first step how what the input of the user is about (question/task/etc.) to then have a specific tool gather an answer. This will be done by using an LLM by providing a specialized prompt \n with descriptions of the tools available, examples and the question. The agent will then give us the name of the preferred tool to solve the whole task or parts of it. Agents are capable of combining tools also to answer questions. The tools are then queried for giving answers. \n\nAdditional Explanations\n\n* https://python.langchain.com/en/latest/modules/agents/getting_started.html\n*  https://huggingface.co/docs/transformers/transformers_agents#whats-happening-here-what-are-tools-and-what-are-agents\n\n#### 2. Available Tools for context\n\nThe switch agent is provided a set of tools that is available per individual page, each tool has a description (e.g. \"useful for when you need to answer questions how to use gitlab the product and its features\"). \n\n##### Local Context\n\nFor each page in GitLab we want to provide a tool specific for the page's context (e.g. Code File, Issue, Epic, ...). \n\nTo start with the MVC we will target to build a universal data reader tool, which gets all properties of a current's object and will try to answer any question just by that. \n\nAs a next step we then can replace per specific page this universal context tool with one customized to the specific page to not only provide information but also task execution suggestion (e.g. \"Set the current milestone\")\n\n##### Universe Context\n\nWhile a user is on a specific page they still want to interact with the current project or namespace to ask questions about the project, issues, epics, CI/CD, monitoring etc.. \n\n##### Personal Context\n\nA user might also want to ask about their personal todo's, issues, etc.\n\n##### GitLab Documentation Context\n\nThe current GitLab Chat (formerly known as Ask Tanuki) will be available to help users find specific information or help on a feature.\n\n##### General coding + info questions\n\nThe chat should also be able to help on any unrelated code, project management, UX or other DevSecOps related questions.\n\n#### 3. Chat Tools\n\nIt's crucial to realize that we're not directly creating a specific code-related feature. Instead, we're building a tool that lets the LLM access code and other details. This tool helps address user questions or tasks. For instance, we're not making a feature called \"Explain the code.\" Instead, we're developing a tool that handles anything about code. This tool provides code snippets, actions, and more. The LLM then uses this code to provide explanations. Additionally, the tool can enhance prompts behind the scenes for specific tasks, giving more detailed instructions about what's needed.\n\n##### Universal Object access tool\n\nFor our MVC we start with a tooling that gets the keys of all attributes and is then able to access all values to fulfill a task. e.g. Summarize the description, the LLM is going to determine to look for a description or something similar and will then be able to fulfill the specific task on that description.\n\n##### VectorQARetrieval Tool\n\nWe are using Embeddings for our current documentation and in the future on Issues, Epics, Code, etc. to do different large content tasks like Semantic search. So we should abstract a tool to access and retrieve any kind of documents/objects based on Embeddings. \n\n### Other parts\n\n#### System prompt\n\nWe need to provide a general system prompt so the chat model knows what we are expecting and what it should discuss and what not.\n\n#### Example Questions/Tasks\n\nWe should be able to have an easy way for each product group to provide for the chat examples what a user can ask on the current page for example. So when the users opens a chat they get a better understanding what might be possible. We can also investigate if we can do automated examples in a second step.\n\n-----\n\n### MVC\n\n[GitLab Chat MVC](https://gitlab.com/groups/gitlab-org/-/epics/10220)\n\n### Proposal\n\nMany of the feature ideas proposed in https://gitlab.com/gitlab-org/gitlab/-/issues/402649 that we want to realize will require an interaction with an AI. Instead of every feature implementing its own interaction and having a disjointed experience for the user there should be a small number of interaction concepts for the whole of GitLab. \n\n#### Target Initial User Journey\nPlease note that this user journey only reflects three use cases right now - ask doc questions, explain this code, and write tests. We will include more later, but we want to get mocks created for these to get feedback.\n\n1. Sarah opens the chat window from clicking the item in the sidebar\n2. Sarah asks \"How do I to protect a branch\"\n3. Chat responds with an explanation and a link to our docs\n4. Sarah asks another question about controlling who can merge on a protected branch\n5. Chat responds again with another explanation and another link to our docs\n6. Sarah gives feedback that the response was helpful and closes the chat\n7. Sarah is in the Web IDE. She is typing code and accepts a suggestions that the chat bot makes, but has a question about it.\n8. She highlights the block of code, clicks a button to launch the chat, and is presented with three options:\n   - [Explain this code](https://gitlab.com/groups/gitlab-org/-/epics/10218+)\n   - Write Tests for this code\n   - Refactor my code\n8. Sarah selects the quick action \"explain this code\"\n9. Chat responds with an explanation\n10. Sarah clicks another option \u201cWrite tests for this code block\u201d\n11. Chat responds with some tests\n12. Sarah copies it and puts it in her code \n13. Sarah closes the chat window\n14. Sarah comes back and wants to see the tests that she previously asked about, so she goes to the list of saved conversations and clicks on the one that was about writing test cases\n\n#### Longer term goals\n\nWe will include the following abilities in the chat bot:\n\n1. Explain this vulnerability\n2. Resolve this vulnerability\n3. Create an issue or a merge request\n\n### Intended users\n\n**ALL** personas as described in https://about.gitlab.com/handbook/product/personas/\n\n### Available Tier\n\n ~\"GitLab Ultimate\" \n\n### What we know/Background\n\n* Interactions with LLMs are particularly strong when used interactively with follow-up questions (e.g. as demonstrated by https://martinfowler.com/articles/2023-chatgpt-xu-hao.html)\n* LLM can _understand_ context across multiple questions and answers\n* Existing LLM chat experiences from different providers keep all history of the communication in threads. This maybe something to consider as well, although a quick internal survey showed that out of 144 respondents only 44 ever went back to their chat history older than three days.\n* An endless chat, may feel more like a friend that knows you, than anonymous one-answer-at-a-time answering machine. We can also use the history of chat to know at which experience level the answer needs to be formulate. E.g. junior developer may ask to have answers elaborated further many times, then we can change the prompt to AI to come up with a more elaborate answer from the get go for this user. \n* There a limit to the length of an input \n* We might use other AI tools and mix them. These other AIs may not lend themselves to interactive dialog and might have different limits and possibilities. We would have to deal with that. \n* We have to deal with:\n   * Service not available / very slow\n   * User reached quota\n\n\n\n### Legal and privacy requirements\n* Legal and privacy requirements are being discussed [here](https://gitlab.com/gitlab-com/legal-and-compliance/-/issues/1461) and will be added to this issue once these have been finalized.\n* [This conclusion regarding how we can enable AI-based comment summaries by adding `Created with AI`](https://docs.google.com/document/d/1mgrUNfbUp0GxvsUHoC1Azupx39gfJcSilxe2sqYgQ60/edit#bookmark=kix.qjc46bbkoisp) might be applicable to other use cases like Explain Code as well.", "author_id": 10822493, "group_id": 9970, "updated_by_id": 10822493, "lock_version": 38, "start_date": "2023-03-18", "end_date": "2023-11-10", "created_at": "2023-03-31 10:36:15 UTC", "updated_at": "2023-10-23 16:33:18 UTC", "state_id": "opened", "confidential": false, "color": "#1068bf", "total_opened_issue_weight": 37, "total_closed_issue_weight": 47, "total_opened_issue_count": 140, "total_closed_issue_count": 180, "closed_by_id": null, "closed_at": null, "start_date_sourcing_milestone_id": 2910456, "due_date_sourcing_milestone_id": null, "start_date_fixed": null, "due_date_fixed": null, "start_date_is_fixed": null, "due_date_is_fixed": null, "parent_id": 762022, "relative_position": -28728, "start_date_sourcing_epic_id": null, "due_date_sourcing_epic_id": 899417, "last_edited_by_id": 1646689, "last_edited_at": "2023-08-10 21:52:45 UTC", "labels": [30251403, 30402137, 3207279, 31287876, 29780827]}
+{"id": 677568, "iid": 9450, "title": "\ud83c\udf1f Plan Work Items - UX Vision and Validation", "description": "This epic holds work related to defining what the UX is like for planning objects leveraging work items architecture.\n\nThis includes\n\n- overall vision of the IA, navigation and structure of planning objects\n- detail pages for Issues, Tasks, Requirements and Epics\n- some iteration on Tasks\n\n### Tracking our work and where to find designs\n\nThis table tracks work that's ready for design work - we are confident we need this page, pattern, feature, etc, and we know some things about how people want to use them.\n\n| Name & Issue Link | UX Status | DRI |\n|-------------------|-----------|-----|\n| https://gitlab.com/gitlab-org/gitlab/-/issues/411841+ | In progress | ~\"group::project management\" |\n| [Viewing items in context: drawer, modal, etc](https://gitlab.com/gitlab-org/gitlab/-/issues/409886) | 15.6 | ~\"group::product planning\"  |\n| https://gitlab.com/gitlab-org/gitlab/-/issues/414535+ | In Progress | ~\"group::product planning\" |\n| https://gitlab.com/gitlab-org/gitlab/-/issues/414539+ | In Progress | ~\"group::product planning\" |\n| [Interaction patterns of editing/adding issue attributes](https://gitlab.com/gitlab-org/gitlab/-/issues/368944 \"Work item widget patterns\") | In Progress | ~\"group::project management\" |\n| https://gitlab.com/gitlab-org/gitlab/-/issues/387214+ | In Progress | ~\"group::project management\" |\n| Overall IA for Epics, Issues, Tasks: https://gitlab.com/gitlab-org/gitlab/-/issues/410068+ | This is currently on hold pending work on Problems with hierarchy, access and permission ... ( gitlab#414964 - closed) |  |\n| UX for Issues in Groups |  |  |\n| List Views for Planning Objects (Epics, Issues, Tasks) |  |  |\n| Saved Views and/or Collections |  |  |\n| Board Views |  |  |\n| Roadmap Views |  |  |", "author_id": 3617348, "group_id": 9970, "updated_by_id": 5041243, "lock_version": 19, "start_date": "2021-02-18", "end_date": "2023-07-17", "created_at": "2022-12-09 17:44:04 UTC", "updated_at": "2023-09-14 16:47:07 UTC", "state_id": "opened", "confidential": false, "color": "#1068bf", "total_opened_issue_weight": 12, "total_closed_issue_weight": 88, "total_opened_issue_count": 39, "total_closed_issue_count": 81, "closed_by_id": null, "closed_at": null, "start_date_sourcing_milestone_id": null, "due_date_sourcing_milestone_id": null, "start_date_fixed": null, "due_date_fixed": "2023-07-17", "start_date_is_fixed": null, "due_date_is_fixed": true, "parent_id": 273703, "relative_position": -44245, "start_date_sourcing_epic_id": 302607, "due_date_sourcing_epic_id": 302006, "last_edited_by_id": 5041243, "last_edited_at": "2023-09-14 16:47:07 UTC", "labels": [2024184, 3103451]}
+{"id": 273703, "iid": 6033, "title": "[INITIATIVE] Work Items", "description": "## Problem\n\n- Epics, Issues, and Requirements all have similar but just subtle enough differences in common interactions that it requires the user to hold a complicated mental model of how each behaves.\n- Using labels to denote Issue types is cumbersome and makes every reporting view more complex (because you have to include all labels in picking which you want to show analytics for).\n- [Issue Types](https://app.periscopedata.com/app/gitlab/654183/Plan-stage-.com-events) are one of the top two use cases of labels. Given that, we should provide first-class support for it.\n- Issues are starting to feel cluttered as we add more and more capabilities to them. There is no consistent pattern for how to surface relationships to other objects, there is not a coherent interaction model across Issuables, and the various implementations of [issue types](https://docs.gitlab.com/ee/development/issue_types.html) are feeling the pain of the lack of flexibility and extensibility.\n\n## Solution\n\n* Create a new architecture called Work Items that will support Issues, Epics, Requirements, and future planning items. This will allow us to enhance the experience for Epics and Requirements and expose more functionality that is available in Issues to them.\n* We cannot re-use our existing Issues since the architecture is not flexible and scalable enough to accommodate all the features needed for our future vision.\n* We are also taking this opportunity to change terminology from being centered around \"Issues\" to \"Work Items\". The term \"Issues\" is not comprehensive enough for all the capabilities we plan to build in the future.\n* We will start this effort by creating a new work item called **Tasks**. This was a long-standing ask that provides net new customer value. Starting with a new item also reduces the risk of changing an existing capability like Issues, which has significant traffic and is part of key customer workflows today.\n* The second item to use Work Items will be Requirements. It's an existing item that has fewer data elements and lower usage. Migrating a lower usage item will allow us to develop and test customer education patterns about the new experience.\n* We will build capabilities in the new Work Items framework until we have reached parity with Epics and Issues. Then we will migrate them to use Work Items.\n\n### Roadmap By Product Group\n\nSee [this spreadsheet](https://docs.google.com/spreadsheets/d/1D3QZ5L2hb7yzIyYnob13o3Mk2vxzCplR-hc5GFmr38c/edit#gid=0) for a breakdown of work and how it aligns with each objective\n\n### Important Links\n\n- https://gitlab.com/gitlab-org/gitlab/-/issues/368044+\n- https://gitlab.com/gitlab-org/gitlab/-/issues/368607+\n\n### Q & A\n\n<details>\n<summary>If we were to move mutli-level epics to premium and add the ability to use epics in projects, what do users get from tasks that is not already available?</summary>\n\nIn terms of customer value, [this video](https://www.youtube.com/watch?v=g5n0dEwcXio&feature=youtu.be) explains \"why\" fairly succinctly.\n\nIn terms of \"why\" from a technical and product perspective, the main point is that we do not want to maintain two different objects -- issue and epic -- in the long run. To advance the maturity of epics, they need:\n\n* Assignees\n* weight\n* first-class types\n* Design manager\n* The ability to be moved to other groups\n* Description templates\n* integrated with webhooks\n* integrated with events so activity shows on a user's profile.\n* ...the list goes on\n\nOn top of that, based on our longer-term vision:\n\n* It will be even more work to integrate epics into places like values stream analytics.\n* The two frontends for issues and epics are different code, so whenever we want to change one aspect of issues or epics that share functionality (say updating the labels widget to pajamas), we have to do it twice. It will require duplicate work for any new things we introduce like https://gitlab.com/groups/gitlab-org/-/epics/5099+\n* The date inheritance model on epics is fairly broken.\n* Issues need to be included in roadmaps.\n\nSo...we can do one of the following:\n\n1. Spend the time doing all the work to bring epics up to \"parity\" with issues, and then double the effort for every change moving forward. This is compounded with each new first-class object we introduce (ex: all the same things noted above for epics apply to requirements). This would also entail making both Epics available in Projects and Issues available in Groups (twice the work).\n2. Consolidate the objects down to a single object, fix some of the underlying wonky stuff (date inheritance model) as we go, and only migrate one object to Group or Project.\n\nPath 2 requires less effort and ultimately increases the rate at which we can improve the maturity of the JTBD for which epics are currently being used.\n</details>\n\n<details>\n<summary>Why did you decide to start with Tasks?</summary>\n\nIn terms of customer value, [this video](https://www.youtube.com/watch?v=g5n0dEwcXio&feature=youtu.be) explains \"why\" fairly succinctly. Additionally, <span dir=\"\">\\~</span>6% of Plan users currently have access to the notion of a grandparent (multi-level epic). <span dir=\"\">\\~</span>15% have access to the notion of a parent (single-level epic). 79% have no notion of parenting in their workflows. By introducing Tasks, we are providing <span dir=\"\">\\~</span>21% of Plan users with the notion of grandparents, and 79% of Plan users with the notion of parent/child relationships.\n\nFrom a technical and product perspective, we needed to find a real problem to solve that would allow us to: 1) Build the work items API, 2) Design and build a new frontend, 3) Incrementally work towards migrating epics to work items -- which requires that we add \"parent/child\" relationships to issues. 4) low risk to disrupting existing issue workflows 5) Reduce the risk for reaching eventual consistency that allowed us to iterate and get feedback as we work towards migrating various objects to be a \"work item\"\n</details>", "author_id": 4669960, "group_id": 9970, "updated_by_id": 2890431, "lock_version": 166, "start_date": "2018-08-08", "end_date": "2024-03-15", "created_at": "2021-05-18 21:59:07 UTC", "updated_at": "2023-10-24 07:01:19 UTC", "state_id": "opened", "confidential": false, "color": "#1068bf", "total_opened_issue_weight": 153, "total_closed_issue_weight": 660, "total_opened_issue_count": 312, "total_closed_issue_count": 517, "closed_by_id": null, "closed_at": null, "start_date_sourcing_milestone_id": null, "due_date_sourcing_milestone_id": null, "start_date_fixed": "2021-05-17", "due_date_fixed": "2021-11-18", "start_date_is_fixed": false, "due_date_is_fixed": false, "parent_id": null, "relative_position": null, "start_date_sourcing_epic_id": 864588, "due_date_sourcing_epic_id": 752853, "last_edited_by_id": 5709669, "last_edited_at": "2023-01-20 04:22:25 UTC", "labels": [27355480, 3103451]}
+{"id": 909555, "iid": 11104, "title": "Work Item Detail Improvements [Phase I] - Header area and breadcrumbs changes", "description": "", "author_id": 4303289, "group_id": 9970, "updated_by_id": 4303289, "lock_version": 1, "start_date": "2023-07-18", "end_date": "2023-08-17", "created_at": "2023-07-27 15:13:18 UTC", "updated_at": "2023-08-09 20:34:37 UTC", "state_id": "opened", "confidential": false, "color": "#1068bf", "total_opened_issue_weight": 0, "total_closed_issue_weight": 3, "total_opened_issue_count": 0, "total_closed_issue_count": 3, "closed_by_id": null, "closed_at": null, "start_date_sourcing_milestone_id": 2969682, "due_date_sourcing_milestone_id": 2969682, "start_date_fixed": null, "due_date_fixed": null, "start_date_is_fixed": null, "due_date_is_fixed": null, "parent_id": 854759, "relative_position": -9169, "start_date_sourcing_epic_id": null, "due_date_sourcing_epic_id": null, "last_edited_by_id": 4303289, "last_edited_at": "2023-07-27 15:38:43 UTC", "labels": []}
+{"id": 762022, "iid": 9997, "title": "AI Integration Strategy", "description": "Over the last months/year, we have seen a global shift with the constant improvements made in the field of large AI models, enabling them to provide capabilities for multiple use cases. There is a vast amount of competition both in the AI as a Service (OpenAI, cloud services, etc.) and the open source model side, which should give us multiple options to choose from for integration.\n\nThe proposal is to focus on \"prompt engineering\" rather than \"model engineering\". By having a strong and competitive global base system (external or self-run) in place that **all development teams/groups** can use and incorporate to extend capabilities, we can stay timely and strategically competitive in this field. In a classic GitLab iteration fashion, the focus should be on searching for small iterations to begin with and extending further in larger use cases, rather than starting with the most complex. We can externalize feasibility and usefulness checkd  with small experiments before incorporating them into the actual product. Again, the value proposition of one DevSecOps platform should come as an advantage, as we would be able to provide any AI system with a 360-degree view of data.\n\n## Increase productivity and time to results for our users\n\nAI is the new super shiny topic and there is a trend to inject AI to everything. We should focus on creating especially value by increasing productivity and time to results for our users so they can focus on the most important topics. Any AI enhance proposal should be checked on this is really useful and could be used something on a daily basis saving a lot of time vs. \"looks shiny and great for marketing\". \n\nWith tools nowadays it should be easy to validate ideas in days before fully integrating into the product.\n\n## Current Projects\n\n* [Code Suggestions](https://about.gitlab.com/direction/modelops/ai_assisted/code_suggestions/)\n* [ModelOps Topics](https://about.gitlab.com/direction/modelops/ai_assisted/)\n* Added Support for GitLab to [codereview.gpt](https://github.com/sturdy-dev/codereview.gpt)\n\n## Done Experiments\n\n* [Tanuki Stan](https://gitlab.com/gitlab-org/ml-ops/tanuki-stan)\n* [Natural language Queries for Analytics](gitlab-org/gitlab#393881)\n* [AI Assist Experiment](https://www.youtube.com/watch?v=URi0teihIGE) + [Repo](https://gitlab.com/a_akgun/gitlab-rapid-machine-learning-prototypes/-/tree/main)\n* [Ask the Tanuki about documentation and handbook content](https://gitlab.com/gitlab-org/gitlab/-/issues/402255)\n* [Spamcheck Product Spam Detection](https://gitlab.com/gitlab-org/gl-security/security-engineering/security-automation/spam/spamcheck)\n\n## Information Gathering\n\n### Dev + Analytics\n\n* [Implementation Map](https://gitlab.com/gitlab-org/gitlab/-/issues/402649)\n* [Possible Use Cases](gitlab-org/gitlab#393884)\n* [Examples/Infos/Competition Use Cases](gitlab-org/gitlab#393883)\n\n## Effort classification\n\nTo help with prioritzation and decision making for \"low hanging\" fruits, trying to classify potential integrations into 3 different buckets. By this we are able to classify early ideas, for a next experimentation level and then a potential go-to-production.\n\n### 1. Ad-hoc Task\n\nA task that is given to an API and an immediate result is returned. E.g. Summarize text content, explain specific part of code, etc. Especially if existing API's can be used and no further model only a good prompt is needed which can be formed in experimentation phase.\n\nExamples:\n* Summarize content, write content, explain, translate, improve code, etc. by OpenAI API (https://platform.openai.com/examples)\n* Use [Prophet](https://facebook.github.io/prophet/) for forecasting data in charts\n\n### 2. Pre-Analysing + Knowledge Base \n\nIf pre-transformation needs to be done and results need to be stored implementation becomes more complex. E.g. Indexing of all issues, code files to be able to answer questions. \n\nExamples\n* Vector Index of Content (Issues, MR, Code?) for different tasks like answering questions, classification, clustering, etc.\n\n### 3. Custom ML\n\nVery specific tasks and workflows that even need implementation of own models and continous improvement.\n\n----\n\nBoth 1 and 2 types are classic work items in product development and should be handled like that. Experimentation can be done in work spikes. We need to define a sign off procedure regarding production go live.", "author_id": 1149402, "group_id": 9970, "updated_by_id": 3796140, "lock_version": 13, "start_date": "2023-03-18", "end_date": "2023-11-10", "created_at": "2023-03-03 09:40:31 UTC", "updated_at": "2023-09-09 18:15:12 UTC", "state_id": "opened", "confidential": false, "color": "#217645", "total_opened_issue_weight": 50, "total_closed_issue_weight": 76, "total_opened_issue_count": 270, "total_closed_issue_count": 306, "closed_by_id": null, "closed_at": null, "start_date_sourcing_milestone_id": null, "due_date_sourcing_milestone_id": null, "start_date_fixed": null, "due_date_fixed": null, "start_date_is_fixed": false, "due_date_is_fixed": false, "parent_id": null, "relative_position": null, "start_date_sourcing_epic_id": 785858, "due_date_sourcing_epic_id": 818139, "last_edited_by_id": 480804, "last_edited_at": "2023-05-11 07:45:45 UTC", "labels": [30251403, 30402137, 13934960, 29780827]}
+{"id": 302007, "iid": 6286, "title": "\ud83d\udc67 Work Items -  Relationships", "description": "# Summary\n\nIn this epic, we will build the relationship architecture for work items. Relationships in this sense apply to parent, child, related, blocked, blocking, other(?) between work items.\n\n## Relationship rules for work item records\n\n* Cross hierarchy linking should be available for all relationships within work items\n* Work items can only have one kind of relationship to another (parent/child, blocking/blocked by/related).\n* You can easily switch the relationship type without removing and then re-adding the work items to create the relationship.\n* Work items can only have one immediate parent record\n* Enforce a strict hierarchy in order to adhere to frameworks like SAFe\n  * Provide a way for customers to model the rules for parent/child relationships.\n    * Example: Epic -\\> Feature -\\> Story -\\> Bug. In this example, you could not have an Epic be the parent of a Bug.\n  * Provide out of the box hierarchies that adhere to industry-standard frameworks\n  * Allow customers to set their own hierarchies\n* Beyond the restrictions in the restrictions table, work items can have relationships to any other work item in a hierarchy, so long as there is only one type of relationship between two distinct records.\n* Epic nesting should allow for 9 levels to match OKR nesting (this is an increase from 7 levels which are available in issuables today)\n\n## Relationship management exploration\n\nIn https://gitlab.com/groups/gitlab-org/-/epics/9083 and https://gitlab.com/gitlab-org/ux-research/-/issues/2168, we are conducting research on the ways that users are thinking about and interacting with relationships in order to create an efficient and pleasant user experience for relationship management in work items.\n\n## Relationship management feature expectations\n\n* Display metadata related to the record type (label, milestone, weight, assignee, progress, etc)\n* Display nested records with collapse/expand controls\n* Offer expand all / collapse all controls (pending performance impact see [discussion](https://gitlab.com/gitlab-org/gitlab/-/issues/386416#note_1325273564 \"OKR MVC - User feedback\"))\n* Allow users to drag and drop to reorder or reparent the records and allow that manual order to remain sticky\n* Allow users to reparent records without opening another page/tab/modal\n* Create sort controls for the entire widget (sort by date created, assignee, milestone, etc)\n* Allow users to edit metadata displayed on the record without opening another page/tab/modal\n* Ensure users can quickly gauge health status of records (on track, at risk, needs attention)\n* Ensure users can quickly understand dependencies of records\n* Ensure users can quickly understand status of records (open, closed, blocked, complete, etc)\n\n## Allowable relationships between issuables and work items\n\nIn https://gitlab.com/groups/gitlab-org/-/epics/10851 we are creating the ability to have a work item `parent` related to an issuables `child`. Since migration to the work items framework will not occur for all issuable types simultaneously, we will need to support these hybrid relationships until all issuables have been migrated to work items. Below lists the approved mixed relationships between work items and issuables during this transition period:\n\n- :white_check_mark: `work item:Epic` can be a parent of an `issuable:Issue`\n- :white_check_mark: `issuable:Issue` can be a parent of a `work item:task`\n\n\n\n\n## Allowable work item relationships\n\n#### Parent:Child\n\n|  | Epic as child | Issue as child | Task as child | Objective as child | Key Result as child | \n|--|---------------|----------------|---------------|--------------------|---------------------|\n| Epic as parent | :white_check_mark: | :white_check_mark: | :x: | :x: | :x: | \n| Issue as parent | :x: | :x: | :white_check_mark: | :x: | :x: | \n| Task as parent | :x: | :x: | :x: | :x: | :x: | \n| Objective as parent | :x: | :x: | :x: | :white_check_mark: | :white_check_mark: | \n| Key Results as parent | :x: | :x: | :x: | :x: | :x: |\n\n\n#### Linked (blocked by)\n\n|  | Epic | Issue | Task | Objective | Key Result |\n|--|------|-------|------|-----------|------------|\n| Epic blocked by | :white_check_mark: | :white_check_mark: | :white_check_mark: | :x: | :x: |\n| Issue blocked by | :white_check_mark: | :white_check_mark: | :white_check_mark: | :x: | :x: | \n| Task blocked by | :white_check_mark: | :white_check_mark: | :white_check_mark: | :x: | :x: | \n| Objective blocked by | :white_check_mark: | :white_check_mark: | :white_check_mark: | :white_check_mark: | :white_check_mark: |\n| Key Result blocked by | :white_check_mark: | :white_check_mark: | :white_check_mark: | :white_check_mark: | :white_check_mark: | \n\n\n#### Linked (blocking)\n\n|  | Epic | Issue | Task | Objective | Key Result | \n|--|------|-------|------|-----------|------------|\n| Epic blocks | :white_check_mark: | :white_check_mark: | :white_check_mark: | :white_check_mark: | :white_check_mark: |\n| Issue blocks | :white_check_mark: | :white_check_mark: | :white_check_mark: | :white_check_mark: | :white_check_mark: |\n| Task blocks | :white_check_mark: | :white_check_mark: | :white_check_mark: | :white_check_mark: | :white_check_mark: | \n| Objective blocks | :x: | :x: | :x: | :white_check_mark: | :white_check_mark: |\n| Key Result blocks | :x: | :x: | :x: | :white_check_mark: | :white_check_mark: |\n\n\n#### Linked (related)\n\n|  | Epic | Issue | Task | Objective | Key Result | \n|--|------|-------|------|-----------|------------|\n| Epic related to | :white_check_mark: | :white_check_mark: | :white_check_mark: | :white_check_mark: | :white_check_mark: | \n| Issue related to | :white_check_mark: | :white_check_mark: | :white_check_mark: | :white_check_mark: | :white_check_mark: |\n| Task related to | :white_check_mark: | :white_check_mark: | :white_check_mark: | :white_check_mark: | :white_check_mark: | \n| Objective related to | :white_check_mark: | :white_check_mark: | :white_check_mark: | :white_check_mark: | :white_check_mark: | \n| Key Result related to | :white_check_mark: | :white_check_mark: | :white_check_mark: | :white_check_mark: | :white_check_mark: |", "author_id": 4669960, "group_id": 9970, "updated_by_id": 2890431, "lock_version": 59, "start_date": "2022-11-01", "end_date": "2023-12-15", "created_at": "2021-07-06 16:33:20 UTC", "updated_at": "2023-10-05 15:01:47 UTC", "state_id": "opened", "confidential": false, "color": "#1068bf", "total_opened_issue_weight": 16, "total_closed_issue_weight": 73, "total_opened_issue_count": 12, "total_closed_issue_count": 52, "closed_by_id": null, "closed_at": null, "start_date_sourcing_milestone_id": null, "due_date_sourcing_milestone_id": null, "start_date_fixed": "2023-07-18", "due_date_fixed": "2023-10-17", "start_date_is_fixed": false, "due_date_is_fixed": false, "parent_id": 657742, "relative_position": -7182, "start_date_sourcing_epic_id": 624151, "due_date_sourcing_epic_id": 939712, "last_edited_by_id": 2890431, "last_edited_at": "2023-10-05 15:01:47 UTC", "labels": [27355480, 29821275, 3103451, 10690700, 14918378, 25541419]}
+{"id": 854759, "iid": 10814, "title": "[UX] Detail pages for Plan related Work Items", "description": "## Iteration 1: Building a foundation for work item detail views\n\nThe goal of Iteration 1 is to create a consistent and flexible foundation for work items that will accommodate a variety of different planning objects.\n\n### Iteration 1A: Header area and breadcrumbs changes\n\nThese changes to the header area are meant to group similar work item information together and make work items more consistent with other planning objects.\n\nBecause these changes are small and increase consistency with other areas of the product, they do not need to be behind a feature flag.\n\n_Iteration 1A is a blocker for the release of Iteration 1B._\n\n_<sub>Table updated 2023-09-05</sub>_\n\n<table>\n<tr>\n<th>Reference</th>\n<th>Description</th>\n<th>UX status</th>\n<th>Issue links</th>\n</tr>\n<tr>\n<td>\n\n:one:\n</td>\n<td>Header area and breadcrumbs changes</td>\n<td>\n\nSome aspects are ~\"workflow::ready for development\" , some aspects are still in ~\"workflow::design\"\n\nConfidence level is high, ~\"workflow::solution validation\" is not needed.\n</td>\n<td>\n\n* https://gitlab.com/gitlab-org/gitlab/-/issues/416800+s\n* https://gitlab.com/gitlab-org/gitlab/-/issues/416799+s\n* https://gitlab.com/gitlab-org/gitlab/-/issues/415079+s\n</td>\n</tr>\n</table>\n\n### Iteration 1B: Two-column layout, sidebar attributes, and edit experience\n\nWhen updating the work item detail view, there are a number of changes that need to happen all at once to provide value and a consistent, usable experience for our users. These changes should be made behind a feature flag and released to users together.\n\n_Iteration 1A is a blocker for the release of Iteration 1B._\n\n_<sub>Table updated 2023-09-05</sub>_\n\n<table>\n<tr>\n<th>Reference</th>\n<th>Description</th>\n<th>UX status</th>\n<th>Issue links</th>\n</tr>\n<tr>\n<td>\n\n:one:\n</td>\n<td>Two-column layout (including two-column layout for small screens)</td>\n<td>\n\nSome aspects are ~\"workflow::ready for development\" , some aspects are still in ~\"workflow::design\" .\n\nConfidence level is high, ~\"workflow::solution validation\" is not needed.\n</td>\n<td>\n\n* https://gitlab.com/gitlab-org/gitlab/-/issues/415077+s\n* https://gitlab.com/gitlab-org/gitlab/-/issues/417915+s\n</td>\n</tr>\n<tr>\n<td>\n\n:two:\n</td>\n<td>Sidebar attributes</td>\n<td>\n\nCurrently in ~\"workflow::design\"\n\nWhether we need ~\"workflow::solution validation\" depends on which design direction we pursue. TBD.\n</td>\n<td>\n\n* https://gitlab.com/gitlab-org/gitlab/-/issues/416801+s\n</td>\n</tr>\n<tr>\n<td>\n\n:three:\n</td>\n<td>Edit experience (for work item title and description)</td>\n<td>\n\nCurrently in ~\"workflow::design\" .\n\nWill likely need ~\"workflow::solution validation\" .\n</td>\n<td>\n\n\u2022 https://gitlab.com/gitlab-org/gitlab/-/issues/419952+s\n</td>\n</tr>\n<tr>\n<td>\n\n:four:\n</td>\n<td>Sticky header (includes making utility actions sticky)</td>\n<td>\n\nCurrently in ~\"workflow::design\" . Confidence level is high, ~\"workflow::solution validation\" is not needed.\n</td>\n<td>\n\n* https://gitlab.com/gitlab-org/gitlab/-/issues/419953+s\n</td>\n</tr>\n</table>\n\n## Iteration 2: Create flow for work items\n\nImprove the creation of work items (does not impact legacy issues/epics).\n\n_<sub>Table updated 2023-07-24</sub>_\n\n| Reference | Description | UX status | Issue links |\n|-----------|-------------|-----------|-------------|\n| :one: | Create experience | Currently in ~\"workflow::design\" . Will likely need ~\"workflow::solution validation\" . | https://gitlab.com/groups/gitlab-org/-/epics/11012+s |\n\n## Iteration 3: Adding a contextual work item view\n\nOnce we have a foundation for work items in place, we'll continue to build upon that by adding and improving widgets and introducing a contextual work item view for users to be able to view work items without losing their current context.\n\n_<sub>Table updated 2023-08-03</sub>_\n\n<table>\n<tr>\n<th>Reference</th>\n<th>Description</th>\n<th>UX status</th>\n<th>Issue links</th>\n</tr>\n<tr>\n<td>\n\n:one:\n</td>\n<td>Work item contextual view (modal? drawer?)</td>\n<td>\n\nSome of this is being explored with the overall detail page design, but the majority of design requirements will be handled in https://gitlab.com/gitlab-org/gitlab/-/issues/409886.\n\nThere will be a separate ~\"workflow::solution validation\" effort conducted alongside https://gitlab.com/gitlab-org/gitlab/-/issues/409886.\n</td>\n<td>\n\n</td>\n</tr>\n</table>\n\n## Non-dependent improvements that can be released in any order\n\nImprovements in this area are not dependent on Iterations 1-3. They can be made at any time (before or after Iterations 1-3).\n\n_<sub>Table updated 2023-07-24</sub>_\n\n<table>\n<tr>\n<th>Reference</th>\n<th>Description</th>\n<th>UX status</th>\n<th>Issue links</th>\n</tr>\n<tr>\n<td>\n\n:one:\n</td>\n<td>Parent / ancestry information</td>\n<td>\n\nCurrently in ~\"workflow::design\" .\n\n~\"workflow::solution validation\" will be done in https://gitlab.com/gitlab-org/ux-research/-/issues/2486+s\n</td>\n<td>\n\n</td>\n</tr>\n</table>", "author_id": 4089849, "group_id": 9970, "updated_by_id": 4377833, "lock_version": 16, "start_date": "2023-07-18", "end_date": "2023-11-10", "created_at": "2023-06-09 19:34:47 UTC", "updated_at": "2023-10-24 14:14:38 UTC", "state_id": "opened", "confidential": false, "color": "#1068bf", "total_opened_issue_weight": 6, "total_closed_issue_weight": 8, "total_opened_issue_count": 26, "total_closed_issue_count": 9, "closed_by_id": null, "closed_at": null, "start_date_sourcing_milestone_id": null, "due_date_sourcing_milestone_id": null, "start_date_fixed": null, "due_date_fixed": null, "start_date_is_fixed": null, "due_date_is_fixed": null, "parent_id": 677568, "relative_position": -35781, "start_date_sourcing_epic_id": 909555, "due_date_sourcing_epic_id": 909556, "last_edited_by_id": 4377833, "last_edited_at": "2023-09-05 21:07:28 UTC", "labels": []}
+{"id": 835460, "iid": 10694, "title": "Work items permission adjustments", "description": "We have observed differences between permission checks for users with guest access to issues vs work items. This epic will track the issues to solve them.", "author_id": 3860200, "group_id": 9970, "updated_by_id": 3860200, "lock_version": 1, "start_date": "2023-05-18", "end_date": "2023-08-17", "created_at": "2023-05-24 10:02:12 UTC", "updated_at": "2023-10-24 13:56:16 UTC", "state_id": "opened", "confidential": false, "color": "#1068bf", "total_opened_issue_weight": 0, "total_closed_issue_weight": 8, "total_opened_issue_count": 0, "total_closed_issue_count": 5, "closed_by_id": null, "closed_at": null, "start_date_sourcing_milestone_id": 2969659, "due_date_sourcing_milestone_id": 2969682, "start_date_fixed": null, "due_date_fixed": null, "start_date_is_fixed": false, "due_date_is_fixed": false, "parent_id": null, "relative_position": null, "start_date_sourcing_epic_id": null, "due_date_sourcing_epic_id": null, "last_edited_by_id": null, "last_edited_at": null, "labels": [10690700, 2278648, 25541419]}

data/duo_chat/v1/jsonl/context/resources/c96036bb531f42988870e2f93497b9bc.jsonl

@@ -0,0 +1,51 @@
+{"id": 992791, "title": "Deliverable", "color": "#428BCA", "template": false, "lock_on_merge": false, "type": "GroupLabel", "created_at": "2016-11-18 17:02:50 UTC", "updated_at": "2019-04-17 18:49:16 UTC", "description": "Issues scheduled for the current milestone.", "project_id": null, "group_id": 9970}
+{"id": 10413872, "title": "SLO::Missed", "color": "#CC0000", "template": false, "lock_on_merge": false, "type": "GroupLabel", "created_at": "2019-04-28 18:18:21 UTC", "updated_at": "2023-02-16 18:38:39 UTC", "description": "Label to signify that a bug issue has missed its targeted SLO (Service Level Objective). See https://docs.gitlab.com/ee/development/contributing/issue_workflow.html#priority-labels. Previously titled as missed-SLO", "project_id": null, "group_id": 9970}
+{"id": 2492649, "title": "backend", "color": "#D10069", "template": false, "lock_on_merge": false, "type": "GroupLabel", "created_at": "2017-08-15 14:49:42 UTC", "updated_at": "2018-06-11 10:34:33 UTC", "description": "Issues that require backend work", "project_id": null, "group_id": 9970}
+{"id": 26460213, "title": "bug::functional", "color": "#CC0000", "template": false, "lock_on_merge": false, "type": "GroupLabel", "created_at": "2022-08-16 19:56:26 UTC", "updated_at": "2022-08-16 19:56:26 UTC", "description": "Functional defects resulting from feature changes", "project_id": null, "group_id": 9970}
+{"id": 3103451, "title": "devops::plan", "color": "#E44D2A", "template": false, "lock_on_merge": false, "type": "GroupLabel", "created_at": "2017-12-01 19:00:23 UTC", "updated_at": "2022-05-11 06:40:37 UTC", "description": "Issues for the Plan stage of the DevOps lifecycle (e.g. Project Management, Agile Portfolio Management, Requirements Management)", "project_id": null, "group_id": 9970}
+{"id": 3412464, "title": "frontend", "color": "#3cb371", "template": false, "lock_on_merge": false, "type": "GroupLabel", "created_at": "2018-01-30 21:42:37 UTC", "updated_at": "2022-05-13 09:23:38 UTC", "description": "Issues for the Frontend team. Covers everything related to the way GitLab behaves (and, to an extent, looks) inside your browser.", "project_id": null, "group_id": 9970}
+{"id": 10690700, "title": "group::product planning", "color": "#A8D695", "template": false, "lock_on_merge": false, "type": "GroupLabel", "created_at": "2019-05-22 19:55:52 UTC", "updated_at": "2020-10-16 19:33:41 UTC", "description": "Issues belonging to the Product Planning group of the Plan stage of the DevOps lifecycle. See https://about.gitlab.com/handbook/product/product-categories/#product-planning-group", "project_id": null, "group_id": 9970}
+{"id": 3857523, "title": "priority::2", "color": "#ff8800", "template": false, "lock_on_merge": false, "type": "GroupLabel", "created_at": "2018-04-13 08:01:55 UTC", "updated_at": "2020-09-14 22:10:38 UTC", "description": "We will address this soon and will provide capacity from our team for it in the next few releases. See https://about.gitlab.com/handbook/engineering/quality/issue-triage/#priority", "project_id": null, "group_id": 9970}
+{"id": 14918378, "title": "section::dev", "color": "#F0AD4E", "template": false, "lock_on_merge": false, "type": "GroupLabel", "created_at": "2020-05-11 22:11:57 UTC", "updated_at": "2020-05-11 22:11:57 UTC", "description": "Issues related to the Dev section", "project_id": null, "group_id": 9970}
+{"id": 3713902, "title": "severity::2", "color": "#ff8800", "template": false, "lock_on_merge": false, "type": "GroupLabel", "created_at": "2018-03-23 14:46:34 UTC", "updated_at": "2020-09-14 22:13:45 UTC", "description": "Critical - applies to bugs and bug categories of availability, performance, security and ux. See https://about.gitlab.com/handbook/engineering/quality/issue-triage/#severity", "project_id": null, "group_id": 9970}
+{"id": 2278648, "title": "type::bug", "color": "#CC0000", "template": false, "lock_on_merge": false, "type": "GroupLabel", "created_at": "2017-07-07 20:20:34 UTC", "updated_at": "2021-10-27 09:36:49 UTC", "description": "Issues that report undesirable or incorrect behavior. See https://about.gitlab.com/handbook/engineering/metrics/#work-type-classification", "project_id": null, "group_id": 9970}
+{"id": 25541419, "title": "work items", "color": "#428BCA", "template": false, "lock_on_merge": false, "type": "GroupLabel", "created_at": "2022-06-13 14:41:30 UTC", "updated_at": "2022-06-13 14:41:30 UTC", "description": "Related to the Work Items feature", "project_id": null, "group_id": 9970}
+{"id": 28669354, "title": "workflow::complete", "color": "#428BCA", "template": false, "lock_on_merge": false, "type": "GroupLabel", "created_at": "2023-01-12 00:18:59 UTC", "updated_at": "2023-01-12 17:27:43 UTC", "description": "Applied after all MRs have merged and the issue has been verified if necessary", "project_id": null, "group_id": 9970}
+{"id": 11039421, "title": "Category:Code Analytics", "color": "#428BCA", "template": false, "lock_on_merge": false, "type": "GroupLabel", "created_at": "2019-06-18 19:25:29 UTC", "updated_at": "2019-08-27 17:07:41 UTC", "description": "", "project_id": null, "group_id": 9970}
+{"id": 11469047, "title": "Category:Source Code Management", "color": "#428BCA", "template": false, "lock_on_merge": false, "type": "GroupLabel", "created_at": "2019-07-25 19:15:39 UTC", "updated_at": "2019-08-27 17:08:57 UTC", "description": "Category vision in Create stage: https://gitlab.com/groups/gitlab-org/-/epics/687", "project_id": null, "group_id": 9970}
+{"id": 7161201, "title": "Manage [DEPRECATED]", "color": "#44AD8E", "template": false, "lock_on_merge": false, "type": "GroupLabel", "created_at": "2018-07-19 05:48:06 UTC", "updated_at": "2019-08-19 11:52:05 UTC", "description": "Please use the devops::manage label instead of this deprecated label. It is kept for historical issues.", "project_id": null, "group_id": 9970}
+{"id": 1890178, "title": "[deprecated] Accepting merge requests", "color": "#69d100", "template": false, "lock_on_merge": false, "type": "GroupLabel", "created_at": "2017-04-21 11:34:01 UTC", "updated_at": "2023-06-28 08:14:53 UTC", "description": "[deprecated] Please use \"Seeking community contributions\" instead. https://gitlab.com/gitlab-org/developer-relations/contributor-success/team-task/-/issues/77", "project_id": null, "group_id": 9970}
+{"id": 2677574, "title": "auto updated", "color": "#FFECDB", "template": false, "lock_on_merge": false, "type": "GroupLabel", "created_at": "2017-09-19 02:09:18 UTC", "updated_at": "2019-05-02 11:05:59 UTC", "description": "Issues that have been updated in accordance with our issue triage policies (https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/development/contributing/issue_workflow.md)", "project_id": null, "group_id": 9970}
+{"id": 1672341, "title": "customer", "color": "#ad4363", "template": false, "lock_on_merge": false, "type": "GroupLabel", "created_at": "2017-03-10 22:24:59 UTC", "updated_at": "2017-03-10 22:24:59 UTC", "description": "Issues that were reported by Enterprise Edition subscribers. This label should be accompanied by either the 'bug' or 'feature proposal' label", "project_id": null, "group_id": 9970}
+{"id": 3103452, "title": "devops::create", "color": "#E44D2A", "template": false, "lock_on_merge": false, "type": "GroupLabel", "created_at": "2017-12-01 19:01:03 UTC", "updated_at": "2022-07-04 07:09:55 UTC", "description": "Issues for the Create stage of the DevOps lifecycle (e.g. Source Code Management, Design Management, Web IDE, Code Review, Gitter)", "project_id": null, "group_id": 9970}
+{"id": 4107658, "title": "graphs", "color": "#428bca", "template": false, "lock_on_merge": false, "type": "GroupLabel", "created_at": "2018-05-22 15:01:06 UTC", "updated_at": "2018-05-22 15:01:06 UTC", "description": "Issues related to the project Graphs pages", "project_id": null, "group_id": 9970}
+{"id": 10309854, "title": "group::source code", "color": "#A8D695", "template": false, "lock_on_merge": false, "type": "GroupLabel", "created_at": "2019-04-17 13:57:02 UTC", "updated_at": "2019-05-23 09:26:35 UTC", "description": "Issues belonging to the Source Code group of the Create stage of the DevOps lifecycle. See https://about.gitlab.com/handbook/product/categories/#source-code-group", "project_id": null, "group_id": 9970}
+{"id": 15237307, "title": "icebox", "color": "#d6ecef", "template": false, "lock_on_merge": false, "type": "GroupLabel", "created_at": "2020-06-09 02:25:38 UTC", "updated_at": "2020-06-09 02:35:52 UTC", "description": "Issues on which no work is anticipated in the next several milestones but which may be considered for work shortly thereafter thus not closed.", "project_id": null, "group_id": 9970}
+{"id": 2936416, "title": "popular proposal", "color": "#FFECDB", "template": false, "lock_on_merge": false, "type": "GroupLabel", "created_at": "2017-10-31 10:32:07 UTC", "updated_at": "2017-10-31 10:32:07 UTC", "description": "Feature proposals deemed popular by our issue triage policies (https://gitlab.com/gitlab-org/triage) will have this label applied", "project_id": null, "group_id": 9970}
+{"id": 2714266, "title": "potential proposal", "color": "#FFECDB", "template": false, "lock_on_merge": false, "type": "GroupLabel", "created_at": "2017-09-25 01:24:57 UTC", "updated_at": "2017-09-25 01:24:57 UTC", "description": "Label added by triage tools to mark interesting feature proposals for consideration", "project_id": null, "group_id": 9970}
+{"id": 10230929, "title": "type::feature", "color": "#009966", "template": false, "lock_on_merge": false, "type": "GroupLabel", "created_at": "2019-04-09 12:29:58 UTC", "updated_at": "2022-03-28 23:33:53 UTC", "description": "Any issue/MR that contains work to support the implementation of a feature and/or results in an improvement in the user experience. Read more at https://about.gitlab.com/handbook/engineering/metrics/#work-type-classification", "project_id": null, "group_id": 9970}
+{"id": 130812, "title": "frontend", "color": "#3cb371", "template": false, "lock_on_merge": false, "type": "ProjectLabel", "created_at": "2015-11-27 21:29:34 UTC", "updated_at": "2023-04-27 10:56:44 UTC", "description": "", "project_id": 7764, "group_id": null}
+{"id": 8595532, "title": "trainee maintainer", "color": "#8E44AD", "template": false, "lock_on_merge": false, "type": "ProjectLabel", "created_at": "2018-11-08 12:29:56 UTC", "updated_at": "2018-11-08 12:29:56 UTC", "description": "", "project_id": 7764, "group_id": null}
+{"id": 2771176, "title": "direction", "color": "#ad8d43", "template": false, "lock_on_merge": false, "type": "GroupLabel", "created_at": "2017-10-04 13:38:26 UTC", "updated_at": "2017-10-04 13:38:26 UTC", "description": "Issues for important features that are on our roadmap: https://about.gitlab.com/direction/", "project_id": null, "group_id": 9970}
+{"id": 26375975, "title": "type::ignore", "color": "#808080", "template": false, "lock_on_merge": false, "type": "GroupLabel", "created_at": "2022-08-09 18:12:49 UTC", "updated_at": "2022-08-09 19:21:21 UTC", "description": "When using this type, the issue will be excluded from cross functional planning metrics. This is used for meta, planning, issues.", "project_id": null, "group_id": 9970}
+{"id": 11111311, "title": "workflow::problem validation", "color": "#428BCA", "template": false, "lock_on_merge": false, "type": "GroupLabel", "created_at": "2019-06-26 11:39:07 UTC", "updated_at": "2020-08-21 15:43:10 UTC", "description": "Workflow label for validating if the problem is customer relevant. https://about.gitlab.com/handbook/product-development-flow/#workflow-summary", "project_id": null, "group_id": 9970}
+{"id": 22241940, "title": "Category:Team Planning", "color": "#6699cc", "template": false, "lock_on_merge": false, "type": "GroupLabel", "created_at": "2021-10-22 13:33:21 UTC", "updated_at": "2021-10-22 13:33:21 UTC", "description": "Plan, organize, and track team progress using Scrum, Kanban, SAFe, and other Agile methodologies.", "project_id": null, "group_id": 9970}
+{"id": 2024184, "title": "UX", "color": "#D10069", "template": false, "lock_on_merge": false, "type": "GroupLabel", "created_at": "2017-05-17 17:55:03 UTC", "updated_at": "2022-05-31 23:10:02 UTC", "description": "Issues or MRs that introduce user-facing changes or impact the user experience. Applying this label to issues will signal a need for a designer.", "project_id": null, "group_id": 9970}
+{"id": 15714199, "title": "design-weight::1", "color": "#ffdbed", "template": false, "lock_on_merge": false, "type": "GroupLabel", "created_at": "2020-07-20 17:33:24 UTC", "updated_at": "2020-07-20 17:33:56 UTC", "description": "(Trivial) Mostly small UI changes leading to small incremental UX improvements. No users\u2019 workflow involved in these changes. Requirements are clear and there are no unanswered questions.", "project_id": null, "group_id": 9970}
+{"id": 2975007, "title": "feature::enhancement", "color": "#F0AD4E", "template": false, "lock_on_merge": false, "type": "GroupLabel", "created_at": "2017-11-07 21:18:44 UTC", "updated_at": "2021-07-14 18:22:59 UTC", "description": "User-facing improvements that refine the initial MVC to make it more useful and usable. Read more at https://about.gitlab.com/handbook/engineering/metrics/#data-classification", "project_id": null, "group_id": 9970}
+{"id": 10690691, "title": "group::project management", "color": "#A8D695", "template": false, "lock_on_merge": false, "type": "GroupLabel", "created_at": "2019-05-22 19:55:45 UTC", "updated_at": "2020-08-28 15:40:02 UTC", "description": "Issues belonging to the Project Management group of the Plan stage of the DevOps lifecycle. See https://about.gitlab.com/handbook/product/categories/#team-planning-group | PM: @gweaver", "project_id": null, "group_id": 9970}
+{"id": 11111313, "title": "workflow::planning breakdown", "color": "#428BCA", "template": false, "lock_on_merge": false, "type": "GroupLabel", "created_at": "2019-06-26 11:39:40 UTC", "updated_at": "2020-04-27 22:24:44 UTC", "description": "Issues that need estimation, and possibly breaking down into further chunks to enable effective iteration. https://about.gitlab.com/handbook/product-development-flow/", "project_id": null, "group_id": 9970}
+{"id": 30251403, "title": "AI-Priority", "color": "#9400d3", "template": false, "lock_on_merge": false, "type": "GroupLabel", "created_at": "2023-05-11 19:53:00 UTC", "updated_at": "2023-05-11 19:53:00 UTC", "description": "", "project_id": null, "group_id": 9970}
+{"id": 31167182, "title": "Category:Duo Chat", "color": "#6699cc", "template": false, "lock_on_merge": false, "type": "GroupLabel", "created_at": "2023-07-31 04:14:40 UTC", "updated_at": "2023-08-14 17:02:16 UTC", "description": "AI Framework category, formerly named Category:GitLab Duo Chat", "project_id": null, "group_id": 9970}
+{"id": 30402137, "title": "Copilot-X-Compete", "color": "#9400d3", "template": false, "lock_on_merge": false, "type": "GroupLabel", "created_at": "2023-05-24 18:43:40 UTC", "updated_at": "2023-05-24 18:43:40 UTC", "description": null, "project_id": null, "group_id": 9970}
+{"id": 3207279, "title": "GitLab Ultimate", "color": "#8E44AD", "template": false, "lock_on_merge": false, "type": "GroupLabel", "created_at": "2017-12-22 09:43:27 UTC", "updated_at": "2018-01-30 19:53:24 UTC", "description": "Features or changes limited or intended as part of GitLab Ultimate.", "project_id": null, "group_id": 9970}
+{"id": 31287867, "title": "devops::ai-powered", "color": "#e44d2a", "template": false, "lock_on_merge": false, "type": "GroupLabel", "created_at": "2023-08-10 17:56:54 UTC", "updated_at": "2023-08-16 05:24:57 UTC", "description": "AI-powered stage part of the Data Science section", "project_id": null, "group_id": 9970}
+{"id": 31287876, "title": "group::duo chat", "color": "#a8d695", "template": false, "lock_on_merge": false, "type": "GroupLabel", "created_at": "2023-08-10 18:01:08 UTC", "updated_at": "2023-08-16 05:45:05 UTC", "description": "Duo Chat group, part of the AI-powered stage within the Data Science section", "project_id": null, "group_id": 9970}
+{"id": 23545476, "title": "section::data-science", "color": "#F0AD4E", "template": false, "lock_on_merge": false, "type": "GroupLabel", "created_at": "2022-01-27 10:11:43 UTC", "updated_at": "2022-09-17 00:09:49 UTC", "description": "Issues related to the Data Science section including ModelOps and Anti-Abuse Stages", "project_id": null, "group_id": 9970}
+{"id": 29655839, "title": "CPO Interest", "color": "#36454f", "template": false, "lock_on_merge": false, "type": "GroupLabel", "created_at": "2023-03-21 19:51:00 UTC", "updated_at": "2023-03-21 19:51:00 UTC", "description": "", "project_id": null, "group_id": 9970}
+{"id": 27355480, "title": "FY24", "color": "#c21e56", "template": false, "lock_on_merge": false, "type": "GroupLabel", "created_at": "2022-10-14 15:07:27 UTC", "updated_at": "2022-10-14 15:07:52 UTC", "description": "", "project_id": null, "group_id": 9970}
+{"id": 28630294, "title": "FY24::Q3", "color": "#c21e56", "template": false, "lock_on_merge": false, "type": "GroupLabel", "created_at": "2023-01-09 19:50:43 UTC", "updated_at": "2023-01-09 19:50:43 UTC", "description": "Efforts Targeted For Release Between Aug-Oct 2023", "project_id": null, "group_id": 9970}
+{"id": 29821275, "title": "Now", "color": "#8fbc8f", "template": false, "lock_on_merge": false, "type": "GroupLabel", "created_at": "2023-04-04 14:14:17 UTC", "updated_at": "2023-04-04 14:14:17 UTC", "description": "Features that are part of short-term planning.", "project_id": null, "group_id": 9970}
+{"id": 1672342, "title": "customer+", "color": "#ad4363", "template": false, "lock_on_merge": false, "type": "GroupLabel", "created_at": "2017-03-10 22:25:11 UTC", "updated_at": "2023-05-30 01:57:26 UTC", "description": "Features and bugs reported by large enterprise customers. This label is in use by the product org, please post in #product Slack channel if you have questions.", "project_id": null, "group_id": 9970}
+{"id": 29780827, "title": "wg-ai-integration", "color": "#330066", "template": false, "lock_on_merge": false, "type": "GroupLabel", "created_at": "2023-03-31 13:29:22 UTC", "updated_at": "2023-03-31 13:29:22 UTC", "description": null, "project_id": null, "group_id": 9970}
+{"id": 13934960, "title": "Development Department", "color": "#F0AD4E", "template": false, "lock_on_merge": false, "type": "GroupLabel", "created_at": "2020-02-21 07:12:38 UTC", "updated_at": "2020-02-21 07:12:38 UTC", "description": null, "project_id": null, "group_id": 9970}

data/duo_chat/v1/jsonl/context/resources/d076864e3e9d49898e27c466e2ba8e3b.jsonl

@@ -0,0 +1 @@
+{"id": 39982, "title": "Plan:Project Management", "description": "", "duration_in_weeks": 2, "iterations_in_advance": 4, "created_at": "2023-07-11 21:37:58 UTC", "updated_at": "2023-10-20 00:05:03 UTC", "start_date": "2023-06-30", "next_run_date": "2023-11-03", "active": true, "automatic": true, "roll_over": true, "group_id": 9970}

data/duo_chat/v1/jsonl/context/resources/f1b559b73f524625b727e265dc7ec4f2.jsonl

@@ -0,0 +1,6 @@
+{"id": 2453027, "title": "15.5", "description": "", "due_date": "2022-10-17", "created_at": "2022-02-03 22:29:56 UTC", "updated_at": "2022-02-03 22:29:56 UTC", "state": "active", "iid": 77, "start_date": "2022-09-18", "group_id": 9970, "lock_version": 0, "project_id": null}
+{"id": 2969687, "title": "16.4", "description": "", "due_date": "2023-09-17", "created_at": "2023-02-01 16:04:08 UTC", "updated_at": "2023-02-01 16:04:08 UTC", "state": "active", "iid": 91, "start_date": "2023-08-18", "group_id": 9970, "lock_version": 0, "project_id": null}
+{"id": 3094094, "title": "16.6", "description": "", "due_date": "2023-11-10", "created_at": "2023-05-09 04:50:08 UTC", "updated_at": "2023-08-22 21:35:28 UTC", "state": "active", "iid": 93, "start_date": "2023-10-18", "group_id": 9970, "lock_version": 1, "project_id": null}
+{"id": 2910456, "title": "15.11", "description": "", "due_date": "2023-04-17", "created_at": "2022-12-13 20:08:46 UTC", "updated_at": "2022-12-13 20:08:46 UTC", "state": "active", "iid": 86, "start_date": "2023-03-18", "group_id": 9970, "lock_version": 0, "project_id": null}
+{"id": 2969682, "title": "16.3", "description": "", "due_date": "2023-08-17", "created_at": "2023-02-01 16:03:42 UTC", "updated_at": "2023-02-01 16:03:42 UTC", "state": "active", "iid": 90, "start_date": "2023-07-18", "group_id": 9970, "lock_version": 0, "project_id": null}
+{"id": 2969659, "title": "16.1", "description": "", "due_date": "2023-06-17", "created_at": "2023-02-01 16:02:12 UTC", "updated_at": "2023-02-01 16:02:12 UTC", "state": "active", "iid": 88, "start_date": "2023-05-18", "group_id": 9970, "lock_version": 0, "project_id": null}