Configuring the Viable Issues Button

Owned by Thomas Egger (Deactivated)
Last updated: 16. Mar 2021
2 min read

After reading Installation Viable Issues Cloud and using it once (Quick start guide Viable Issues Cloud), it's time to get to know the details.

Configuration of a Viable Issues macro

The Viable Issues Button has several Macro Parameters to be optionally configured:

  • Project

  • Issue type

  • Component

  • Priority

  • Labels

  • Button text

Project

Define in which project the issue will be created.

When the project field is empty, the issue will be created in a Jira project where the Confluence space key is the same as the Jira project key.

The user can change the value to whatever fits best while creating the issue.

Default value: Empty

Possible values: All projects the user configuring the macro can access.

Issue type

Define which Issue type the issue should be.

Default value: Empty

As the default issue type for a given Jira project can only be accessed by an admin, we don’t influence what shall be selected while using the button with no issue type selected. The user can change the value to whatever fits best while creating the issue.

Possible values: All issue types that are related with the corresponding Jira project.

Component

Allows to set a pre-defined component when the macro is used. The user can change the value to whatever fits best while creating the issue.

Default value: None

Possible values: All components created in the corresponding Jira project first.

Priority

Allows to set a pre-defined priority when the macro is used. The user can change the value to whatever fits best while creating the issue.

Default value: None

Possible values: All priorities that are related with the corresponding Jira project.

Labels

Allows the user to add any labels that should be added to the issues when the macro is used.

Additionally a label that indicates the source of an issue will be added. Please see Quick start guide Viable Issues Cloud for details on how the label is named.

Button text

Allows you to define the label of the Viable Issues Button.

Default value: Empty

Default label: Viable Issues (only visible if the button remains unconfigured)