Difference between revisions of "Patch: 05th February 2018"
(Created page with "This page details the content that has been released in the patch named in the title above, if you were looking for the content from a different Sprint, or Union Cloud Release...") |
(→ZDTkt#) |
||
| Line 18: | Line 18: | ||
*This issue has been resolved. | *This issue has been resolved. | ||
| − | == | + | == DE2054 == |
| − | + | ===Approving Nominations=== | |
| − | === | + | Directly via the URL it was possible for a Union Administrator to approve a candidate once an election had begun, this issue has now been resolved. |
| − | |||
*This issue has been resolved. | *This issue has been resolved. | ||
Revision as of 10:34, 9 April 2018
This page details the content that has been released in the patch named in the title above, if you were looking for the content from a different Sprint, or Union Cloud Release, please take a look at the Version History page to see all Sprints and Releases.
Contents
ZD9406
Missing Draft Elections
Issue occurred where Elections that had been created as, and left in a draft state, if the provisional date that was set for the duration of the election had passed, the election was no longer visible in the Current or Past Election tabs.
- This issue has been resolved.
ZD9131
Incorrect Date on Refund & Resale of Membership
We store two dates on a user group membership record in the ugm table . An end_date and an expire_date_time. expire_date_time is passed as end_date in API. The way this is used is the following. Whenever someone buys a membership lets say today for a membership ending on 08/12/2018. The expire_date_time gets set to 08/12/2018. Now when that day comes, the current to alumni job running every night picks this up and applies this value to the end date field as well. So on 09/12/2018 both these date columns show date 08/12/2018. On that day if I see current members user-group, system checks for members whose database column end_date is beyond 08/12/2018 and hence the said member is not seen there. Even if the API call is made on that day it will show the correct end date i.e. 08/12/2018. If a user's membership record is directly extended or brought before(globally or record level) again the change is correctly reflected on the API end_date again because the expire_date_time is extended.
While refunding membership before it's natural expiry, we are not setting the expire_date_time but the end_date directly. The solution is to actually set the expire date_time as well.
- This issue has been resolved.
ZD9352 ZD9449
SiteWide Search Issue
Further updates to the Elastic Search settings to improve functionality, as there had been some issues with results for particular strings not being returned.
- This issue has been resolved.
DE2054
Approving Nominations
Directly via the URL it was possible for a Union Administrator to approve a candidate once an election had begun, this issue has now been resolved.
- This issue has been resolved.
Uncat
Minor uncategorised fix
Title
Details
