After reading the https://hagen-management.atlassian.net/wiki/x/OgCJUg we now can go on a deep dive using Viable Issues for Confluence Cloud.
Using Viable Issues for Confluence Cloud
By clicking the Viable Issues Button, a dialog will open. It displays Jira's create screen.
In the default configuration of the button the project field will be filled with the Jira project bearing the same project key as the Confluence space. The project and issue type can be changed by the user while filling the create screen.
If the Viable Issues Button has been configured before, some fields might be pre-populated with content.
Complete your input on all displayed fields according to your needs.
At the bottom of the dialog you find four options:
Question mark 
As we are rendering the create screen within our app, some fields might not be displayed. The affected fields are listed here.
Create another
To create a series of similar issues select the Create another checkbox at the bottom of the dialog.
The dialog will remain open after the issue has been created and some of the fields will be may be pre-populated depending on your configuration and the values you may have specified when creating the previous issue.
Create
The issue will be created.
Cancel
The dialog will close and all your information entered in the create form will be lost.
Configuring the Viable Issues Button
As mentioned above, the Viable Issues Button can be configured. Find all the details on the page https://hagen-management.atlassian.net/wiki/x/U4CHUg.
Use-cases
Viable Issues for Confluence Cloud can be used in various use-cases. Basically customers use it to quickly create Jira Issues without leaving Confluence. Have a look at our https://hagen-management.atlassian.net/wiki/x/IgCRUg page to read about the glorious use-cases of Viable Issues for Confluence Cloud inspired by our customers.