/troubleshoot should work on the job page without the button
UX Plan
-
/troubleshoot
works on this page without any additional arguments - e.g. the user does not need to add a URL-
/troubleshoot
works when making requests not through the button
-
Technical details
From a backend perspective we just need to pass in the resourceId
for each duo mutation request on that page to get it to work and currently the frontend passes the backend the User
for the resourceId
.
Likely frontend only. To confirm.
Designs
- Show closed items
Relates to
Activity
-
Newest first Oldest first
-
Show all activity Show comments only Show history only
- Allison Browne marked this issue as related to #471244 (closed)
marked this issue as related to #471244 (closed)
- Allison Browne changed milestone to %17.3
changed milestone to %17.3
- Allison Browne changed the description
Compare with previous version changed the description
- Allison Browne mentioned in issue #471244 (closed)
mentioned in issue #471244 (closed)
- Allison Browne added gitlab-org#13080 (closed) as parent epic
added gitlab-org#13080 (closed) as parent epic
- Allison Browne assigned to @allison.browne
assigned to @allison.browne
- Allison Browne assigned to @jivanvl
assigned to @jivanvl
- Maintainer
@allison.browne, Please add a group or category label to identify issue ownership.You can refer to the Features by Group handbook page for guidance.
If you are unsure about the correct group, please do not leave the issue without a group label, and refer to GitLab's shared responsibility functionality guidelines for more information on how to triage this kind of issue.
This message was generated automatically. You're welcome to improve it.
- Maintainer
@allison.browne - please see the following guidance and update this issue.1 Error Please add typebug typefeature, typemaintenance and optionally a subtype label to this issue. If you do not feel the purpose of this issue matches one of the types, you may apply the typeignore label to exclude it from type tracking metrics and future prompts.
This message was generated automatically. You're welcome to improve it.
- Contributor
This issue was automatically tagged with the label groupacquisition by TanukiStan, a machine learning classification model, with a probability of 0.92.
If this label is incorrect, please tag this issue with the correct group label as well as automation:ml wrong to help TanukiStan learn from its mistakes.
If you are unsure about the correct group, please do not leave the issue without a group label. Please refer to GitLab's shared responsibility functionality guidelines for more information on how to triage this kind of issues.
Authors who do not have permission to update labels can use the
@gitlab-bot label ~"group::<correct group name>"
command, or leave the issue to be triaged by group leaders initially assigned by TanukiStan.This message was generated automatically. You're welcome to improve it.
- A deleted user added automation:ml groupacquisition labels
added automation:ml groupacquisition labels
- 🤖 GitLab Bot 🤖 added devopsgrowth sectiongrowth labels
added devopsgrowth sectiongrowth labels
- Caroline Simpson added automation:ml wrong devopsverify grouppipeline execution sectionci labels and removed devopsgrowth groupacquisition sectiongrowth labels
added automation:ml wrong devopsverify grouppipeline execution sectionci labels and removed devopsgrowth groupacquisition sectiongrowth labels
- Caroline Simpson added typebug label
added typebug label
- Caroline Simpson added priority1 severity2 labels
- Caroline Simpson added typefeature label and removed typebug label
added typefeature label and removed typebug label
- Caroline Simpson removed severity2 label
removed severity2 label
- Caroline Simpson added workflowready for development label
added workflowready for development label
- Rutvik Shah mentioned in epic &13080 (closed)
mentioned in epic &13080 (closed)
- Author Maintainer
@jivanvl,
@mksionek
left a note about how we can do this: #471617 (comment 2004904448)It gets set in ruby with
set_application_context!
on the controller action. So this is the code change:diff --git a/ee/app/controllers/ee/projects/jobs_controller.rb b/ee/app/controllers/ee/projects/jobs_controller.rb index 5f67f8191191..214356ed50ce 100644 --- a/ee/app/controllers/ee/projects/jobs_controller.rb +++ b/ee/app/controllers/ee/projects/jobs_controller.rb @@ -9,6 +9,11 @@ module JobsController before_action only: [:show] do push_frontend_ability(ability: :troubleshoot_job_with_ai, resource: @build, user: @current_user) push_frontend_feature_flag(:root_cause_analysis_duo, @current_user) + set_application_context! + end + + def set_application_context! + ::Gitlab::ApplicationContext.push(ai_resource: @build.try(:to_global_id)) end end end
- Jose Ivan Vargas mentioned in merge request !159936 (merged)
mentioned in merge request !159936 (merged)
- Jose Ivan Vargas added workflowin dev label and removed workflowready for development label
added workflowin dev label and removed workflowready for development label
- Jose Ivan Vargas added workflowin review label and removed workflowin dev label
added workflowin review label and removed workflowin dev label
- Jose Ivan Vargas mentioned in issue jivanvl/manager-of-one#16 (closed)
mentioned in issue jivanvl/manager-of-one#16 (closed)
- Jose Ivan Vargas added workflowcomplete label and removed workflowin review label
added workflowcomplete label and removed workflowin review label
- Maintainer
This is now live in production, closing
- Jose Ivan Vargas closed
closed
- Rutvik Shah mentioned in epic gitlab-org#13872
mentioned in epic gitlab-org#13872