...
This page describes how you can use autocomplete on an issue (simple query).
Using autocomplete on Create/Update
...
issue screens
Follow the steps below:
...
- Log into your Jira as Admin.
- Go to the field configuration page and ensure that the type of the custom field is "Autocomplete
...
- ".
...
- Go to an issue in
...
- Jira and try to edit it first. The database custom fields will appear like any other custom field. When trying to edit an issue, the sql is executed and the results will be available through autocomplete.
...
...
- Type the first letter of a possible value and a list of options will appear. From these options you can select one
...
- for the current field. When
...
- you select a value for
...
- the main database custom field, the value for the child database custom field is filled in
...
- automatically, see an example in the picture below
...
- .
- Now that the fields are filled in, you can update the issue
...
- with the provided values.
- After
...
- you update the issue, the values are displayed as details of that issue.
| Info |
|---|
The creation of an issue can be done in a similar way. |
...
Using autocomplete for a transition
...
The following example involves updating the issue fields when Reopen is pressed.
...
This is similar to the update of an issue,
...
but we provide more details on how to use the database custom fields on transitions.
The following example involves updating the issue fields when a user clicks Reopen for a ticket.
The value of the field Product Name can be changed to another value like in the screenshot below:
The database child custom field is filled in on selection of the value for the main database custom field. If the button you click Start Progress is pressed, the values are updated for the database custom fields and the issue goes in to the final state of the transition.
For this our example it looks like this:
the following picture.
