-
Bug
-
Resolution: Fixed
-
Low
-
10.80
-
1
-
Severity 3 - Minor
-
No
Issue Summary
When a Jira Bug is synced to a Jira Align Story of type defect and is updated in Jira Align, the audit log will indicate that the Jira Project is changed even though it's not.
Steps to Reproduce
- Jira Align - Jira connector is configured.
- Add Bug to Story of type defect in Custom Issue Types
- Create a Jira Bug and wait for it to sync in Jira Align.
- Once synced, open the story of type defect(Jira Bug) in JA and update any fields.
- Check the audit logs.
Expected Results
Audit log should only indicate what was chaged.
Actual Results
Audit log always indicates that the Jira Project is Changed.
Workaround
This issue is only on the logging and the Jira Project key is not changed on the backend side.
Currently there is no known workaround for this behavior. A workaround will be added here when available.
- duplicates
-
JIRAALIGN-2191 [JIRAALIGN-2191] Story - Jira Project changed in Audit log is null
- Closed