WIP: Create dependency flowchart for epic issues [RUN ALL RSPEC] [RUN AS-IF-FOSS]
What does this MR do?
I've been wanting a way to visualize how issues relate to each other as we plan out new features on ~"group::monitor". I couldn't find any issues for something like this, so I built it.
What is it:
- a flowchart which connects the issues directly under an epic based on how they block one another. Sub-epics aren't included & blocking relationships with issues in other epics aren't shown.
Still needed:
-
documentation -
string updates -
fix ee/spec/helpers/epics_helper_spec.rb:153 -
fix ee/spec/helpers/epics_helper_spec.rb:185 -
issue.rb specs -
javascript epic_tabs.js specs -
issue_link.tb specs
Approach:
- To keep the scope small-ish, I opted to generate a flowchart with mermaid based on the
blocks/is blocked byrelationships for linked issues. - By sticking to mermaid, this also means the designs are fairly fixed. The font & node color/shape are all fairly customizable, but that's about it. https://mermaid-js.github.io/mermaid/#/flowchart?id=styling-and-classes
Screenshots (strongly suggested)
| New flowchart | some of the corresponding epics | Epic without blocking dependencies |
|---|---|---|
 |
 |
 |
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
Edited by 🤖 GitLab Bot 🤖