Closed
Milestone
Jun 8, 2017–Jul 22, 2017
9.4
Display by
Burndown chart
Remaining
Guideline
Burnup chart
Total
Completed
Unstarted Issues (open and unassigned)
0
Ongoing Issues (open and assigned)
0
Completed Issues (closed)
74
4
- Geo: Improve checks from SystemChecks to include more configuration issues
- Geo log cursor is broken
- Geo: investigate alternative to geo_{primary|secondary}_role in gitlab.yaml
- Increase parallelism of GeoRepositorySyncWorker
- Git access over HTTPS is broken with LDAP account on Geo secondary
- DR: Could not connect to Geo node - HTTP Status Code: 500
- Repository#fetch_geo_mirror quietly fails if the repository is broken
- Show replication status in Geo admin panel
- Make CI artifacts to be stored on object storage
- Allow to access individual files for artifacts stored on Object Storage
- Related Issues BE followup - Add public API
- Slack slash commands using Slack app integration on GitLab.com
- Productionize Object-Storage
- Link between project pipeline views (mini-graph)
- Namespace license checks for locking project membership to members of a group
- Namespace license checks for exporting issues
- Namespace license checks for audit events
- Namespace license checks for preventing committing secrets
- License checks for global code search (ElasticSearch)
- Namespace license checks for issue/MR templates
- Namespace license checks for contribution analytics
- Namespace license checks for burndown charts
- Namespace license checks for repository mirrors
- Namespace license checks for group-level webhooks
- Namespace license checks for issue weights
- Namespace license checks for branch and tag permissions for users and groups
- Namespace license checks for push rules
- Namespace license checks for fast-forward merge when possible
- Namespace license checks for squash and merge
- Namespace license checks for rebase MR before merge
- Namespace license checks for issue boards focus mode
- Namespace license checks for issue boards with milestones
- Namespace license checks for multiple issue boards
- Namespace license checks for MR approvers
- Namespace license checks for service desk
- Namespace license checks for multiple issue assignees
- GitLab CE features to work with unlicensed EE instance
- Adding approvals via our API could raise a race condition when an approval is sent via the API and a commit is pushed at the same time
- Extend namespace license checks to existing EE features for GitLab.com and EE as default
- Environment-specific variables
- Service Desk by default configured on
- Related issues
- Project setting to toggle ability to overwrite merge request project settings
- Rebase not working with forked projects in 9.4.2
- navbar covers Boards topbar in focus mode
- Deprecated LDAP config syntax broken on 9.4.2 and up
- Only show Related Issues add badge when user can :admin_issue_link
- ArtifactUploader copies files across filesystems
- `Board` should be `Boards` in new navigation
- Logged-out users can't see related issues
- Rebasing not working with Merge Requests
- Improvements for Multi-Project Pipeline Mini-graph
- Licenses with explict plan: "" or plan: nil specifiers are not treated as EES
- Manual QA for 9.4 RC2 (staging)
- Audit events do not exist in new EE navigation admin panel
- Adding a related issue by keyboard adds the issue twice
- Elasticsearch indexer attempts to reindex entire repository with pull mirror
- Issue description is not taken atwho selection in consideration
- Refactor docs for "Slack application service"
- Transient spec failure in spec/features/protected_branches_spec.rb
- Follow-up from "Namespace license checks for multiple assignees"
- Add separate docs for multiple assignees
- Unable to remove approvers in 9.3.2
- Document that Code Quality needs a base report to compare to
- Expand `Namespace#feature_available?` to check the `application_settings` similar to what we have for `Project#feature_available?`
- Shared example group 'protected branches > access control' has been previously defined
- Related system note should not be visible for confidential issue if don't have confidential issue permission to view
- UI polish for Related Issues
- Code Quality not shown in Status Widget
- Follow-up from "Document the Delete Merged Branches functionality"
- Sometimes, Deploy Boards show Kubernetes deployment not found
- Text decoration on suggested approvers in MR Widget
- CE and EE KubernetesService
- Elasticsearch AWS support not using role credentials when applicable
Loading
Loading
Loading