3. How to configure the Button - Display Settings ?
Required Jira Role: Jira Software Administrator Please switch to the second Tab “Display Settings” to define where and when the button should be displayed:
Parameter
Syntax
Description
Source Projects
Project Picker Mandatory
Please select the projects where you want to place your button on the view screen.
Source Issue Types
Issue Type Picker Mandatory
Please select the issue types where you want to place your button on the view screen.
✓
The list of issue types is restricted to only those relevant to the previously selected projects.
Filter (JQL)
JQL Expression Optional
You can add an optional condition for displaying the button by defining a JQL (Jira Query Language) statement. Please make sure the JQL statement is correct and that, together with the selected source projects and source issue types, it leads to meaningful results.
✓
The JQL statement syntax is checked by the app.
Filter (JQL)
asasasasas
Error in the JQL Query: Expecting operator before the end of the query. The valid operators are =, !=, <, >, <=, >=, ~, !~, IN, NOT IN, IS and IS NOT.
Permissions
Picker Optional
You can add an optional condition for displaying the button by defining specific permissions. Please select first the permission type:
Permissions
Select... ⌄
Groups
Users
Project Roles
The app will list you all valid parameters, and you can select one or several values:
All configured display settings must be true before the button is displayed. The app checks your Jira instance in real time using the Atlassian standard API. Atlassian sometimes shows changes (e.g., in user groups) with minor latencies. Additionally, the response time of the Atlassian API impacts when the button is checked and can be displayed, which can take several seconds.
4. How to configure the Button - Action Settings ?
Required Jira Role: Jira Software Administrator Please switch to the second Tab “Action Setting” to complete the Button Configuration, and configure which issue type should be created and linked:
Parameter
Syntax
Description
Target Project
Project Picker Mandatory
Please select the project from which you want to create and link issues.
Target Issue Type
Issue Type Picker Mandatory
Please select the issue type from which you want to create and link issues.
✓
The list of issue types is restricted to only those relevant to the previously selected project.
Template Issue
Issue Picker Optional
Select an existing issue as a template. The fields of this issue will be prefilled automatically in the creation screen.
You can select the issue by entering the exact issue key:
Template Issue
Exact key ⌄
Template Fields
Select...
TEMP-1 ⌄
TEMP-1 Bug-Template: Please enter a clear Bug Summary: What is exactly is wrong
Or by searching the issue summary and selecting one result:
Template Issue
Summary ⌄
Template Fields
Select...
Bug-Template ⌄
TEMP-1 Bug-Template: Please enter a clear Bug Summary: What is exactly is wrong
CL-47 Bug-Template: Please enter a clear Bug Summary: What is exactly is wrong
Template Fields
Field Picker Optional
Default: All relevant fields will be copied if they exist in the template issue.
Once a template issue has been selected, you can narrow down the fields to be copied in the creation process to a subset. We will list exactly the fields that will be used in the creation screen of the configured target project and target issue type.
Template Fields
Components ×Test Repository Path ×⌄
Assignee
Test Type
Cucumber Test Type
Cucumber Scenario
Generic Test Definition
Manual Test Steps
Test Sets association with a Test
Pre-Conditions association with a Test
Test Plans associated with a Test
Link Type
Link Picker Optional
Default: No Link
Choose the type of link that should be established between your source issue and the target issue after the creation action.
i
Our Issue Template Feature leverages the capabilities of the Atlassian Forge Platform, providing full support in Software and Work Management projects. However, when used in Service Management or Product Discovery projects, some limitations may arise, such as restrictions on custom fields and UI modifications. See Atlassian Forge Platform Limitations.
4. How to configure the Button - Create Behaviours ?
Required Jira Role: Jira Software Administrator Please switch to the second Tab “Create Behaviours” to complete the Button Configuration, if you want to add Behaviours to the Create Screen and refer to the documentation here:
Integrate your CRM with other tools
Venenatis sollicitudin posuere elit consequat et enim. Neque tortor amet dictum tempor. Leo facilisis aliquet viverra scelerisque eleifend viverra est. At massa erat vel amet enim laoreet dictum pellentesque. Urna cursus quam pulvinar tellus. Duis fermentum nibh volutpat morbi. Et ac sed ultricies ut nunc.
How to connect your integrations to your CRM platform?
Et urna ac et maecenas fusce amet. Nibh nec commodo massa sed. Tincidunt porttitor in pharetra egestas sit neque ac lacus. Amet a nunc et cum. Odio at volutpat volutpat in leo eget ipsum diam elementum. Erat magna arcu orci.
Morbi fringilla molestie magna sed dictum. Praesent pharetra.
Cras mi purus, viverra vitae felis sit amet, tincidunt fringilla lorem.
Non mattis urna ex nec sem. Donec varius diam et suscipit.
Quisque euismod posuere lacus sit amet volutpat praesent.
Quis faucibus massa sit egestas. Sit fermentum est ac pulvinar et sagittis sed sit ut. Quis faucibus aenean nibh vestibulum enim mi sit. Sollicitudin ultrices ultrices in ipsum urna fringilla massa leo. Sapien ultricies vitae rhoncus molestie purus. Urna urna dolor euismod porttitor et. Magna adipiscing dictum et adipiscing.
Quis faucibus massa sit egestas. Sit fermentum est ac pulvinar et sagittis sed sit ut. Quis faucibus aenean nibh vestibulum enim mi sit. Sollicitudin ultrices ultrices in ipsum urna fringilla massa leo. Sapien ultricies vitae rhoncus molestie purus.
Infotech is the next-gen CRM platform designed for modern sales teams
Cursus curabitur euismod vel fermentum sapien non dolor odio vel. Tortor lectus mauris in praesent a tincidunt nam. In aenean odio aliquet pretium viverra elit quis magna. Eget ut risus posuere velit purus nisi nec sollicitudin tellus enim.
“Sed id mi eget urna facilisis pharetra. Nunc viverra est at magna maximus consectetur. Sed nec maximus augue. Aliquam commodo sem eu.”
Cursus curabitur euismod vel fermentum sapien non dolor odio vel. Tortor lectus mauris in praesent a tincidunt nam. In aenean odio aliquet pretium viverra elit quis magna. Eget ut risus posuere velit purus nisi nec sollicitudin. Tellus enim interdum neque sit vestibulum lacus. Nam pulvinar a lectus justo aliquet.
Why using the right CRM can make your team close more sales?
Sed non quis tellus velit orci. Quam sed mauris elementum tempor viverra. Luctus semper risus ipsum id diam praesent. Pretium eget mauris ultrices curabitur sed sem amet. Erat nulla habitant in mattis massa mi adipiscing.
Morbi fringilla molestie magna sed dictum. Praesent pharetra.
Cras mi purus, viverra vitae felis sit amet, tincidunt fringilla lorem.
Non mattis urna ex nec sem. Donec varius diam et suscipit.
Quisque euismod posuere lacus sit amet volutpat praesent.
What other features would you like to see in our product?
Sed non quis tellus velit orci. Quam sed mauris elementum tempor viverra. Luctus semper risus ipsum id diam praesent. Pretium eget mauris ultrices curabitur sed sem amet. Erat nulla habitant in mattis massa mi adipiscing ullamcorper condimentum. Erat quisque integer tincidunt ac amet.