Details
-
Bug
-
Resolution: Fixed
-
Medium
-
10.100.3
-
4
-
Severity 3 - Minor
-
No
Description
Issue Summary
When the state of a work item is changed the correte date timestamp is not being captured in all scenarios. If the user changes the state on JA and hit save, it got recorded, but if the same happens without the save (like being changed on Jira and synced to JA), the timestamp is not recorded even though the state changes.
Steps to Reproduce
- Create a Feature on JA, let it sync with Jira
- Change the State on JA
- Check the tables (or EI) and notice that the timestamp was capture related to that state
- Now change the State on Jira and wait it to sync
- Check the same data and you will notice that the timestamp of the change was not captured on the correct fields
Expected Results
Regardless of how the state changes, the timestamp will be captured on the corresponding fields.
Actual Results
Depending on how the state is changed, the timestamp is not captured accordingly.
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
Fix Existing Data
Attachments
Issue Links
- is related to
-
JIRAALIGN-3868 Date timestamp of changes in state are not correctly captured - wrong timestamp
-
- Closed
-
- mentioned in
-
Page Loading...
- relates to
-
ALIGNSP-12278 Loading...
- resolves
-
ALIGNSP-11354 Loading...
-
ALIGNSP-12086 Loading...
-
ALIGNSP-12218 Loading...