Table of Contents | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
1. How
...
Are the “Create and Link” Buttons Displayed for End Users
...
?
...
Status | ||||
---|---|---|---|---|
|
1.1 When is the Issue Picker Displayed for End Users?
The end user can utilize the Issue Picker under the following conditions:
The Issue Picker is included in the create and/or edit screen.
The end user has permissions to create or edit the specific issue type
1.2 How the relevant Issues are listed in the Issue Picker?
The list of issues that the end user can select is dynamically generated by the app.
The app executes the Filter JQL as an admin and retrieves a list of issues.
This list can be limited to the current project if configured accordingly.
Initially, only the first batch of issues retrieved is displayed (subject to Atlassian's limitations).
To view additional issues, the end user must click 'more'."
We assume that no end user will scroll through thousands of options. In such cases, the end user will likely use the search function to narrow down the results. Therefore, we have decided not to retrieve all options and provide a paging function (The behaviour is similar to the standard field Fix Version/s). Fetching an extensive list of options could result in significant waiting times, especially when the option list is extensive.
...
1.3 How can the End User use the search function in the Issue Picker?
The End User can enter any text to narrow down the list of listed issues:
The app searches for the entered text in the Summary field to retrieve a subset of the listed issues.
The app also searches for issue keys when:
The user enters the starting letters of the project key (minimum 2 letters) and
The entered key part belongs to existing projects.
The user can also enter e.g. STORY-1, in this case all issue keys starting with STORY-1 will be searched.
The search function of the app is based on the native search function of Atlassian, utilizing the JQL syntax. Therefore, the capabilities and limits are the same.
As soon as:
a button is configured for a specific source project and issue type,
and the button is 'enabled',
and the end user has the permission to access the source issue type view screen
then the 'Create and Link' button can be displayed in the View Screen, as follows (Example: + Bug):
...
The button in the right app context area is always visible and cannot be removed by users.
However, to display the button section in the bottom app panel area, the end user must first click on the following menu button, if necessary:
...
The end user can use the section menu to collapse or remove the section. This setting will be stored for future interactions and can be changed later:
...
Info |
---|
Atlassian has made the decision to hide the app panel section by default. Therefore, it is necessary for users to click on this button for each issue individually. We have requested Atlassian to enable Jira administrators to set the button section to be displayed by default. We recommend to use the button on right context area. |
2. Using the Buttons to Create and Link New Issues
Status | ||||
---|---|---|---|---|
|
The end user can see one or several buttons in the View Screen, under the 'Create and Link' section. By clicking on a button, the user can create a specific issue and link it with a pre-configured link. This accelerates the workflow of end users, allowing them to immediately create issues in the context of the source issue:
...
Info |
---|
The project is pre-selected on the create screen, but the end user has the option to change this selection. We have submitted a change request to Atlassian requesting the ability to fix this value. |
Tip |
---|
The issue type is pre-selected, and the end user cannot change this value. |