Details
-
Bug
-
Resolution: Fixed
-
Low
-
10.100.3
-
1
-
Severity 3 - Minor
-
No
Description
Issue Summary
For each action that happens on a Feature, an entry on the tblRequestsAudit is created, with the most last one having the _ValidTo set as NULL. So whenever a new entry is created, the last one is updated with a valid date, and the most recent one keeps the NULL. The problem is that, if for some reason a sync error happens, the last 2 entries on the table will keep the value as NULL.
This is reflected on EI, as the table Feature History will have the have 2 entries with the field Valid_to as 9999-12-31T00:00:00
Steps to Reproduce
- Create a Feature on JA, let it sync with Jira
- Break the sync between the 2 (in my case I did change one field, the PI one, as mandatory on Jira)
- Update the Feature on JA and wait it try to sync
- Query the table tblRequestsAudit for this Feature and see the column _ValidTo
Expected Results
Only one entry on tblRequestsAudit would keep the _ValidTo as NULL
Actual Results
More than one entry is having the _ValidTo as NULL
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
Attachments
Issue Links
- resolves
-
ALIGNSP-11325 Loading...