...
...
BPMN 2.0
...
| Info |
|---|
Playground and example diagrams You can find a couple of readily copyable example diagrams in the /wiki/spaces/UPLAY/pages/1746010343. |
...
Rendering engine
...
Chart & Diagram types
...
Example galleries
...
Online playgrounds
...
Visual Studio Code extensions
...
...
Arbitrary visualizations
...
...
...
...
...
Arbitrary visualizations
...
...
...
...
...
ASCII
...
...
...
…
...
...
...
...
...
Flowchart
Sequence diagram
Class Diagram
State Diagram
Entity Relationship Diagram
User Journey
Gantt
Pie Chart
Directives
...
...
...
...
...
Graphs
...
...
...
...
System Context & System Landscape diagrams
Container diagram
Component diagram
...
...
Example CI/CD solutions TBD |
Provider and Status
Each service and resource type requires a dedicated mapping to the five Jira Software Cloud data provider types – we are evolving this along the following lines:
Jira Software Cloud data providers
– feasibility has been verified, implementation is pending (CodeCommit)Status colour Yellow title Source
– integration is available, with additional AWS services in developmentStatus colour Green title Build
– integration is available, with additional AWS services in developmentStatus colour Green title Deployment
– feasibility has been verified, implementation is pending (App Config)Status colour Yellow title feature flag
– integrations is blocked due to API not being sufficiently supported yetStatus title Remote Links (Beta)
AWS resource event mapping status
– dedicated support of applicable resource lifecycle eventsStatus colour Green title Lifecycle events
– indirect support of applicable resource lifecycle events via CodePipelineStatus colour Green title codepipeline events
– support of result status reporting via CodePipeline (i.e. success/failure)Status colour Blue title codepipeline result
– integration feasibility has been verified but implementation is pendingStatus colour Yellow title pending
– integration feasibility has not yet been verifiedStatus title triage
