Details
-
Bug
-
Resolution: Fixed
-
High
-
None
-
11
-
Severity 2 - Major
-
1
-
Description
Summary
If we use the Update Issue Custom Field post-function in JIRA to set a custom field value, JIRA will actually only find the issue if we search for its old value, ignoring this new value set.
This issue also occurs whenever a custom field is updated upon a workflow transition screen. As an example, if a custom field has no value and is updated during a transition, searching for the new value will not return the expected issue. This does not include the issue creation screen.
Steps to Reproduce
In Post-Function | In Workflow Transition |
---|---|
|
|
Expected Results
The ticket is only found in "Test Field" = 'Text1' in first search, before setting the field, and only found in "Test Field" = 'Text2' after it.
Actual Results
The ticket is found in "Test Field" = 'Text1' in both cases, even after setting the field to 'Text2'.
Notes
This does not happen if we set the field by editing the issue.
Workaround:
- Editing custom field value manually makes it searchable once again
- Setting custom field on issue creation screen (if applicable) also works.
Attachments
Issue Links
- is duplicated by
-
JRACLOUD-67704 Custom field value set on workflow transition screen is not searchable
- Closed
- Testing discovered
-
JRACLOUD-68040 Updating issue fields fails in Jira fails with exception
- Closed
- relates to
-
JVS-2426 Loading...