Add cross-stage dependency to issue template
What does this MR do?
This MR proposes adding information to the feature request template that will help identify cross-stage dependencies for issues created on GitLab.
Feature Requests often lack information that help indicate multiple teams or DRIs will need to be involved in the engineering process. This is true mainly to Product Designers, that need to identify ahead of time when a proposed change on the user experience will affect a particular feature or workflow. As much as team members try to be proactive to try and identify dependencies and potential DRIs for existing features via Slack, there are times when different proposals are established and planned by dev teams, causing friction and slowing down the delivery process. Examples:
With this proposal, we aim to allow anyone planning/creating issues be able to proactively identify what product area or feature will be touched. This will help Product Designers, Product Managers, and Developers to plan their work and keep other counterparts informed.
Screenshots
Does this MR meet the acceptance criteria?
Conformity
-
Changelog entry -
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