Open issues from alerts as `GitLab Alert Bot`
We are currently working on the support for opening issues from alerts: https://gitlab.com/gitlab-org/gitlab-ee/issues/4925#note_146390734
However we need a user to set as the "author" of these issues. We are going to ship the first iteration behind a feature flag, which opens issues with the built-in ghost
user a the author, in order to be able to start doing some testing with customers.
Issues opened as a ghost user are not ideal though, and we need our own Bot user that we can use to open these issues under, like Service Desk. (GitLab Support Bot)
Proposal
We should create another bot user called GitLab Alert Bot
, and open all new issues from alerts under that user.
Designs
- Show closed items
- Issue#324228BacklogCategory:SAST GitLab Core GitLab Premium GitLab Ultimate [deprecated] Accepting merge requests backend devops application security testing group static analysis section sec type feature
- Epicgitlab-org#130501219Feb 10 – Sep 13, 2024Category:SAST devops application security testing feature consolidation group static analysis section sec type feature
- Issue#439046BacklogCategory:SAST backend customer devops application security testing group static analysis section sec
- Issue#425084BacklogCategory:SAST devops application security testing group static analysis section sec type feature workflow planning breakdown
- Issue#373117515.9Category:SAST Deliverable Track Health Status [DEPRECATED] devops application security testing feature enhancement group static analysis section sec type feature workflow complete
- Issue#36295816.0Category:SAST Deliverable GitLab Free GitLab Premium GitLab Ultimate backend customer devops application security testing documentation group static analysis missed-deliverable missed:15.7 missed:15.8 section sec type feature workflow complete
- Issue#36284915.10Category:SAST Deliverable [deprecated] Accepting merge requests devops application security testing feature consolidation group static analysis section sec type feature workflow complete
- Issue#35266615.4Category:SAST GitLab Free GitLab Premium GitLab Ultimate backend devops application security testing documentation group static analysis missed:15.2 missed:15.3 section sec type feature
- Issue#34725815.4Category:SAST backend customer devops application security testing feature enhancement group static analysis section sec type feature workflow production
- Issue#335221BacklogCategory:SAST [deprecated] Accepting merge requests devops application security testing group static analysis maintenance workflow section sec type maintenance
- Issue#33406514.02Category:SAST backend devops application security testing group static analysis section sec type maintenance workflow in dev
- Epicgitlab-org#544064Feb 18 – Apr 17, 2021Category:SAST devops application security testing group static analysis section sec type feature
- EpicClosedgitlab-org#56881013Jan 18 – Jun 17, 2021Category:SAST backend devops application security testing group static analysis section sec
- Issue#331801BacklogCategory:SAST [deprecated] Accepting merge requests backend devops application security testing feature enhancement group static analysis section sec type feature
- Issue#330578BacklogCategory:SAST Product Feedback SAST: New Scanner [deprecated] Accepting merge requests customer devops application security testing group static analysis section sec
- Epicgitlab-org#57971015Apr 18 – May 17, 2021Category:SAST [deprecated] Accepting merge requests backend devops application security testing feature enhancement group static analysis section sec type feature
- Issue#327236BacklogCategory:SAST [deprecated] Accepting merge requests backend devops application security testing feature enhancement group static analysis section sec type feature
- Issue#321204BacklogCategory:SAST [deprecated] Accepting merge requests backend devops application security testing group static analysis section sec type feature
- Issue#118496BacklogCategory:SAST SAST: Integrate customer devops application security testing group static analysis section sec type feature workflow start
- Issue#26206813.11Category:SAST Deliverable Discovery SAST: Integrate [deprecated] Accepting merge requests backend devops application security testing group static analysis missed-deliverable missed:13.10 missed:13.9 section sec type feature workflow planning breakdown
- IssueClosed#300486BacklogCategory:SAST [deprecated] Accepting merge requests auto updated backend devops application security testing group static analysis section sec type feature
Activity
-
Newest first Oldest first
-
Show all activity Show comments only Show history only
- Joshua Lambert added devopsmonitor ~2975006 + 1 deleted label
added devopsmonitor ~2975006 + 1 deleted label
- Joshua Lambert changed the description
changed the description
- Author Contributor
cc @splattael
- Author Contributor
If we have time for this in %11.9 great, otherwise we should do this in the %11.10 cycle. Even if we miss freeze, maybe we can get this in with the FF process.
Edited by Joshua Lambert - Joshua Lambert changed milestone to %11.10
changed milestone to %11.10
- Joshua Lambert added Deliverable label
added Deliverable label
- Joshua Lambert mentioned in issue #4925 (closed)
mentioned in issue #4925 (closed)
- 🤖 GitLab Bot 🤖 added [deprecated] Accepting merge requests label
added [deprecated] Accepting merge requests label
- Peter Leitzen assigned to @splattael
assigned to @splattael
- 🤖 GitLab Bot 🤖 removed [deprecated] Accepting merge requests label
removed [deprecated] Accepting merge requests label
- Peter Leitzen mentioned in merge request !10353 (merged)
mentioned in merge request !10353 (merged)
- Seth Engelhard added backend label
added backend label
- Peter Leitzen created merge request !10460 (merged) to address this issue
created merge request !10460 (merged) to address this issue
- Peter Leitzen mentioned in merge request !10460 (merged)
mentioned in merge request !10460 (merged)
- Maintainer
This issue has passed the feature freeze date and considered a missed-deliverable. Adding missed:11.10.
- 🤖 GitLab Bot 🤖 added missed-deliverable missed:11.10 labels
added missed-deliverable missed:11.10 labels
- Seth Engelhard changed milestone to %11.11
changed milestone to %11.11
- Contributor
This issue is closed - https://gitlab.com/gitlab-org/gitlab-ee/issues/4925
Are we able to create issues from alerts today but we have to use a specific user and this allows us to do so with a generic/bot user?
- Sean McGivern closed via merge request !10460 (merged)
closed via merge request !10460 (merged)
- Sean McGivern mentioned in commit b9fe2104
mentioned in commit b9fe2104
- Reuben Pereira mentioned in merge request !10569 (merged)
mentioned in merge request !10569 (merged)
- Contributor
Is this GitLab Premium tier?
Collapse replies - Developer
- Peter Leitzen added GitLab Ultimate label
added GitLab Ultimate label
- 🤖 GitLab Bot 🤖 added Enterprise Edition label
added Enterprise Edition label
- Jeremy Watson (ex-GitLab) mentioned in issue #36500 (closed)
mentioned in issue #36500 (closed)
- Tetiana Chupryna mentioned in issue #197349 (closed)
mentioned in issue #197349 (closed)
- Amanda Rueda mentioned in merge request !31160 (merged)
mentioned in merge request !31160 (merged)
- Amanda Rueda mentioned in issue #211616 (closed)
mentioned in issue #211616 (closed)
Old thread but maybe someone knows the answer-
How can I give this bot at least "Guest" permission on projects so it is able to assign the created issues using templates? We make use of LDAP sync for permission, so this local internal user cannot be added to groups/projects with the right role.
Thanks