JIRA Issues:

Universal Navigation: https://topcoder.atlassian.net/browse/PROD-3116

Pull Request:

• tc-website : #70
• tc-website-static : topcoder-archive/topcoder-platform-tc-website-static#5

JIRA Issues:

• Update PACTS so user can navigate back to their settings page: https://topcoder.atlassian.net/browse/PROD-2989

Pull Request:

• tc-website : #64
• tc-website-static : topcoder-archive/topcoder-platform-tc-website-static#4

JIRA Issues:

• Member payment tracking reskin: https://topcoder.atlassian.net/browse/PROD-2121
• Reskin Header and Footer of payment tracking page: https://topcoder.atlassian.net/browse/PROD-2197
• Enable payment functionalities lost due to reskinning: https://topcoder.atlassian.net/browse/PROD-2892

Pull Request:

• tc-website : #61
• tc-website-static : topcoder-archive/topcoder-platform-tc-website-static#3

This is a patch to fix the issue of the jira_issue_id value being nulled when a new payment detail record is created. This was happening when a payment was updated and when the user hit "Pay Me".

This is needed since V5 uses the jira_issue_id column to hold the v5 challenge GUID

Adds a column to the internal PACTS listing pages that displays the v5 challenge ID when it is present. This helps transition away from legacy OR-based payments and toward payments from v5 flows.