Draft: Remove jira_issues_show_integration feature flag
What does this MR do?
For #299832 (closed)
Screenshots (strongly suggested)
Does this MR meet the acceptance criteria?
Conformity
-
📋 Does this MR need a changelog?-
I have included a changelog entry. -
I have not included a changelog entry because _____.
-
-
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers -
Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
-
Label as security and @ mention @gitlab-com/gl-security/appsec
-
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team
Merge request reports
Activity
mentioned in merge request !56182 (merged)
3 Warnings ⚠ Please add a merge request type to this merge request. ⚠ This merge request does not have any assignee yet. Setting an assignee clarifies who needs to take action on the merge request at any given time. ⚠ This merge request does not refer to an existing milestone. 1 Message 📖 CHANGELOG missing: If you want to create a changelog entry for GitLab FOSS, run the following:
bin/changelog -m 56748 "Enable jira_issues_show_integration by default"
If you want to create a changelog entry for GitLab EE, run the following instead:
bin/changelog --ee -m 56748 "Enable jira_issues_show_integration by default"
If this merge request doesn't need a CHANGELOG entry, feel free to ignore this message.
Reviewer roulette
Changes that require review have been detected! A merge request is normally reviewed by both a reviewer and a maintainer in its primary category (e.g. frontend or backend), and by a maintainer in all other categories.
To spread load more evenly across eligible reviewers, Danger has picked a candidate for each review slot, based on their timezone. Feel free to override these selections if you think someone else would be better-suited or use the GitLab Review Workload Dashboard to find other available reviewers.
To read more on how to use the reviewer roulette, please take a look at the Engineering workflow and code review guidelines. Please consider assigning a reviewer or maintainer who is a domain expert in the area of the merge request.
Once you've decided who will review this merge request, assign them as a reviewer! Danger does not automatically notify them for you.
Category Reviewer Maintainer ~feature_flag No reviewer available No maintainer available If needed, you can retry the
danger-review
job that generated this comment.Generated by
🚫 DangerHi @tomquirk,
Please add labels to your merge request, this helps triage community merge requests.
Thanks for your help!
❤
You are welcome to help improve this comment.
added auto updated label
added groupecosystem [DEPRECATED] label
changed milestone to %13.11
assigned to @tomquirk
Closing, work happening in !56942 (merged)
cc @justin_ho
added 1 deleted label and removed devopscreate label
added devopsmanage label and removed 1 deleted label