-
Bug
-
Resolution: Fixed
-
Low
-
10.103.2
-
1
-
Severity 3 - Minor
-
No
Issue Summary
Similar to JIRAALIGN-3689, however the timestamp data is actually entered, but it's incorrect information.
Steps to Reproduce
- Create a Story in Jira, let it sync with Jira Align
- Check the tables (or EI) and notice that the timestamp was captured related to that state
- Change the Status of the Story multiple times in Jira in quick succession as follows:
Note: that the timestamp is identical for each state change.
Check the same data and you will notice that the timestamp of the change was not correctly captured on the date fields
Expected Results
Regardless of when the state changes or the frequency, the CORRECT timestamp will be captured on the corresponding fields.
Actual Results
Depending on the frequency of the state change, the timestamp is not correctly captured accordingly.
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
- relates to
-
JIRAALIGN-3689 Date timestamp of changes in state are not correctly captured - NULL
- Closed
-
ALIGNSP-12278 Loading...
- mentioned in
-
Page Loading...