-
Type:
Bug
-
Resolution: Fixed
-
Priority:
High
-
Affects Version/s: 5.4.0
-
Component/s: Integration - JIRA, Integration - JIRA - Issue Transitioning
-
3
-
Severity 3 - Minor
-
3
Summary
Steps to Reproduce
- Define a custom field in JIRA, e.g. "Colors".
- Add this field to a project, e.g. "GUS"
- Create an issue in JIRA, e.g. "GUS-1" and assign a value, e.g. "Green", to this custom field.
- Make a commit and comment with the JIRA issue ID.
- Push to Stash
- In Stash click on the JIRA issue ID in the Issues column.
- Transition the issue by clicking "Done".
Expected Results
The value visible in JIRA in the custom field, e.g. "Green", is also visible in the modal window.
![]()
Actual Results
The custom field is visible without a value:
![]()
If the issue is transitioned, the existing data "Green" in JIRA is removed.
- is duplicated by
-
BSERV-7893 Stash changes state variables without user interaction
-
- Closed
-
-
BSERV-9378 JIRA-BitBucket integration: custom select fields get reset
-
- Closed
-
-
BSERV-9591 Failure is not indicated when transitioning Jira issues in Bitbucket Server
-
- Closed
-
- is related to
-
BSERV-9590 Jira issue dialog is not displaying the content of issue fields on transition
-
- Closed
-
- relates to
-
BSERV-7893 Stash changes state variables without user interaction
-
- Closed
-
-
FE-6656 Custom field values overwritten or set on modal transition
-
- Closed
-