Issue Summary

Datetime shows in wrong format in Development section
This is reproducible on Data Center.

Steps to Reproduce

1. Create application link between Jira and Bitbucket
2. In Bitbucket, create a project and commit a sample code
3. In Jira, create Scrum Project with sample data
4. Open anyone of the sample tickets, for example SP-22, click Create branch
5. Click Issues > Current Search, and click the testing ticket, for example SP-22

The datetime shows in wrong format before take an action in browser, which is unexpected. The actions can be but not limited to:

• if you open and close the edit screen
• if you open and close develop tools ( F12)
• If you return to the browser after clicking the mouse anywhere other than the browser

After you take an action in browser, the date time format will be restored in correct format.

Additional information related to this issue

1. The issue only happens when the Jira issue is opened by going through Issues > Current Search flow and doesn't happen when you visit the issue directly using search box or direct URL hit.
2. Once you land on the Jira issue page, try going to a different application (other than the browser) and then come back to trigger a refresh of the development panel. By doing so, the date is refreshed and displayed in the right format.
3. The request to /rest/dev-status/1.0/issue/summary is made only when you follow the step 2 above which proves that there is nothing wrong with the REST response that could cause the issue. In fact once the URL is hit, the UI is updated with the right date format.
4. The DOM object under question is rendered using server side templating (SOY) which contains ${$lastUpdated} which is supposed to be rendered using another SOY template but apparently it gets rendered with a $ (possibly HTML encoding issue?). This is most likely the culprit behind incorrect rendering. You can see the code here.
5. The difference between correctly rendered and incorrectly rendered DOM element is as follows. Note the attributes which contain date value which are same in both cases which is another proof that the date returned by the backend is not responsible for incorrect rendering -

Expected Results

    <div class="rolling-container sliding-container" style="height: auto;">
        <div class="rolling-content">
            <div>Latest
                <time class="livestamp date user-tz allow-future" data-datetime-format="fullAge"
                      datetime="2017-12-15T05:52:18.000+0000" title="15/Dec/17 5:52 AM">15/Dec/17 5:52 AM
                </time>
            </div>
        </div>
    </div>

Actual Results

    <div class="rolling-container sliding-container">
        <div class="rolling-content">
            <div>Latest
                <time class="livestamp date user-tz allow-future" data-datetime-format="fullAge"
                      datetime="2017-12-15T05:52:18.000+0000" title="15/Dec/17 5:52 AM">$2017-12-15T05:52:18.000+0000
                </time>
            </div>
        </div>
    </div>

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available